From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
Sunil V L <sunilvl@ventanamicro.com>,
Andrew Jones <ajones@ventanamicro.com>,
"Warkentin, Andrei" <andrei.warkentin@intel.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Weiwei Li <liweiwei@iscas.ac.cn>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org
Subject: Re: riscv64 virt board crash upon startup
Date: Fri, 8 Sep 2023 01:55:26 +0200 [thread overview]
Message-ID: <bfddf3fa-0b14-25b4-39d6-e3f65b659525@redhat.com> (raw)
In-Reply-To: <fe0ebb81-30b7-9e60-e9b5-7737c562274b@redhat.com>
On 9/8/23 01:47, Laszlo Ersek wrote:
> I don't know why qemu_console_is_multihead() used a lot of QOM
> trickery for this in the first place, but here's what I'd propose as
> fix -- simply try to locate a QemuGraphicConsole in "consoles" that
> references the same "device" that *this* QemuGraphicConsole
> references, but by a different "head" number.
So, the final version of the function would look like:
static bool qemu_graphic_console_is_multihead(QemuGraphicConsole *c)
{
QemuConsole *con;
QTAILQ_FOREACH(con, &consoles, next) {
if (!QEMU_IS_GRAPHIC_CONSOLE(con)) {
continue;
}
QemuGraphicConsole *candidate = QEMU_GRAPHIC_CONSOLE(con);
if (candidate->device != c->device) {
continue;
}
if (candidate->head != c->head) {
return true;
}
}
return false;
}
Laszlo
next prev parent reply other threads:[~2023-09-07 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 11:25 riscv64 virt board crash upon startup Laszlo Ersek
2023-09-07 12:29 ` Philippe Mathieu-Daudé
2023-09-07 23:47 ` Laszlo Ersek
2023-09-07 23:55 ` Laszlo Ersek [this message]
2023-09-11 8:05 ` Marc-André Lureau
2023-09-11 8:12 ` Marc-André Lureau
2023-09-11 8:53 ` Gerd Hoffmann
2023-09-11 13:12 ` Laszlo Ersek
2023-09-12 8:40 ` Laszlo Ersek
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=bfddf3fa-0b14-25b4-39d6-e3f65b659525@redhat.com \
--to=lersek@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=andrei.warkentin@intel.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=kraxel@redhat.com \
--cc=liweiwei@iscas.ac.cn \
--cc=marcandre.lureau@redhat.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=rjones@redhat.com \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.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).