From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ayan Kumar Halder <ayankuma@amd.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Xen-devel <xen-devel@lists.xenproject.org>,
Stewart Hildebrand <stewart.hildebrand@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Sergiy Kibrik <Sergiy_Kibrik@epam.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Vikram Garhwal <vikram.garhwal@amd.com>,
Stefano Stabellini <stefano.stabellini@amd.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Bill Mills <bill.mills@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: QEMU features useful for Xen development?
Date: Tue, 05 Sep 2023 10:55:20 +0100 [thread overview]
Message-ID: <87tts8hqfx.fsf@linaro.org> (raw)
In-Reply-To: <799b1754-7529-0538-1b5a-d94a362eb74d@amd.com>
Ayan Kumar Halder <ayankuma@amd.com> writes:
> Hi Peter/Alex,
>
> Appreciate your help. :)
>
> On 31/08/2023 11:03, Peter Maydell wrote:
>> On Thu, 31 Aug 2023 at 10:53, Alex Bennée <alex.bennee@linaro.org> wrote:
>>>
>>> Peter Maydell <peter.maydell@linaro.org> writes:
>>>
>>>> On Thu, 31 Aug 2023 at 01:57, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>>>> As Xen is gaining R52 and R82 support, it would be great to be able to
>>>>> use QEMU for development and testing there as well, but I don't think
>>>>> QEMU can emulate EL2 properly for the Cortex-R architecture. We would
>>>>> need EL2 support in the GIC/timer for R52/R82 as well.
>>>> We do actually have a Cortex-R52 model which at least in theory
>>>> should include EL2 support, though as usual with newer QEMU
>>>> stuff it quite likely has lurking bugs; I'm not sure how much
>>>> testing it's had. Also there is currently no board model which
>>>> will work with the Cortex-R52 so it's a bit tricky to use in practice.
>>>> (What sort of board model would Xen want to use it with?)
>>> We already model a bunch of the mps2/mps3 images so I'm assuming adding
>>> the mps3-an536 would be a fairly simple step to do (mps2tz.c is mostly
>>> tweaking config values). The question is would it be a useful target for
>>> Xen?
>> All our MPS2/MPS3 boards are M-profile. That means we have the
>> device models for all the interesting devices on the board, but
>> it would be simpler to write the an536 board model separately.
>> (In particular, the M-profile boards are wrappers around an
>> "ARMSSE" sort-of-like-an-SoC component; there's no equivalent
>> for the Cortex-R52.)
>>
>>> https://developer.arm.com/documentation/dai0536/latest/
>
> Yes, it will be helpful if Qemu can model this board. We have a
> downstream port of Xen on R52 (upstreaming is in progress).
>
> So, we can test the Qemu model with Xen.
>
> Also if all works fine, we might consider adding this to the upstream
> Xen CI docker.
>
> Out of curiosity, are you planning to add Qemu R52 SoC support to Zephyr ?
Generally enabling other software platforms is out of scope for the QEMU
team as we have plenty enough to do in QEMU itself. However its
certainly useful to have images we can test with.
Eyeballing the Zephyr docs it looks like it already supports some
R-profile cores on various boards, including CPU_CORTEX_R52 for the
NXPS32Z/E board. The BSP sections mostly look like config fragments but
I'm not really familiar with how Zephyr goes together.
I can ask our micro-controller experts what might be missing and need
implementing but I can't commit them to work on it ;-)
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-09-05 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 16:11 QEMU features useful for Xen development? Alex Bennée
2023-08-31 0:56 ` Stefano Stabellini
2023-08-31 9:02 ` Peter Maydell
2023-08-31 9:37 ` Alex Bennée
2023-08-31 10:03 ` Peter Maydell
2023-08-31 10:27 ` Alex Bennée
2023-08-31 11:42 ` Peter Maydell
2023-08-31 10:32 ` Ayan Kumar Halder
2023-09-05 9:55 ` Alex Bennée [this message]
2023-10-20 15:15 ` Alex Bennée
2023-10-20 18:15 ` Ayan Kumar Halder
2024-02-19 11:50 ` Peter Maydell
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=87tts8hqfx.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Sergiy_Kibrik@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayankuma@amd.com \
--cc=bill.mills@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@amd.com \
--cc=stewart.hildebrand@amd.com \
--cc=vikram.garhwal@amd.com \
--cc=viresh.kumar@linaro.org \
--cc=xen-devel@lists.xenproject.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).