From: Junaid Shahid <junaids@google.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v5 6/8] NX 6
Date: Wed, 9 Oct 2019 15:52:14 -0700 [thread overview]
Message-ID: <8ff30427-c133-ca67-7da1-418069e2797e@google.com> (raw)
In-Reply-To: <973c85efc96c05cba9ddfc2f5bf53c9482801924.camel@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
On 10/9/19 3:42 PM, speck for Ben Hutchings wrote:
>
> I've started trying to backport the NX patches to stable branches, and
> I think I can take them back as far as 4.9.
>
> However, kvm_mmu_zap_all() is a relatively new addition and looks hard
> to backport. I intend to make the nx_huge_pages parameter read-only
> (0444 permissions) and delete this "if (new_val != old_val)" block.
> Does that seem reasonable?
>
You could also just replace the call to kvm_mmu_zap_all() with kvm_mmu_invalidate_zap_all_pages(), which is present as far back as 3.11
Thanks,
Junaid
next prev parent reply other threads:[~2019-10-09 22:52 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 [this message]
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
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=8ff30427-c133-ca67-7da1-418069e2797e@google.com \
--to=junaids@google.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).