From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zyk4C-0004xG-As for qemu-devel@nongnu.org; Tue, 17 Nov 2015 12:29:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zyk4B-0002wT-ER for qemu-devel@nongnu.org; Tue, 17 Nov 2015 12:29:16 -0500 Sender: Paolo Bonzini References: <1447765689-28940-1-git-send-email-hch@lst.de> From: Paolo Bonzini Message-ID: <564B63E2.4040306@redhat.com> Date: Tue, 17 Nov 2015 18:29:06 +0100 MIME-Version: 1.0 In-Reply-To: <1447765689-28940-1-git-send-email-hch@lst.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] (no subject) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig , Keith Busch Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org On 17/11/2015 14:08, Christoph Hellwig wrote: > below is a fix for a bug in the qemu NVMe identify implementation that's > causing us some trouble with an updated Linux driver. We'll have to > blacklist the existing Qemu device ID for it, so I wonder how we can > advertize a fixed controller. Maybe a new PCI ID? Or maybe just bump > the PCI revision, altough that would be a bit more complicated in the > driver. Bumping the PCI revision would be ideal, but I guess the PCI ID would work too if it's really that bad. Paolo