qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Xiaoyao Li" <xiaoyao.li@intel.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Eduardo Habkost <eduardo@habkost.net>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 1/2] i386/tdx: Fix build on 32-bit host
Date: Fri, 6 Jun 2025 11:38:25 +0200	[thread overview]
Message-ID: <d0eb5075-0f68-4430-ae0e-fb41646f2734@linaro.org> (raw)
In-Reply-To: <fde03bbf-415a-466f-a3cd-fac4f952c531@intel.com>

On 6/6/25 11:28, Xiaoyao Li wrote:
> On 6/6/2025 5:19 PM, Philippe Mathieu-Daudé wrote:
>> On 6/6/25 10:49, Xiaoyao Li wrote:
>>> On 6/3/2025 10:53 PM, Paolo Bonzini wrote:
>>>> On 6/3/25 13:26, Philippe Mathieu-Daudé wrote:
>>>>> On 3/6/25 05:04, Xiaoyao Li wrote:
>>>>>> On 6/3/2025 1:31 AM, Cédric Le Goater wrote:
>>>>>>> Use PRI formats where required and fix pointer cast.
>>>>>>
>>>>>> Maybe we can make 32-bit build exclusive with CONFIG_TDX? since 
>>>>>> TDX is not supported on 32-bit host.
>>>>>
>>>>> Yes please!
>>>>
>>>> No objections, but I'm still applying these first to fix the build.
>>>
>>> Can anyone guide how to implement it? Or directly help cook a patch?
>>>
>>> I'm struggling to learn the 32-bit build stuff and create a 32-bit 
>>> environment.
>>
>> -- >8 --
>> diff --git a/hw/i386/Kconfig b/hw/i386/Kconfig
>> index eb65bda6e07..b5970f9a1f3 100644
>> --- a/hw/i386/Kconfig
>> +++ b/hw/i386/Kconfig
>> @@ -13,7 +13,7 @@ config SGX
>>   config TDX
>>       bool
>>       select X86_FW_OVMF
>> -    depends on KVM
>> +    depends on KVM && !I386
>>
>> ---
> 
> CONFIG_X86_64 selects I386 in target/i386/Kconfig, so above change will 
> just leads to CONFIG_TDX always being 0.
> 
> config X86_64
>      bool
>      select I386

Doh. We could expose TARGET_LONG_BITS to Kconfig (see commit 
bae3e3a5c6b, "meson: make target endianneess available to Kconfig"),
but there is likely a clever way.


  reply	other threads:[~2025-06-06  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 17:30 [PATCH 0/2] i386/tdx: Fix build on 32-bit host Cédric Le Goater
2025-06-02 17:31 ` [PATCH 1/2] " Cédric Le Goater
2025-06-03  3:04   ` Xiaoyao Li
2025-06-03 11:26     ` Philippe Mathieu-Daudé
2025-06-03 14:53       ` Paolo Bonzini
2025-06-06  8:49         ` Xiaoyao Li
2025-06-06  9:19           ` Philippe Mathieu-Daudé
2025-06-06  9:28             ` Xiaoyao Li
2025-06-06  9:38               ` Philippe Mathieu-Daudé [this message]
2025-06-02 17:31 ` [PATCH 2/2] i386/tdvf: " Cédric Le Goater
2025-06-03 14:52 ` [PATCH 0/2] i386/tdx: " Paolo Bonzini

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=d0eb5075-0f68-4430-ae0e-fb41646f2734@linaro.org \
    --to=philmd@linaro.org \
    --cc=clg@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=xiaoyao.li@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).