From: Peter Maydell <peter.maydell@linaro.org>
To: Daniel Bertalan <dani@danielbertalan.dev>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/arm/bcm2835_property: Implement "get command line" message
Date: Tue, 2 May 2023 12:42:55 +0100 [thread overview]
Message-ID: <CAFEAcA-_a3Qx9UnsJf++9aM=5X_S22yajkA-p4iaXHWScQrcyA@mail.gmail.com> (raw)
In-Reply-To: <vxR7X7H0IH2rUOb1rvzXmmG3_3raS-2LMKN-ugFoq0ziCSX199bwb_i-zZ5_KdhWzllmtwIlvJF74epNBag-Etjya_nhkplFFNGmi6blpvs=@danielbertalan.dev>
On Tue, 2 May 2023 at 12:10, Daniel Bertalan <dani@danielbertalan.dev> wrote:
>
> Hi Peter,
>
> Thank you for merging the patch.
>
> On Tuesday, May 2nd, 2023 at 12:15, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > Are there any particularly interesting bits of guest software
> > that try to read this property ?
>
> We plan to use it in the AArch64 port of SerenityOS temporarily, while
> we are in the process of bringing up device tree support.
> I added it here: <https://github.com/SerenityOS/serenity/pull/18557>
>
> [sidenote]
> By the way, do you know if anyone has managed to run the raspi3b emulation in
> EL1 (under KVM/HVF)?
No, that's not supported. The only board we have that works in
KVM is the 'virt' board. I guess in theory it could be bodged
into working, but AArch64 KVM isn't really intended as "run
an arbitrary guest kernel that uses an arbitrary machine and
set of devices", it's more "run a guest kernel that knows it's
running as a VM" (for instance there is no way to give the
guest something that says it's a Cortex-A53 -- you always get
the CPU type the host has).
-- PMM
prev parent reply other threads:[~2023-05-02 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 10:34 [PATCH] hw/arm/bcm2835_property: Implement "get command line" message Daniel Bertalan
2023-05-02 10:15 ` Peter Maydell
2023-05-02 11:10 ` Daniel Bertalan
2023-05-02 11:42 ` Peter Maydell [this message]
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='CAFEAcA-_a3Qx9UnsJf++9aM=5X_S22yajkA-p4iaXHWScQrcyA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=dani@danielbertalan.dev \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 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).