From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Luck, Tony" <tony.luck@intel.com>,
"Lin, Jing" <jing.lin@intel.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/asm: Add support for MOVDIR64B instruction
Date: Thu, 1 Aug 2019 14:03:59 +0300 [thread overview]
Message-ID: <20190801110358.jmfd2cy7s277j6qv@black.fi.intel.com> (raw)
In-Reply-To: <20190801095928.GA32138@nazgul.tnic>
On Thu, Aug 01, 2019 at 10:03:41AM +0000, Borislav Petkov wrote:
> On Wed, Jul 31, 2019 at 02:05:54AM +0300, Kirill A. Shutemov wrote:
> > Add support for a new instruction MOVDIR64B. The instruction moves
> > 64-bytes as direct-store with 64-byte write atomicity from source memory
> > address to destination memory address.
> >
> > MOVDIR64B requires the destination address to be 64-byte aligned. No
> > alignment restriction is enforced for source operand.
> >
> > See Intel Software Developer’s Manual for more information on the
> > instruction.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > ---
> >
> > Several upcoming patchsets will make use of the helper.
>
> ... so why aren't you sending it together with its first user?
We are not yet sure which patchset will hit upstream first. I thought it
would be logistically easier to get the patch upstream on its own.
But if you prefer the patch to be submitted along with the first user, we
can definately do this.
Jing, are you okay with this?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2019-08-01 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 23:05 [PATCH] x86/asm: Add support for MOVDIR64B instruction Kirill A. Shutemov
2019-07-31 0:24 ` jinglin
2019-08-01 10:03 ` Borislav Petkov
2019-08-01 11:03 ` Kirill A. Shutemov [this message]
2019-08-01 19:20 ` Luck, Tony
2019-08-01 19:36 ` Borislav Petkov
2019-08-01 19:43 Alexey Dobriyan
2019-08-01 19:49 ` Luck, Tony
2019-08-01 20:28 ` Kirill A. Shutemov
2019-08-01 20:36 ` Borislav Petkov
2019-08-01 22:06 ` Luck, Tony
2019-08-02 14:40 ` Borislav Petkov
2019-08-05 17:50 ` Lin, Jing
2019-08-01 21:53 ` Alexey Dobriyan
2019-08-02 8:15 ` Peter Zijlstra
2019-08-02 12:58 ` Kirill A. Shutemov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190801110358.jmfd2cy7s277j6qv@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jing.lin@intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).