qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: virtio-pci in qemu-system-arm is broken in 8.2
Date: Tue, 9 Jan 2024 11:33:32 +0000	[thread overview]
Message-ID: <CAFEAcA-hkd=VQdqw7-P1RGwu-c9JLn-NUHC1kgU-YgZ1FOMQww@mail.gmail.com> (raw)
In-Reply-To: <560c9f56-f0d8-4def-863a-63ba4226209e@tls.msk.ru>

On Mon, 8 Jan 2024 at 17:38, Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> 08.01.2024 20:07, Peter Maydell wrote:
> ..
> > I'm trying to figure out what kind of kernel config causes
> > this. If I do an upstream build of v6.6.9 with this config:
> > https://people.linaro.org/~peter.maydell/arm-6.6.9-config
> >
> > then it successfully probes the PCI device even with -cpu max:
>
> (with -cpu max it worked before but broke in 8.2 (after that commit).
> Without -cpu max it doesn't work for me neither before nor in 8.2.
> But ok.)
>
> 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.)

thanks
-- PMM


  reply	other threads:[~2024-01-09 11:34 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 [this message]
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
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='CAFEAcA-hkd=VQdqw7-P1RGwu-c9JLn-NUHC1kgU-YgZ1FOMQww@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mjt@tls.msk.ru \
    --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).