From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] i386: Build SEV only for 64-bit target
Date: Wed, 16 Jul 2025 10:56:52 +0100 [thread overview]
Message-ID: <aHd3ZBiAaHMqQ6qb@redhat.com> (raw)
In-Reply-To: <84bf8968-aa46-4eb0-b18f-a0468942da82@redhat.com>
On Wed, Jul 16, 2025 at 11:36:48AM +0200, Cédric Le Goater wrote:
> On 7/16/25 11:28, Daniel P. Berrangé wrote:
> > On Wed, Jul 16, 2025 at 09:15:54AM +0200, Cédric Le Goater wrote:
> > > Recent changes broke build on 32-bit host. Since there is no 32-bit
> > > support, restrict SEV to 64-bit.
> > >
> > > Signed-off-by: Cédric Le Goater <clg@redhat.com>
> > > ---
> > > hw/i386/Kconfig | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >
> > Matches what we just did for TDX too.
>
> What about SGX ?
Our SGX features only require kernel support.
The SGX userspace SDK can build for 32 & 64 bit, though in Fedora/RHEL I
will only build it for 64-bit, but that's not relevant for QEMU's needs
anyway.
Ultimately we're dropping 32-bit host support for QEMU in general at the
end of this year, so we don't need to go out of our way to selectively
drop things before then unless they're giving us trouble today.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-07-16 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 7:15 [PATCH] i386: Build SEV only for 64-bit target Cédric Le Goater
2025-07-16 9:28 ` Daniel P. Berrangé
2025-07-16 9:36 ` Cédric Le Goater
2025-07-16 9:56 ` Daniel P. Berrangé [this message]
2025-07-17 5:23 ` Xiaoyao Li
2025-07-28 17:25 ` Cédric Le Goater
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=aHd3ZBiAaHMqQ6qb@redhat.com \
--to=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.