From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: mips system emulation failure with virtio
Date: Tue, 5 Sep 2023 18:46:50 +0200 [thread overview]
Message-ID: <932ee6f0-f8bb-f9eb-49bd-3ffee7afd265@linaro.org> (raw)
In-Reply-To: <58b3aa9437ac94d7665e7b93f4868f7e7d3f71b3.camel@linuxfoundation.org>
On 5/9/23 17:53, Richard Purdie wrote:
> On Tue, 2023-09-05 at 17:12 +0200, Philippe Mathieu-Daudé wrote:
>> Hi Richard,
>>
>> On 5/9/23 16:50, Richard Purdie wrote:
>>> On Tue, 2023-09-05 at 14:59 +0100, Alex Bennée wrote:
>>>> Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>>>>
>>>>> With qemu 8.1.0 we see boot hangs fox x86-64 targets.
>>>>>
>>>>> These are fixed by 0d58c660689f6da1e3feff8a997014003d928b3b (softmmu:
>>>>> Use async_run_on_cpu in tcg_commit) but if I add that commit, mips and
>>>>> mips64 break, hanging at boot unable to find a rootfs.
>>
>> Are you testing mipsel / mips64el?
>
> No, it was mips/mips64, i.e. big endian.
Sorry my question was not clear. I meant: Do you also
test mipsel / mips64el guests, and if so, do they work?
(IOW, is this bug only big-endian guest specific?)
Thanks,
Phil.
next prev parent reply other threads:[~2023-09-05 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 13:19 mips system emulation failure with virtio Richard Purdie
2023-09-05 13:59 ` Alex Bennée
2023-09-05 14:50 ` Richard Purdie
2023-09-05 15:12 ` Philippe Mathieu-Daudé
2023-09-05 15:53 ` Richard Purdie
2023-09-05 16:46 ` Philippe Mathieu-Daudé [this message]
2023-09-05 16:50 ` Richard Purdie
2023-09-06 15:50 ` Philippe Mathieu-Daudé
2023-09-06 16:06 ` Philippe Mathieu-Daudé
2023-09-06 16:46 ` Richard Purdie
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=932ee6f0-f8bb-f9eb-49bd-3ffee7afd265@linaro.org \
--to=philmd@linaro.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=jiaxun.yang@flygoat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=richard.purdie@linuxfoundation.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).