From: Guenter Roeck <linux@roeck-us.net>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Jinhao Fan <fanjinhao21s@ict.ac.cn>,
qemu-devel@nongnu.org, kbusch@kernel.org
Subject: Re: [PATCH v3 1/2] hw/nvme: Implement shadow doorbell buffer support
Date: Thu, 8 Dec 2022 12:39:55 -0800 [thread overview]
Message-ID: <20221208203955.GA1367659@roeck-us.net> (raw)
In-Reply-To: <20221208201353.GA928427@roeck-us.net>
On Thu, Dec 08, 2022 at 12:13:55PM -0800, Guenter Roeck wrote:
> On Thu, Dec 08, 2022 at 10:47:42AM -0800, Guenter Roeck wrote:
> > >
> > > A cq head doorbell mmio is skipped... And it is not the fault of the
> > > kernel. The kernel is in it's good right to skip the mmio since the cq
> > > eventidx is not properly updated.
> > >
> > > Adding that and it boots properly on riscv. But I'm perplexed as to why
> > > this didnt show up on our regularly tested platforms.
> > >
> > > Gonna try to get this in for 7.2!
> >
> > I see another problem with sparc64.
> >
> > [ 5.261508] could not locate request for tag 0x0
> > [ 5.261711] nvme nvme0: invalid id 0 completed on queue 1
> >
> > That is seen repeatedly until the request times out. I'll test with
> > your patch to see if it resolves this problem as well, and will bisect
> > otherwise.
> >
> The second problem is unrelated to the doorbell problem.
> It is first seen in qemu v7.1. I'll try to bisect.
>
Unfortunately, the problem observed with sparc64 also bisects to this
patch. Making things worse, "hw/nvme: fix missing cq eventidx update"
does not fix it (which is why I initially thought it was unrelated).
I used the following qemu command line.
qemu-system-sparc64 -M sun4v -cpu "TI UltraSparc IIi" -m 512 -snapshot \
-device nvme,serial=foo,drive=d0,bus=pciB \
-drive file=rootfs.ext2,if=none,format=raw,id=d0 \
-kernel arch/sparc/boot/image -no-reboot \
-append "root=/dev/nvme0n1 console=ttyS0" \
-nographic -monitor none
Guenter
next prev parent reply other threads:[~2022-12-08 20:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:34 [PATCH v3 0/2] hw/nvme: Add shadow doorbell buffer support Jinhao Fan
2022-06-16 12:34 ` [PATCH v3 1/2] hw/nvme: Implement " Jinhao Fan
2022-06-27 19:17 ` Keith Busch
2022-06-27 19:33 ` Klaus Jensen
2022-06-28 0:29 ` Jinhao Fan
2022-12-07 17:49 ` Guenter Roeck
2022-12-08 7:16 ` Klaus Jensen
2022-12-08 8:08 ` Klaus Jensen
2022-12-08 18:47 ` Guenter Roeck
2022-12-08 20:13 ` Guenter Roeck
2022-12-08 20:28 ` Keith Busch
2022-12-08 21:16 ` Guenter Roeck
2022-12-08 20:39 ` Guenter Roeck [this message]
2022-12-09 11:00 ` Guenter Roeck
2022-12-12 9:58 ` Klaus Jensen
2022-12-12 13:39 ` Guenter Roeck
2022-12-12 13:45 ` Klaus Jensen
2022-12-12 14:27 ` Guenter Roeck
2022-12-12 15:18 ` Klaus Jensen
2022-06-16 12:34 ` [PATCH v3 2/2] hw/nvme: Add trace events for shadow doorbell buffer Jinhao Fan
2022-06-17 11:54 ` [PATCH v3 0/2] hw/nvme: Add shadow doorbell buffer support Klaus Jensen
2022-06-17 12:47 ` Jinhao Fan
2022-06-17 12:56 ` Klaus Jensen
2022-06-17 13:02 ` Jinhao Fan
2022-06-17 20:35 ` Keith Busch
2022-06-27 6:00 ` Klaus Jensen
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=20221208203955.GA1367659@roeck-us.net \
--to=linux@roeck-us.net \
--cc=fanjinhao21s@ict.ac.cn \
--cc=its@irrelevant.dk \
--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).