From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Kai Huang <kai.huang@intel.com>,
Chang Seok Bae <chang.seok.bae@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kas@kernel.org" <kas@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v2 5/6] KVM: x86: Track available/dirty register masks as "unsigned long" values
Date: Wed, 15 Apr 2026 20:20:45 +0800 [thread overview]
Message-ID: <e11d37d0-a143-44e7-b76d-bf2d5b386d16@intel.com> (raw)
In-Reply-To: <c40b5057-4df5-44ba-93c9-5c46696de765@intel.com>
On 4/15/2026 7:29 PM, Xiaoyao Li wrote:
>> Note that updating only the "available" masks is wrong, as TDX needs
>> to marshall
>> written registers back to their correct location.
>
> In what case it needs to marshall written registers back? Can you
> elaborate?
Sorry that I asked a silly question. I mistakenly thought TDVMCALL for
instructions (like, CPUID, RDMSR, WRMSR) use the same output register as
the x86 instructions. After checking the TDX GHCI, obviously I'm wrong.
But I don't understand what's is wrong regarding "updating only the
"available" masks". Or what is missing for "marshall written registers
back to their correct location"?
next prev parent reply other threads:[~2026-04-15 12:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 22:42 [PATCH v2 0/6] KVM: x86: Reg cleanups / prep work for APX Sean Christopherson
2026-04-09 22:42 ` [PATCH v2 1/6] KVM: x86: Add dedicated storage for guest RIP Sean Christopherson
2026-04-10 18:43 ` Chang S. Bae
2026-04-14 12:31 ` Xiaoyao Li
2026-04-14 13:59 ` Chang S. Bae
2026-04-14 15:37 ` Sean Christopherson
2026-04-15 1:28 ` Xiaoyao Li
2026-04-15 16:06 ` Sean Christopherson
2026-04-09 22:42 ` [PATCH v2 2/6] KVM: x86: Drop the "EX" part of "EXREG" to avoid collision with APX Sean Christopherson
2026-04-13 11:23 ` Huang, Kai
2026-04-09 22:42 ` [PATCH v2 3/6] KVM: nVMX: Do a bitwise-AND of regs_avail when switching active VMCS Sean Christopherson
2026-04-09 22:42 ` [PATCH v2 4/6] KVM: x86: Add wrapper APIs to reset dirty/available register masks Sean Christopherson
2026-04-09 22:42 ` [PATCH v2 5/6] KVM: x86: Track available/dirty register masks as "unsigned long" values Sean Christopherson
2026-04-13 11:24 ` Huang, Kai
2026-04-13 11:28 ` Huang, Kai
2026-04-13 14:54 ` Sean Christopherson
2026-04-13 23:03 ` Huang, Kai
2026-04-14 2:12 ` Xiaoyao Li
2026-04-14 14:04 ` Sean Christopherson
2026-04-15 11:29 ` Xiaoyao Li
2026-04-15 12:20 ` Xiaoyao Li [this message]
2026-04-15 16:05 ` Sean Christopherson
2026-04-14 15:48 ` Sean Christopherson
2026-04-14 22:21 ` Huang, Kai
2026-04-09 22:42 ` [PATCH v2 6/6] KVM: x86: Use a proper bitmap for tracking available/dirty registers Sean Christopherson
2026-04-13 11:31 ` [PATCH v2 0/6] KVM: x86: Reg cleanups / prep work for APX 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=e11d37d0-a143-44e7-b76d-bf2d5b386d16@intel.com \
--to=xiaoyao.li@intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kai.huang@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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