From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: virtio-pci in qemu-system-arm is broken in 8.2
Date: Tue, 09 Jan 2024 15:03:06 +0000 [thread overview]
Message-ID: <875y02h7md.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA9K2jf3BfHY3xpP4T-_iH9nNX=XLrNp=mPg5nqZURBOrw@mail.gmail.com> (Peter Maydell's message of "Tue, 9 Jan 2024 14:31:45 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 9 Jan 2024 at 14:21, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>> > On Tue, 9 Jan 2024 at 11:33, Peter Maydell <peter.maydell@linaro.org> wrote:
>> >> On Mon, 8 Jan 2024 at 17:38, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> >> > Speaking of config. This is standard debian config, I'm attaching one
>> >> > to this email. It can be found in the package, eg
>> >> > http://deb.debian.org/debian/pool/main/l/linux/linux-image-6.6.9-armmp_6.6.9-1_armhf.deb
>> >> > in /boot/config-$(uname -r).
>> >>
>> >> It does seem to be a config thing -- on a plain upstream
>> >> v6.6.9 my config works and that debian default one does
>> >> not. Now to try to identify which particular config
>> >> difference is at fault. (It's not the CONFIG_VMSPLIT one,
>> >> I just tried that.)
>> >
>> > Oh, your kernel isn't an LPAE one (i.e. CONFIG_LPAE is not
>> > set). That will obviously never be able to access registers
>> > above the 4GB mark (though the kernel's error message in this
>> > situation is a bit unhelpful and could perhaps be improved).
>> > If I set CONFIG_LPAE on the non-working config it starts working.
>> >
>> > I think then the answer is:
>> > * if you want to use the (default) highmem setup, use an LPAE kernel
>> > * if you want to use a non-LPAE kernel, tell QEMU to avoid
>> > highmem using '-machine virt,highmem=off'
>>
>> Could we expand the "highmem" description in
>> https://www.qemu.org/docs/master/system/arm/virt.html to make it
>> clearer. I'm sure this isn't the first time there have been 32bit
>> difficulties with non-LPAE kernels?
>
> Sure. We could make the highmem property description read:
>
> # Set on/off to enable/disable placing devices and RAM in physical
> # address space above 32 bits. The default is on for machine types
> # later than virt-2.12 when the CPU supports an address space
> # bigger than 32 bits (i.e. 64-bit CPUs, and 32-bit CPUs with the
> # Large Physical Address Extension (LPAE) feature). If you want to
> # boot a 32-bit kernel which does not have CONFIG_LPAE enabled on
> # a CPU type which implements LPAE, you will need to manually set
> # this to 'off'; otherwise some devices, such as the PCI controller,
> # will not be accessible.
>
> How's that ?
LGTM and even if the users don't read it hopefully the LLMs will ;-)
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-01-09 15:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 11:51 virtio-pci in qemu-system-arm is broken in 8.2 Michael Tokarev
2023-12-21 18:18 ` Alex Bennée
2023-12-21 22:00 ` Alex Bennée
2024-01-04 14:09 ` Peter Maydell
2024-01-04 14:31 ` Peter Maydell
2024-01-04 14:41 ` Peter Maydell
2024-01-04 16:25 ` Michael Tokarev
2024-01-04 17:17 ` Michael Tokarev
2024-01-05 14:09 ` Peter Maydell
2024-01-08 17:07 ` Peter Maydell
2024-01-08 17:38 ` Michael Tokarev
2024-01-09 11:33 ` Peter Maydell
2024-01-09 13:52 ` Peter Maydell
2024-01-09 14:21 ` Alex Bennée
2024-01-09 14:31 ` Peter Maydell
2024-01-09 15:03 ` Alex Bennée [this message]
2024-01-09 16:26 ` Eric Auger
2024-01-09 16:24 ` Michael Tokarev
2024-01-09 16:31 ` Peter Maydell
2024-01-09 16:41 ` 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=875y02h7md.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.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).