From: Jarkko Sakkinen <jarkko@kernel.org>
To: Kai Huang <kai.huang@intel.com>
Cc: dave.hansen@linux.intel.com, linux-sgx@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
seanjc@google.com, pbonzini@redhat.com,
haitao.huang@linux.intel.com
Subject: Re: [PATCH v2] x86/sgx: Allow exposing EDECCSSA user leaf function to KVM guest
Date: Thu, 25 Aug 2022 06:27:46 +0300 [thread overview]
Message-ID: <YwbsMqhnbsuoqwKv@kernel.org> (raw)
In-Reply-To: <YwbrywL9S+XlPzaX@kernel.org>
On Thu, Aug 25, 2022 at 06:26:06AM +0300, Jarkko Sakkinen wrote:
> Nit: shouldn't be this be x86/kvm?
Also, why don't you make one patch set with Dave's patch
included.
BR, Jarkko
next prev parent reply other threads:[~2022-08-25 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:38 [PATCH v2] x86/sgx: Allow exposing EDECCSSA user leaf function to KVM guest Kai Huang
2022-08-25 3:26 ` Jarkko Sakkinen
2022-08-25 3:27 ` Jarkko Sakkinen [this message]
2022-08-25 15:19 ` Sean Christopherson
2022-08-25 15:44 ` Dave Hansen
2022-08-25 15:49 ` Sean Christopherson
2022-08-25 19:27 ` Jarkko Sakkinen
2022-08-29 1:37 ` Huang, Kai
2022-08-29 1:36 ` Huang, Kai
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=YwbsMqhnbsuoqwKv@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox