Linux Confidential Computing Development
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosry@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Lisa Wang <wyihan@google.com>,
	Andrew Jones <ajones@ventanamicro.com>,
	 Ackerley Tng <ackerleytng@google.com>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	 Chao Gao <chao.gao@intel.com>,
	Chenyi Qiang <chenyi.qiang@intel.com>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	Erdem Aktas <erdemaktas@google.com>,
	 Ira Weiny <ira.weiny@intel.com>,
	Isaku Yamahata <isaku.yamahata@intel.com>,
	 Kiryl Shutsemau <kas@kernel.org>,
	linux-kselftest@vger.kernel.org,
	 Paolo Bonzini <pbonzini@redhat.com>,
	"Pratik R. Sampat" <pratikrajesh.sampat@amd.com>,
	 Reinette Chatre <reinette.chatre@intel.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	 Roger Wang <runanwang@google.com>,
	Ryan Afranji <afranji@google.com>,
	 Sagi Shahar <sagis@google.com>, Shuah Khan <shuah@kernel.org>,
	Oliver Upton <oupton@kernel.org>,
	 Jeremiah McReynolds <jmcrey@google.com>,
	kvm@vger.kernel.org, linux-coco@lists.linux.dev,
	 linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v13 07/22] KVM: selftests: Introduce structures for TDX guest boot parameters
Date: Thu, 28 May 2026 19:25:14 +0000	[thread overview]
Message-ID: <ahiVwxm2kD0TVqxj@google.com> (raw)
In-Reply-To: <CAO9r8zMaiGL8v=f72EAwWbwofoUHOkH8r6Se22k2TVxnUCQLOQ@mail.gmail.com>

On Fri, May 22, 2026 at 04:50:07PM -0700, Yosry Ahmed wrote:
> > > Sean, is this the preferred way to expose offsets to asm files (or asm
> > > code blocks) -- as opposed to say using .equ [*]?
> >
> > For actual .S assembly, yes.  For inline asm, maybe?  If it looks prettier, go
> > for it.
> >
> > > If yes, I can rework my nVMX GPR fixes to use the same approach for
> > > register offsets. I wonder if the non-TDX part of this patch (i.e.
> > > Makefile stuff) can be split, then patch 6 and the Makefile stuff can
> > > land independently and allow development on top.
> > >
> > > I can also split them out and include them in the next version of my
> > > series, then whichever series lands first will land the offsets
> > > support.
> > >
> > > WDYT?
> >
> > Hmm, I'd say keep your series as-is for now.  The OFFSET() infrastructure really
> > shines for proper assembly.  For what you're doing, AFAICT it's only marginally
> > better.  So I don't think it's worth juggling dependencies to use it right away,
> > we can always convert if/when the TDX series lands the fancy stuff.
> 
> Ack. We can do the switch later like you say.

I take this back. My series builds with the internal toolchain, but not
when I just use make with LLVM. Probably different compiler versions or
build options, but the fact the .equ thing doesn't always work means I
can't use it.

I would paste the error here, but the compiler literally spits out
incomprehensible garbage.

Lisa, if you will send a new version of this series for other reasons,
do you mind splitting out the non-TDX parts of this patch? Ideally we'd
have 1-2 patches that introduce the OFFSET() infrastructure without any
TDX parts, which should make it easier to pick up separately or include
with other series.

If a new version won't be needed anyway, I will just wait for this to
land before refreshing my series on top.

  parent reply	other threads:[~2026-05-28 19:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 23:16 [PATCH v13 00/22] TDX KVM selftests Lisa Wang
2026-05-21 23:16 ` [PATCH v13 01/22] KVM: selftests: Add macros to simplify creating VM shapes for non-default types Lisa Wang
2026-05-21 23:16 ` [PATCH v13 02/22] KVM: selftests: Update kvm_init_vm_address_properties() for TDX Lisa Wang
2026-05-21 23:16 ` [PATCH v13 03/22] KVM: selftests: Initialize the TDX VM Lisa Wang
2026-05-21 23:16 ` [PATCH v13 04/22] KVM: selftests: TDX: Use KVM_TDX_CAPABILITIES to validate TDs' attribute configuration Lisa Wang
2026-05-21 23:16 ` [PATCH v13 05/22] KVM: selftests: Expose segment definitions to assembly files Lisa Wang
2026-05-21 23:16 ` [PATCH v13 06/22] tools: include: Add kbuild.h for assembly structure offsets Lisa Wang
2026-05-21 23:16 ` [PATCH v13 07/22] KVM: selftests: Introduce structures for TDX guest boot parameters Lisa Wang
2026-05-22 17:43   ` Yosry Ahmed
2026-05-22 23:05     ` Sean Christopherson
     [not found]       ` <CAO9r8zMaiGL8v=f72EAwWbwofoUHOkH8r6Se22k2TVxnUCQLOQ@mail.gmail.com>
2026-05-28 19:25         ` Yosry Ahmed [this message]
2026-05-21 23:16 ` [PATCH v13 08/22] KVM: selftests: Add TDX boot code Lisa Wang
2026-05-21 23:16 ` [PATCH v13 09/22] KVM: selftests: Expose functions to get default sregs values Lisa Wang
2026-05-21 23:16 ` [PATCH v13 10/22] KVM: selftests: Set up TDX boot code region Lisa Wang
2026-05-21 23:16 ` [PATCH v13 11/22] KVM: selftests: Set up TDX boot parameters region Lisa Wang
2026-05-21 23:16 ` [PATCH v13 12/22] KVM: selftests: Back the first memory region with guest_memfd for TDX Lisa Wang
2026-05-21 23:16 ` [PATCH v13 13/22] KVM: selftests: Set first memory region as shared if guest_memfd Lisa Wang
2026-05-21 23:16 ` [PATCH v13 14/22] KVM: selftests: Expose function to allocate vCPU stack Lisa Wang
2026-05-21 23:16 ` [PATCH v13 15/22] KVM: selftests: Call KVM_TDX_INIT_VCPU when creating a new TDX vcpu Lisa Wang
2026-05-21 23:16 ` [PATCH v13 16/22] KVM: selftests: Load per-vCPU guest stack in TDX boot parameters Lisa Wang
2026-05-21 23:16 ` [PATCH v13 17/22] KVM: selftests: Set entry point for TDX guest code Lisa Wang
2026-05-21 23:16 ` [PATCH v13 18/22] KVM: selftests: Add helpers to init TDX memory and finalize VM Lisa Wang
2026-05-21 23:17 ` [PATCH v13 19/22] KVM: selftests: Finalize TD memory as part of kvm_arch_vm_finalize_vcpus Lisa Wang
2026-05-21 23:17 ` [PATCH v13 20/22] KVM: selftests: Implement MMIO WRITE for the TDX VM Lisa Wang
2026-05-21 23:17 ` [PATCH v13 21/22] KVM: selftests: Add ucall support for TDX Lisa Wang
2026-05-21 23:17 ` [PATCH v13 22/22] KVM: selftests: Add TDX lifecycle test Lisa Wang

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=ahiVwxm2kD0TVqxj@google.com \
    --to=yosry@kernel.org \
    --cc=ackerleytng@google.com \
    --cc=afranji@google.com \
    --cc=ajones@ventanamicro.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=chao.gao@intel.com \
    --cc=chenyi.qiang@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=erdemaktas@google.com \
    --cc=ira.weiny@intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=jmcrey@google.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=oupton@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pratikrajesh.sampat@amd.com \
    --cc=reinette.chatre@intel.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=runanwang@google.com \
    --cc=sagis@google.com \
    --cc=seanjc@google.com \
    --cc=shuah@kernel.org \
    --cc=wyihan@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