kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Binbin Wu <binbin.wu@linux.intel.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
	"Li, Xiaoyao" <xiaoyao.li@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"seanjc@google.com" <seanjc@google.com>
Cc: "mikko.ylinen@linux.intel.com" <mikko.ylinen@linux.intel.com>,
	"Gao, Chao" <chao.gao@intel.com>,
	"Huang, Kai" <kai.huang@intel.com>,
	"Chatre, Reinette" <reinette.chatre@intel.com>,
	"Lindgren, Tony" <tony.lindgren@intel.com>,
	"Zhao, Yan Y" <yan.y.zhao@intel.com>,
	"Hunter, Adrian" <adrian.hunter@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Yamahata, Isaku" <isaku.yamahata@intel.com>
Subject: Re: [PATCH 1/2] KVM: TDX: Handle TDG.VP.VMCALL<GetQuote>
Date: Tue, 15 Apr 2025 09:55:28 +0800	[thread overview]
Message-ID: <dad54712-8576-47d0-8ef0-8928acb14d6c@linux.intel.com> (raw)
In-Reply-To: <b644c042602cac5096b32c0d61e5a2f7acdbcfa0.camel@intel.com>



On 4/15/2025 9:51 AM, Edgecombe, Rick P wrote:
> On Tue, 2025-04-15 at 09:49 +0800, Xiaoyao Li wrote:
>>> diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
>>> index c6988e2c68d5..eca86b7f0cbc 100644
>>> --- a/include/uapi/linux/kvm.h
>>> +++ b/include/uapi/linux/kvm.h
>>> @@ -178,6 +178,7 @@ struct kvm_xen_exit {
>>>     #define KVM_EXIT_NOTIFY           37
>>>     #define KVM_EXIT_LOONGARCH_IOCSR  38
>>>     #define KVM_EXIT_MEMORY_FAULT     39
>>> +#define KVM_EXIT_TDX_GET_QUOTE    41
>> Number 40 is skipped and I was told internally the reason is mentioned
>> in cover letter
>>
>>       Note that AMD has taken 40 for KVM_EXIT_SNP_REQ_CERTS in the
>>       patch [4] under review, to avoid conflict, use number 41 for
>>       KVM_EXIT_TDX_GET_QUOTE and number 42 for
>>       KVM_EXIT_TDX_SETUP_EVENT_NOTIFY.
>>
>> I think we shouldn't give up number 40 unless this series depends on AMD
>> one or it's agreement that AMD one will be queued/merged earlier.
> Yes, if this patch needed to sit in kvm-coco-queue with AMD patches for awhile
> it might make sense. But it sounds like the plan is to include it in base
> support.
Right, now it seems that this patch could probably win the race upstream,
will use number 40 for KVM_EXIT_TDX_GET_QUOTE in the next version if no
objections.


  reply	other threads:[~2025-04-15  1:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  0:15 [PATCH 0/2] TDX attestation support Binbin Wu
2025-04-02  0:15 ` [PATCH 1/2] KVM: TDX: Handle TDG.VP.VMCALL<GetQuote> Binbin Wu
2025-04-02  0:53   ` Huang, Kai
2025-04-02  8:58     ` Huang, Kai
2025-04-02 12:53     ` Binbin Wu
2025-04-02 13:16       ` Binbin Wu
2025-04-02 22:05         ` Huang, Kai
2025-04-02 22:00       ` Huang, Kai
2025-04-08  2:35         ` Binbin Wu
2025-04-09 13:49       ` Sean Christopherson
2025-04-10  0:06         ` Binbin Wu
2025-04-10  0:15         ` Huang, Kai
2025-04-02 22:19   ` Huang, Kai
2025-04-07  1:00     ` Binbin Wu
2025-04-15  1:49   ` Xiaoyao Li
2025-04-15  1:51     ` Edgecombe, Rick P
2025-04-15  1:55       ` Binbin Wu [this message]
2025-04-02  0:15 ` [PATCH 2/2] KVM: TDX: Handle TDG.VP.VMCALL<SetupEventNotifyInterrupt> Binbin Wu
2025-04-02  0:20 ` [PATCH 0/2] TDX attestation support Edgecombe, Rick P
2025-04-11  1:42   ` Binbin Wu

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=dad54712-8576-47d0-8ef0-8928acb14d6c@linux.intel.com \
    --to=binbin.wu@linux.intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=chao.gao@intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kai.huang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikko.ylinen@linux.intel.com \
    --cc=pbonzini@redhat.com \
    --cc=reinette.chatre@intel.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=tony.lindgren@intel.com \
    --cc=xiaoyao.li@intel.com \
    --cc=yan.y.zhao@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 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).