From: Klaus Jensen <its@irrelevant.dk>
To: Jinhao Fan <fanjinhao21s@ict.ac.cn>
Cc: qemu-devel@nongnu.org, kbusch@kernel.org
Subject: Re: [PATCH v4] hw/nvme: Use ioeventfd to handle doorbell updates
Date: Tue, 26 Jul 2022 11:19:32 +0200 [thread overview]
Message-ID: <Yt+xpMzwRWvn3QqR@apples> (raw)
In-Reply-To: <869047CA-DD0A-45D1-9DBA-2BA1A3E00ADF@ict.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]
On Jul 26 15:55, Jinhao Fan wrote:
> at 3:41 PM, Klaus Jensen <its@irrelevant.dk> wrote:
>
> > On Jul 26 15:35, Jinhao Fan wrote:
> >> at 4:55 AM, Klaus Jensen <its@irrelevant.dk> wrote:
> >>
> >>> We have a regression following this patch that we need to address.
> >>>
> >>> With this patch, issuing a reset on the device (`nvme reset /dev/nvme0`
> >>> will do the trick) causes QEMU to hog my host cpu at 100%.
> >>>
> >>> I'm still not sure what causes this. The trace output is a bit
> >>> inconclusive still.
> >>>
> >>> I'll keep looking into it.
> >>
> >> I cannot reproduce this bug. I just start the VM and used `nvme reset
> >> /dev/nvme0`. Did you do anything before the reset?
> >
> > Interesting and thanks for checking! Looks like a kernel issue then!
> >
> > I remember that I'm using a dev branch (nvme-v5.20) of the kernel and
> > reverting to a stock OS kernel did not produce the bug.
>
> I’m using 5.19-rc4 which I pulled from linux-next on Jul 1. It works ok on
> my machine.
Interesting. I can reproduce on 5.19-rc4 from torvalds tree. Can you
drop your qemu command line here?
This is mine.
/home/kbj/work/src/qemu/build/x86_64-softmmu/qemu-system-x86_64 \
-nodefaults \
-display "none" \
-machine "q35,accel=kvm,kernel-irqchip=split" \
-cpu "host" \
-smp "4" \
-m "8G" \
-device "intel-iommu" \
-netdev "user,id=net0,hostfwd=tcp::2222-:22" \
-device "virtio-net-pci,netdev=net0" \
-device "virtio-rng-pci" \
-drive "id=boot,file=/home/kbj/work/vol/machines/img/nvme.qcow2,format=qcow2,if=virtio,discard=unmap,media=disk,read-only=no" \
-device "pcie-root-port,id=pcie_root_port1,chassis=1,slot=0" \
-device "nvme,id=nvme0,serial=deadbeef,bus=pcie_root_port1,mdts=7" \
-drive "id=null,if=none,file=null-co://,file.read-zeroes=on,format=raw" \
-device "nvme-ns,id=nvm-1,drive=nvm-1,bus=nvme0,nsid=1,drive=null,logical_block_size=4096,physical_block_size=4096" \
-pidfile "/home/kbj/work/vol/machines/run/null/pidfile" \
-kernel "/home/kbj/work/src/kernel/linux/arch/x86_64/boot/bzImage" \
-append "root=/dev/vda1 console=ttyS0,115200 audit=0 intel_iommu=on" \
-virtfs "local,path=/home/kbj/work/src/kernel/linux,security_model=none,readonly=on,mount_tag=kernel_dir" \
-serial "mon:stdio" \
-d "guest_errors" \
-D "/home/kbj/work/vol/machines/log/null/qemu.log" \
-trace "pci_nvme*"
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-26 9:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 14:24 [PATCH v4] hw/nvme: Use ioeventfd to handle doorbell updates Jinhao Fan
2022-07-05 17:11 ` Klaus Jensen
2022-07-05 18:43 ` Keith Busch
2022-07-06 11:34 ` Jinhao Fan
2022-07-07 5:51 ` Klaus Jensen
2022-07-07 8:50 ` Jinhao Fan
2022-07-06 10:57 ` Jinhao Fan
2022-07-09 3:06 ` Jinhao Fan
2022-07-12 12:23 ` Klaus Jensen
2022-07-14 5:35 ` Klaus Jensen
2022-07-25 20:55 ` Klaus Jensen
2022-07-26 7:35 ` Jinhao Fan
2022-07-26 7:41 ` Klaus Jensen
2022-07-26 7:55 ` Jinhao Fan
2022-07-26 9:19 ` Klaus Jensen [this message]
2022-07-26 10:09 ` Klaus Jensen
2022-07-26 11:24 ` Klaus Jensen
2022-07-26 11:32 ` Klaus Jensen
2022-07-26 12:08 ` Klaus Jensen
2022-07-27 7:06 ` Klaus Jensen
2022-07-27 8:16 ` Jinhao Fan
2022-07-27 8:21 ` Klaus Jensen
2022-07-27 15:09 ` Jinhao Fan
2022-07-26 12:35 ` Stefan Hajnoczi
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=Yt+xpMzwRWvn3QqR@apples \
--to=its@irrelevant.dk \
--cc=fanjinhao21s@ict.ac.cn \
--cc=kbusch@kernel.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).