From: Mostafa Saleh <smostafa@google.com>
To: Zhou Wang <wangzhou1@hisilicon.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Subject: Re: [Bug Report] smmuv3 event 0x10 report when running virtio-blk-pci
Date: Tue, 10 Sep 2024 10:33:41 +0100 [thread overview]
Message-ID: <CAFgf54pzDerdXdfj_Dhowqfn35oPsvUBbzL9Sq3iS7HwkyscBA@mail.gmail.com> (raw)
In-Reply-To: <51b1ed21-e10e-8a7c-10ce-7be2f0c3b89f@hisilicon.com>
On Tue, Sep 10, 2024 at 2:51 AM Zhou Wang <wangzhou1@hisilicon.com> wrote:
>
> On 2024/9/9 22:47, Mostafa Saleh wrote:
> > Hi Zhou,
> >
> > On Mon, Sep 9, 2024 at 3:22 PM Zhou Wang via <qemu-devel@nongnu.org> wrote:
> >>
> >> Hi All,
> >>
> >> When I tested mainline qemu(commit 7b87a25f49), it reports smmuv3 event 0x10
> >> during kernel booting up.
> >>
> >> qemu command which I use is as below:
> >>
> >> qemu-system-aarch64 -machine virt,kernel_irqchip=on,gic-version=3,iommu=smmuv3 \
> >> -kernel Image -initrd minifs.cpio.gz \
> >> -enable-kvm -net none -nographic -m 3G -smp 6 -cpu host \
> >> -append 'rdinit=init console=ttyAMA0 ealycon=pl0ll,0x90000000 maxcpus=3' \
> >> -device pcie-root-port,port=0x8,chassis=0,id=pci.0,bus=pcie.0,multifunction=on,addr=0x2 \
> >> -device pcie-root-port,port=0x9,chassis=1,id=pci.1,bus=pcie.0,addr=0x2.0x1 \
> >> -device virtio-blk-pci,drive=drive0,id=virtblk0,num-queues=8,packed=on,bus=pci.1 \
> >> -drive file=/home/boot.img,if=none,id=drive0,format=raw
> >>
> >> smmuv3 event 0x10 log:
> >> [...]
> >> [ 1.962656] virtio-pci 0000:02:00.0: Adding to iommu group 0
> >> [ 1.963150] virtio-pci 0000:02:00.0: enabling device (0000 -> 0002)
> >> [ 1.964707] virtio_blk virtio0: 6/0/0 default/read/poll queues
> >> [ 1.965759] virtio_blk virtio0: [vda] 2097152 512-byte logical blocks (1.07 GB/1.00 GiB)
> >> [ 1.966934] arm-smmu-v3 9050000.smmuv3: event 0x10 received:
> >> [ 1.967442] input: gpio-keys as /devices/platform/gpio-keys/input/input0
> >> [ 1.967478] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010
> >> [ 1.968381] clk: Disabling unused clocks
> >> [ 1.968677] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000
> >> [ 1.968990] PM: genpd: Disabling unused power domains
> >> [ 1.969424] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.969814] ALSA device list:
> >> [ 1.970240] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.970471] No soundcards found.
> >> [ 1.970902] arm-smmu-v3 9050000.smmuv3: event 0x10 received:
> >> [ 1.971600] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010
> >> [ 1.971601] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000
> >> [ 1.971601] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.971602] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.971606] arm-smmu-v3 9050000.smmuv3: event 0x10 received:
> >> [ 1.971607] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010
> >> [ 1.974202] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000
> >> [ 1.974634] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.975005] Freeing unused kernel memory: 10112K
> >> [ 1.975062] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000
> >> [ 1.975442] Run init as init process
> >>
> >> Another information is that if "maxcpus=3" is removed from the kernel command line,
> >> it will be OK.
> >>
> >
> > That's interesting, not sure how that would be related.
> >
> >> I am not sure if there is a bug about vsmmu. It will be very appreciated if anyone
> >> know this issue or can take a look at it.
> >>
> >
> > Can you please provide logs with adding "-d trace:smmu*" to qemu invocation.
>
> Sure. Please see the attached log(using above qemu commit and command).
>
Thanks a lot, it seems the SMMUv3 indeed receives a translation
request with addr 0x0 which causes this event.
I don't see any kind of modification (alignment) of the address in this path.
So my hunch it's not related to the SMMUv3 and the initiator is
issuing bogus addresses.
> >
> > Also if possible, can you please provide which Linux kernel version
> > you are using, I will see if I can repro.
>
> I just use the latest mainline kernel(commit b831f83e40a2) with defconfig.
>
I see, I can't repro in my setup which has no "--enable-kvm" and with
"-cpu max" instead of host.
I will try other options and see if I can repro.
Thanks,
Mostafa
> Thanks,
> Zhou
>
> >
> > Thanks,
> > Mostafa
> >
> >> Thanks,
> >> Zhou
> >>
> >>
> >>
> >
> > .
prev parent reply other threads:[~2024-09-10 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 14:22 [Bug Report] smmuv3 event 0x10 report when running virtio-blk-pci Zhou Wang via
2024-09-09 14:31 ` Peter Maydell
2024-09-10 1:24 ` Zhou Wang via
2024-09-10 6:42 ` Eric Auger
2024-09-11 9:17 ` Eric Auger
2024-09-09 14:47 ` Mostafa Saleh
2024-09-10 1:51 ` Zhou Wang via
2024-09-10 9:33 ` Mostafa Saleh [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=CAFgf54pzDerdXdfj_Dhowqfn35oPsvUBbzL9Sq3iS7HwkyscBA@mail.gmail.com \
--to=smostafa@google.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=wangzhou1@hisilicon.com \
/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).