From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Christopherson, Sean J" <sean.j.christopherson@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"Dock, Deneen T" <deneen.t.dock@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"x86@kernel.org" <x86@kernel.org>,
"kristen@linux.intel.com" <kristen@linux.intel.com>,
"luto@kernel.org" <luto@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [RFC PATCH 09/13] x86/cpufeature: Add detection of KVM XO
Date: Wed, 30 Oct 2019 21:02:02 +0000 [thread overview]
Message-ID: <217403c0f9790c1142b51231d5b4ccfd6d83cf61.camel@intel.com> (raw)
In-Reply-To: <20191030145520.GA14391@linux.intel.com>
On Wed, 2019-10-30 at 07:55 -0700, Sean Christopherson wrote:
> On Tue, Oct 29, 2019 at 04:52:08PM -0700, Edgecombe, Rick P wrote:
> > On Tue, 2019-10-29 at 16:33 -0700, Kees Cook wrote:
> > > On Thu, Oct 03, 2019 at 02:23:56PM -0700, Rick Edgecombe wrote:
> > > > Add a new CPUID leaf to hold the contents of CPUID 0x40000030 EAX to
> > > > detect KVM defined generic VMM features.
> > > >
> > > > The leaf was proposed to allow KVM to communicate features that are
> > > > defined by KVM, but available for any VMM to implement.
>
> This doesn't necessarily work the way you intend, KVM's base CPUID isn't
> guaranteed to be 0x40000000. E.g. KVM supports advertising itself as
> HyperV *and* KVM, in which case KVM's CPUID base will be 0x40000100.
>
> I think you're better off just making this a standard KVM CPUID feature.
> If a different hypervisor wants to reuse guest support as is, it can
> advertise KVM support at a lower priority.
>
Ok, I'm fine going with the simpler KVM CPUID bit. It's not like per-VMM CPUID
leaf meanings are a new scenario with this.
> Note, querying guest CPUID isn't straightforward in either case. But,
> KVM doesn't support disabling its other CPUID-base paravirt features, e.g.
> KVM emulates the kvm_clock MSRs regardless of what userspace advertises to
> the guest. Depending on what changes are required in KVM's MMU, this may
> also need to be a KVM-wide feature, i.e. controlled via a module param.
> > > > Add cpu_feature_enabled() support for features in this leaf (KVM XO),
> > > > and
> > > > a pgtable_kvmxo_enabled() helper similar to pgtable_l5_enabled() so that
> > > > pgtable_kvmxo_enabled() can be used in early code that includes
> > > > arch/x86/include/asm/sparsemem.h.
> > > >
> > > > Lastly, in head64.c detect and this feature and perform necessary
> > > > adjustments to physical_mask.
> > >
> > > Can this be exposed to /proc/cpuinfo so a guest userspace can determine
> > > if this feature is enabled?
> > >
> > > -Kees
> >
> > Is there a good place to expose the information that the PROT_EXEC and
> > !PROT_READ combo creates execute-only memory? This way apps can check one
> > place
> > for the support and not worry about the implementation whether it's this,
> > x86
> > pkeys, arm or other.
>
> I don't think so? Assuming there's no common method, it can be displayed
> in /proc/cpuinfo by adding a synthetic bit, e.g. in Linux-defined word 8
> (virtualization) instead of a dedicated word. The bit can then be
> set if the features exists and is enabled (by the guest).
>
> I'd also name the feature EXEC_ONLY. XO is unnecessarily terse IMO, and
> including "KVM" in the name may be misconstrued as a host KVM feature and
> will be flat out wrong if hardware ever supports XO natively.
Ok, if there is no generic way I guess I'll do this.
next prev parent reply other threads:[~2019-10-30 21:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 21:23 [RFC PATCH 00/13] XOM for KVM guest userspace Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 01/13] kvm: Enable MTRR to work with GFNs with perm bits Rick Edgecombe
2019-10-14 6:47 ` Yu Zhang
2019-10-14 18:44 ` Edgecombe, Rick P
2019-10-03 21:23 ` [RFC PATCH 02/13] kvm: Add support for X86_FEATURE_KVM_XO Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 03/13] kvm: Add XO memslot type Rick Edgecombe
2019-10-04 7:27 ` Paolo Bonzini
2019-10-04 19:06 ` Edgecombe, Rick P
2019-10-06 16:15 ` Paolo Bonzini
2019-10-03 21:23 ` [RFC PATCH 04/13] kvm, vmx: Add support for gva exit qualification Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 05/13] kvm: Add #PF injection for KVM XO Rick Edgecombe
2019-10-04 7:42 ` Paolo Bonzini
2019-10-04 19:11 ` Edgecombe, Rick P
2019-10-03 21:23 ` [RFC PATCH 06/13] kvm: Add KVM_CAP_EXECONLY_MEM Rick Edgecombe
2019-10-04 7:24 ` Paolo Bonzini
2019-10-04 19:11 ` Edgecombe, Rick P
2019-10-03 21:23 ` [RFC PATCH 07/13] kvm: Add docs for KVM_CAP_EXECONLY_MEM Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 08/13] x86/boot: Rename USE_EARLY_PGTABLE_L5 Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 09/13] x86/cpufeature: Add detection of KVM XO Rick Edgecombe
2019-10-29 23:33 ` Kees Cook
2019-10-29 23:52 ` Edgecombe, Rick P
2019-10-30 14:55 ` Sean Christopherson
2019-10-30 21:02 ` Edgecombe, Rick P [this message]
2019-10-03 21:23 ` [RFC PATCH 10/13] x86/mm: Add NR page bit for " Rick Edgecombe
2019-10-04 7:33 ` Paolo Bonzini
2019-10-03 21:23 ` [RFC PATCH 11/13] x86, ptdump: Add NR bit to page table dump Rick Edgecombe
2019-10-03 21:23 ` [RFC PATCH 12/13] mmap: Add XO support for KVM XO Rick Edgecombe
2019-10-04 7:34 ` Paolo Bonzini
2019-10-04 19:12 ` Edgecombe, Rick P
2019-10-03 21:24 ` [RFC PATCH 13/13] x86/Kconfig: Add Kconfig for KVM based XO Rick Edgecombe
2019-10-29 23:36 ` Kees Cook
2019-10-30 0:01 ` Edgecombe, Rick P
2019-10-30 18:36 ` Kees Cook
2019-10-04 7:22 ` [RFC PATCH 00/13] XOM for KVM guest userspace Paolo Bonzini
2019-10-04 19:03 ` Edgecombe, Rick P
2019-10-04 14:56 ` Andy Lutomirski
2019-10-04 20:09 ` Edgecombe, Rick P
2019-10-05 1:33 ` Andy Lutomirski
2019-10-07 18:14 ` Edgecombe, Rick P
2019-10-29 23:40 ` Kees Cook
2019-10-30 0:27 ` Edgecombe, Rick P
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=217403c0f9790c1142b51231d5b4ccfd6d83cf61.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dave.hansen@intel.com \
--cc=deneen.t.dock@intel.com \
--cc=keescook@chromium.org \
--cc=kristen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--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).