[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v6 24/24] target/arm: Define neoverse-n1

From: Zenghui Yu
Subject: Re: [PATCH v6 24/24] target/arm: Define neoverse-n1
Date: Thu, 11 Aug 2022 15:08:21 +0800
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0

On 2022/8/11 0:47, Peter Maydell wrote:
On Wed, 10 Aug 2022 at 14:14, Zenghui Yu <yuzenghui@huawei.com> wrote:
The r4p1 TRM says that the Neoverse N1 core supports SPE (the value
of ID_AA64DFR0.PMSVer is 0b0001) but do we really support SPE
emulation in QEMU?

The guest immediately received an unexpected exception (with EC==0,
at EFI stage) when I tried to boot it using something like:

/path/to/qemu-system-aarch64 \
-M virt,gic-version=3,virtualization=on \
-cpu neoverse-n1 -accel tcg \
-bios QEMU_EFI.fd [...]

and QEMU shouted that "read access to unsupported AArch64 system
register op0:3 op1:0 crn:9 crm:10 op2:7", which told us that the
guest attempted to read the PMBIDR_EL1 register.

No, we don't emulate SPE. We should probably not advertise it
(we might do a no-op implementation eventually).

What guest is this ?

I guess basically anything that starts playing with SPE. I used Linux
and both stable-5.15 and mainline kernel can't boot.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]