From: "Luck, Tony" <tony.luck@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, "Lin, Jing" <jing.lin@intel.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@intel.com>,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] x86/asm: Add support for MOVDIR64B instruction
Date: Thu, 1 Aug 2019 12:20:30 -0700 [thread overview]
Message-ID: <20190801192030.GA11781@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20190801095928.GA32138@nazgul.tnic>
On Thu, Aug 01, 2019 at 12:03:41PM +0200, Borislav Petkov wrote:
> On Wed, Jul 31, 2019 at 02:05:54AM +0300, Kirill A. Shutemov wrote:
> > Several upcoming patchsets will make use of the helper.
>
> ... so why aren't you sending it together with its first user?
Just to get another of the non-controversial bits out of the
way before the main course arrives.
Note that the CPUFEATURE bit for MOVDIR64B already went upstream
in v4.20:
ace6485a0326 ("x86/cpufeatures: Enumerate MOVDIR64B instruction")
-Tony
next prev parent reply other threads:[~2019-08-01 19:20 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
2019-08-01 19:20 ` Luck, Tony [this message]
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=20190801192030.GA11781@agluck-desk2.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jing.lin@intel.com \
--cc=kirill.shutemov@linux.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=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).