From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] Assign the correct pci id range to virtio_pci Date: Fri, 24 Apr 2009 08:19:17 -0500 Message-ID: <49F1BC55.9080605@codemonkey.ws> References: <1240571860-13832-1-git-send-email-pktoss@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Gerd Hoffmann To: Pantelis Koukousoulas Return-path: Received: from yw-out-2324.google.com ([74.125.46.29]:63757 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753457AbZDXNTW (ORCPT ); Fri, 24 Apr 2009 09:19:22 -0400 Received: by yw-out-2324.google.com with SMTP id 5so650395ywb.1 for ; Fri, 24 Apr 2009 06:19:21 -0700 (PDT) In-Reply-To: <1240571860-13832-1-git-send-email-pktoss@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Pantelis Koukousoulas wrote: > According to the file pci-ids.txt in qemu sources, the range of PCI > device IDs assigned to virtio_pci is 0x1000 to 0x10ff, with a few > subranges that have different rules regarding who can get an ID > there and how. > > Nevertheless, the full range should be assigned to the generic > virtio_pci driver, so that all corresponding devices, including > the experimental/unreleased ones "just work". > Gerd, since you appear to be managing the PCI ID range, what do you think? Regards, Anthony Liguori