From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Dov Murik <dovmurik@linux.ibm.com>,
Michael Roth <michael.roth@amd.com>,
Pankaj Gupta <pankaj.gupta@amd.com>
Subject: Re: Help improve 32-bit testing
Date: Tue, 25 Jun 2024 09:57:16 +0200 [thread overview]
Message-ID: <40e4c21a-1f64-445e-a385-a9f4ccec0b0d@linaro.org> (raw)
In-Reply-To: <ab8beba8-658a-4359-bfb1-672e5782633d@linaro.org>
Hi Richard,
On 25/6/24 01:33, Richard Henderson wrote:
> Hiya,
>
> I've just discovered a 32-bit build issue that is probably 3 weeks old.
How and what did you notice?
> While we still support 32-bit builds at all, I would request that we
> improve our cross-i686 testing. For instance: we have cross-i686-user
> and cross-i686-tci. There is some system build testing in the tci job,
> but (rightfully) not everything.
>
> I would like a full cross-i686-system target that builds all targets,
> and I would like the debian-i686-cross image on which we base these to
> be more complete -- ideally, exactly matching x86_64. In particular,
> CONFIG_SEV is not detected within the current docker image, which is
> where the current build error is located.
Orthogonally to whether we should improve x86 testing on 32-bit
hosts, IIRC this isn't the first time we have an issue with SEV
(or more generically Confidential Computing) on 32-bit host, so
I wonder if this is a feature worth testing & supporting there
(thus Cc'ing more maintainers).
Regards,
Phil.
next prev parent reply other threads:[~2024-06-25 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 23:33 Help improve 32-bit testing Richard Henderson
2024-06-25 7:11 ` Thomas Huth
2024-06-25 14:06 ` Richard Henderson
2024-06-25 7:49 ` Daniel P. Berrangé
2024-06-25 7:57 ` Philippe Mathieu-Daudé [this message]
2024-06-25 14:12 ` Richard Henderson
2024-06-25 14:54 ` Alex Bennée
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=40e4c21a-1f64-445e-a385-a9f4ccec0b0d@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=dovmurik@linux.ibm.com \
--cc=michael.roth@amd.com \
--cc=pankaj.gupta@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).