public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/sgx for v5.13
Date: Mon, 26 Apr 2021 16:22:15 +0000	[thread overview]
Message-ID: <YIbot8szBpbsSGuw@google.com> (raw)
In-Reply-To: <YIaWh9VSEMQnn5E2@zn.tnic>

On Mon, Apr 26, 2021, Borislav Petkov wrote:
> Hi Linus,
> 
> please pull the SGX pile of updates for v5.13.
> 
> Thx.
> 
> ---
> 
> The following changes since commit 1e28eed17697bcf343c6743f0028cc3b5dd88bf0:
> 
>   Linux 5.12-rc3 (2021-03-14 14:41:02 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_sgx_for_v5.13
> 
> for you to fetch changes up to 523caed9efbb049339706b124185c9358c1b6477:
> 
>   x86/sgx: Mark sgx_vepc_vm_ops static (2021-04-12 19:48:32 +0200)
> 
> ----------------------------------------------------------------
> Add the guest side of SGX support in KVM guests. Work by Sean

This is all host side code, there are no guest specific changes required.  Maybe
"Add the non-KVM kernel bits for SGX support in KVM guests."

Thanks!

> Christopherson, Kai Huang and Jarkko Sakkinen. Along with the usual
> fixes, cleanups and improvements.
> 
> ----------------------------------------------------------------
> Dave Hansen (1):
>       selftests/sgx: Improve error detection and messages
> 
> Ira Weiny (1):
>       x86/sgx: Remove unnecessary kmap() from sgx_ioc_enclave_init()
> 
> Jarkko Sakkinen (3):
>       x86/sgx: Replace section->init_laundry_list with sgx_dirty_page_list
>       x86/sgx: Add a basic NUMA allocation scheme to sgx_alloc_epc_page()
>       x86/sgx: Do not update sgx_nr_free_pages in sgx_setup_epc_section()
> 
> Kai Huang (4):
>       x86/cpufeatures: Make SGX_LC feature bit depend on SGX bit
>       x86/sgx: Wipe out EREMOVE from sgx_free_epc_page()
>       x86/sgx: Initialize virtual EPC driver even when SGX driver is disabled
>       x86/sgx: Add helper to update SGX_LEPUBKEYHASHn MSRs
> 
> Sean Christopherson (10):
>       x86/cpufeatures: Add SGX1 and SGX2 sub-features
>       x86/sgx: Add SGX_CHILD_PRESENT hardware error code
>       x86/sgx: Introduce virtual EPC for use by KVM guests
>       x86/cpu/intel: Allow SGX virtualization without Launch Control support
>       x86/sgx: Expose SGX architectural definitions to the kernel
>       x86/sgx: Move ENCLS leaf definitions to sgx.h
>       x86/sgx: Add SGX2 ENCLS leaf definitions (EAUG, EMODPR and EMODT)
>       x86/sgx: Add encls_faulted() helper
>       x86/sgx: Add helpers to expose ECREATE and EINIT to KVM
>       x86/sgx: Move provisioning device creation out of SGX driver
> 
> Tianjia Zhang (1):
>       selftests/sgx: Use getauxval() to simplify test code
> 
> Wei Yongjun (1):
>       x86/sgx: Mark sgx_vepc_vm_ops static

  reply	other threads:[~2021-04-26 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 10:31 [GIT PULL] x86/sgx for v5.13 Borislav Petkov
2021-04-26 16:22 ` Sean Christopherson [this message]
2021-04-26 16:53   ` Linus Torvalds
2021-04-26 16:40 ` pr-tracker-bot

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=YIbot8szBpbsSGuw@google.com \
    --to=seanjc@google.com \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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