All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v25] x86/sgx: Move SGX sub-feature bits to their own word
Date: Thu, 2 Jan 2020 18:54:12 +0200	[thread overview]
Message-ID: <20200102165412.GA17637@linux.intel.com> (raw)
In-Reply-To: <20191220230829.24047-1-sean.j.christopherson@intel.com>

On Fri, Dec 20, 2019 at 03:08:29PM -0800, Sean Christopherson wrote:
> As requested by Boris, move the CPUID 0x12 features to their own word in
> cpufeatures.
> 
> This can be squashed cleanly with commit c3eac55d3882 ("x86/cpufeatures:
> x86/msr: Add Intel SGX hardware bits"), replacing paragraph
> 
>   Remap CPUID.(EAX=12H, ECX=0) bits to the Linux fake CPUID 8 in order to
>   conserve some space. Keep the bit positions intact because KVM requires
>   this. Reserve bits 0-7 for SGX in order to maintain this invariant also
>   when new SGX specific feature bits get added.
> 
> with
> 
>   Add the SGX sub-features in a new word even though only two bits will be
>   used in the immediate future.  KVM support for SGX is expected in the
>   not-too-distant future, and having a dedicated feature word allows KVM
>   to include SGX sub-features in its reserve-cpuid lookup table, e.g. to
>   easily query guest CPUID capabilities.
> 
> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>

Thank you. I merged this and added changelog entry.

/Jarkko

      reply	other threads:[~2020-01-02 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 23:08 [PATCH for_v25] x86/sgx: Move SGX sub-feature bits to their own word Sean Christopherson
2020-01-02 16:54 ` Jarkko Sakkinen [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=20200102165412.GA17637@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=sean.j.christopherson@intel.com \
    /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.