qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Help improve 32-bit testing
Date: Tue, 25 Jun 2024 09:11:59 +0200	[thread overview]
Message-ID: <d59f9541-eb4e-4a0a-b2c2-54d7eecbff95@redhat.com> (raw)
In-Reply-To: <ab8beba8-658a-4359-bfb1-672e5782633d@linaro.org>

On 25/06/2024 01.33, Richard Henderson wrote:
> Hiya,
> 
> I've just discovered a 32-bit build issue that is probably 3 weeks old.
> 
> 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.

System emulation on 32-bit x86 hosts is marked as deprecated since QEMU 8.0 
... maybe we could finally remove it instead?

> 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.
> 
> Do you have time to look at this?

If you really, really want to go a step backwards, then basically just 
revert commit 4f9a8315e65561bafa03651518aa5d22af09bdee and use the 
i686-debian-cross-container image instead of the removed 
i386-fedora-cross-container image.

  HTH,
   Thomas



  reply	other threads:[~2024-06-25  7:12 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 [this message]
2024-06-25 14:06   ` Richard Henderson
2024-06-25  7:49 ` Daniel P. Berrangé
2024-06-25  7:57 ` Philippe Mathieu-Daudé
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=d59f9541-eb4e-4a0a-b2c2-54d7eecbff95@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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).