From: Joerg Roedel <jroedel@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: ***UNCHECKED*** Re: Re: Re: [PATCH v7 0/5] NX 0
Date: Tue, 29 Oct 2019 13:31:57 +0100 [thread overview]
Message-ID: <20191029123157.GG838@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1910291158530.5242@nanos.tec.linutronix.de>
On Tue, Oct 29, 2019 at 12:00:10PM +0100, speck for Thomas Gleixner wrote:
> Not a conflict, but 3/5 needs an extra delta patch on top AFAICT. Paolo said he
> would send a v8. I'll have a look later today.
Ah okay, Paolo wanted to include the fix for the !npt/!ept cases (where
efer.nx was clear for the guest at early boot so that the nx-pages
caused rsvd-bit faults).
But he sent the fix separatly to the public already here:
https://lore.kernel.org/lkml/20191027152323.24326-1-pbonzini@redhat.com/
I guess he plans to send it upstream before the CRD date, Paolo?
Regards,
Joerg
next prev parent reply other threads:[~2019-10-29 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 7:34 [MODERATED] [PATCH v7 0/5] NX 0 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 1/5] NX 1 Paolo Bonzini
2019-10-24 8:57 ` [MODERATED] " Paolo Bonzini
2019-10-24 14:21 ` Tyler Hicks
2019-10-24 14:25 ` Paolo Bonzini
2019-10-24 15:01 ` Tyler Hicks
2019-10-24 7:34 ` [MODERATED] [PATCH v7 2/5] NX 2 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 3/5] NX 3 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 4/5] NX 4 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 5/5] NX 5 Paolo Bonzini
2019-10-28 12:08 ` [PATCH v7 0/5] NX 0 Thomas Gleixner
2019-10-28 16:02 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 8:51 ` Thomas Gleixner
2019-10-29 9:39 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 11:00 ` Thomas Gleixner
2019-10-29 12:31 ` Joerg Roedel [this message]
2019-10-29 15:35 ` ***UNCHECKED*** " Thomas Gleixner
2019-10-29 15:42 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 16:50 ` Paolo Bonzini
2019-10-31 21:00 ` [MODERATED] Re: ***UNCHECKED*** " Tyler Hicks
2019-10-31 22:13 ` Paolo Bonzini
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=20191029123157.GG838@suse.de \
--to=jroedel@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.