From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v5 1/8] NX 1
Date: Wed, 9 Oct 2019 18:33:55 -0700 [thread overview]
Message-ID: <20191010013355.GF11840@guptapadev.amr> (raw)
In-Reply-To: <88ac4542fa0f8d71d0ff672cc4693dcaec73db74.camel@decadent.org.uk>
On Thu, Oct 10, 2019 at 12:01:21AM +0100, speck for Ben Hutchings wrote:
> On Mon, 2019-07-01 at 15:52 +0200, speck for Paolo Bonzini wrote:
> > From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> > Subject: [PATCH 1/8] x86: Add ITLB_MULTIHIT bug infrastructure
> [...]
> > --- a/arch/x86/include/asm/cpufeatures.h
> > +++ b/arch/x86/include/asm/cpufeatures.h
> > @@ -385,5 +385,6 @@
> > #define X86_BUG_L1TF X86_BUG(18) /* CPU is affected by L1 Terminal Fault */
> > #define X86_BUG_MDS X86_BUG(19) /* CPU is affected by Microarchitectural data sampling */
> > #define X86_BUG_MSBDS_ONLY X86_BUG(20) /* CPU is only affected by the MSDBS variant of BUG_MDS */
> > +#define X86_BUG_ITLB_MULTIHIT X86_BUG(21) /* CPU may incur MCE during certain page attribute changes */
> [...]
>
> So this is now going to need to be renumbered after X86_BUG_SWAPGS.
> But the TAA series also allocates the next bug flag here.
>
> Then in other places there are textual conflicts between the two series
> due to insertions in the same place.
>
> I believe both of the issues these are addressing have the same embargo
> date, so it would be helpful to backporters if you could decide which
> fix belongs first, even if they continue to be developed as separate
> branches for now. (So far I've found it easier to apply NX before
> TAA.)
TAA is more recent than NX, so I guess NX should be applied before TAA.
#define X86_BUG_SWAPGS X86_BUG(21)
#define X86_BUG_ITLB_MULTIHIT X86_BUG(22)
#define X86_BUG_TAA X86_BUG(23)
Thanks,
Pawan
prev parent reply other threads:[~2019-10-10 1:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1561989149-17323-1-git-send-email-pbonzini@redhat.com>
[not found] ` <1561989149-17323-9-git-send-email-pbonzini@redhat.com>
[not found] ` <8eab605b-df0e-74d0-e448-986149edf33e@redhat.com>
2019-10-02 20:38 ` [MODERATED] Re: [PATCH v5 8/8] NX 8 Pawan Gupta
2019-10-02 20:59 ` Paolo Bonzini
2019-10-07 19:45 ` Pawan Gupta
2019-10-09 6:13 ` Paolo Bonzini
2019-10-09 14:41 ` Pawan Gupta
2019-10-09 15:10 ` Paolo Bonzini
2019-10-10 5:53 ` Pawan Gupta
2019-10-10 16:14 ` Paolo Bonzini
2019-10-10 16:50 ` Paolo Bonzini
2019-10-10 17:37 ` Paolo Bonzini
[not found] ` <1561989149-17323-7-git-send-email-pbonzini@redhat.com>
[not found] ` <alpine.DEB.2.21.1907022244530.1802@nanos.tec.linutronix.de>
[not found] ` <4c4447ba-838d-cd85-f35b-468508437b61@intel.com>
[not found] ` <alpine.DEB.2.21.1907022303250.1802@nanos.tec.linutronix.de>
2019-10-09 0:14 ` [MODERATED] Re: [PATCH v5 6/8] NX 6 Pawan Gupta
2019-10-09 22:42 ` Ben Hutchings
2019-10-09 22:52 ` Junaid Shahid
2019-10-09 23:05 ` Ben Hutchings
2019-10-09 23:03 ` Kanth Ghatraju
2019-10-09 23:08 ` Paolo Bonzini
2019-10-09 23:20 ` Kanth Ghatraju
2019-10-31 22:54 ` [MODERATED] NX backports (was Re: [PATCH v5 6/8] NX 6) Paolo Bonzini
2019-10-13 22:11 ` [MODERATED] Re: [PATCH v5 6/8] NX 6 Ben Hutchings
2019-10-14 6:57 ` Paolo Bonzini
2019-11-04 19:43 ` mark gross
2019-11-05 12:28 ` [MODERATED] Re: ***UNCHECKED*** " Michal Hocko
2019-11-05 14:53 ` mark gross
2019-11-05 17:03 ` mark gross
2019-10-14 20:46 ` [MODERATED] " Pawan Gupta
2019-10-15 6:24 ` Greg KH
2019-10-15 10:46 ` Jiri Kosina
2019-10-15 21:19 ` Pawan Gupta
2019-10-17 23:50 ` Ben Hutchings
[not found] ` <1561989149-17323-2-git-send-email-pbonzini@redhat.com>
2019-10-09 23:01 ` [MODERATED] Re: [PATCH v5 1/8] NX 1 Ben Hutchings
2019-10-10 1:33 ` Pawan Gupta [this message]
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=20191010013355.GF11840@guptapadev.amr \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=speck@linutronix.de \
/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).