From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: mingo@elte.hu, tglx@linutronix.de,
xen-devel <xen-devel@lists.xenproject.org>,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2] x86-64/Xen: eliminate W+X mappings
Date: Mon, 18 Dec 2017 12:50:20 +0100 [thread overview]
Message-ID: <903b2ec7-8338-658f-665b-41719e82387b@suse.com> (raw)
In-Reply-To: <5A37B0770200007800198130@suse.com>
On 18/12/17 12:11, Jan Beulich wrote:
> A few thousand such pages are usually left around due to the re-use of
> L1 tables having been provided by the hypervisor (Dom0) or tool stack
> (DomU). Set NX in the direct map variant, which needs to be done in L2
> due to the dual use of the re-used L1s.
>
> For x86_configure_nx() to actually do what it is supposed to do, call
> get_cpu_cap() first. This was broken by commit 4763ed4d45 ("x86, mm:
> Clean up and simplify NX enablement") when switching away from the
> direct EFER read.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> v2: Adjust comment style and indentation.
> ---
> While I certainly dislike the added header inclusion to obtain the
> prototype for get_cpu_cap(), I couldn't find a better alternative. I'm
> open to suggestions.
Move the prototype to arch/x86/include/asm/cpu.h ?
With that fixed (or without it in case the x86 maintainers don't like
the prototype to be moved):
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
next parent reply other threads:[~2017-12-18 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5A2FAEB802000055000F9D66@suse.com>
[not found] ` <5A2FBE540200007800196B52@suse.com>
[not found] ` <5A37B0770200007800198130@suse.com>
2017-12-18 11:50 ` Juergen Gross [this message]
[not found] <5A2FAEB802000055000F9D66@prv-mh.provo.novell.com>
2017-12-12 10:32 ` [PATCH 2/2] " Jan Beulich
2017-12-18 11:11 ` [PATCH v2] " Jan Beulich
2017-12-18 12:28 ` Ingo Molnar
2017-12-18 15:52 ` Joe Perches
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=903b2ec7-8338-658f-665b-41719e82387b@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®