public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Niklas Cassel <Niklas.Cassel@wdc.com>,
	Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
	Luis Chamberlain <mcgrof@kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 3/3] nvme-pci: disable namespace identifiers for Qemu controllers
Date: Wed, 13 Apr 2022 17:49:29 +0200	[thread overview]
Message-ID: <YlbxCdgPaVUykcqx@apples> (raw)
In-Reply-To: <20220413153432.GA27146@lst.de>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Apr 13 17:34, Christoph Hellwig wrote:
> On Wed, Apr 13, 2022 at 10:40:47AM +0200, Klaus Jensen wrote:
> > On Apr 13 07:34, Niklas Cassel wrote:
> > > On Wed, Apr 13, 2022 at 06:49:05AM +0200, Christoph Hellwig wrote:
> > > > Qemu unconditionally reports a UUID, which depending on the qemu version
> > > 
> > > Since it appears that both older and current QEMU versions are not
> > > implementing this properly, perhaps you should also consider adding
> > > the pci vendor and device id used by older QEMU versions?
> > > 
> > > QEMU nvme pci vendor and device id was changed in commit:
> > > https://github.com/qemu/qemu/commit/6eb7a071292a2f11065127ac152fa24248806021
> > > 
> > > Which was first included in QEMU v5.2.0.
> > > 
> > 
> > That is a good point Niklas. +1 for that. The driver already knows about
> > that ID.
> 
> 5.2.0 is also the first qemu that supports the namespace descriptor
> list, that's why I didn't include it.

However, backwards compatibility in QEMU mandates that a compatibility
parameter is added when a device changes identity like this (i.e. PCI
vendor id).

This means that the 'use-intel-id' compatibility parameter may cause a
5.2 nvme device to present itself with the Intel PCI vendor/device id,
either because the user explicitly set it, or because the machine is
launched using a pre-5.2 machine type (i.e. `-machine pc-q35-5.1`),
which you would normally do if you want launch an existing VM on a new
version of QEMU.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-04-13 15:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  4:49 quirk broken namespace identifiers v2 Christoph Hellwig
2022-04-13  4:49 ` [PATCH 1/3] nvme: add a quirk to disable namespace identifiers Christoph Hellwig
2022-04-13  4:49 ` [PATCH 2/3] nvme-pci: disable namespace identifiers for the MAXIO MAP1002/1202 Christoph Hellwig
2022-04-13  4:49 ` [PATCH 3/3] nvme-pci: disable namespace identifiers for Qemu controllers Christoph Hellwig
2022-04-13  7:34   ` Niklas Cassel
2022-04-13  8:40     ` Klaus Jensen
2022-04-13 15:34       ` Christoph Hellwig
2022-04-13 15:49         ` Klaus Jensen [this message]
2022-04-13 15:50           ` Christoph Hellwig
2022-04-13 20:08             ` Klaus Jensen
2022-04-13 20:38               ` Keith Busch
2022-04-14  4:19               ` Christoph Hellwig
2022-04-13 14:42 ` quirk broken namespace identifiers v2 Keith Busch
  -- strict thread matches above, loose matches on Subject: below --
2022-04-12  6:11 quirk broken namespace identifiers Christoph Hellwig
2022-04-12  6:11 ` [PATCH 3/3] nvme-pci: disable namespace identifiers for Qemu controllers Christoph Hellwig
2022-04-12  6:33   ` Klaus Jensen
2022-04-12 11:45     ` Christoph Hellwig
2022-04-12 20:43       ` Klaus Jensen
2022-04-12 10:25   ` Sagi Grimberg

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=YlbxCdgPaVUykcqx@apples \
    --to=its@irrelevant.dk \
    --cc=Niklas.Cassel@wdc.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=sagi@grimberg.me \
    /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