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: Sun, 26 Apr 2009 19:44:24 -0500 Message-ID: <49F4FFE8.9010603@codemonkey.ws> References: <1240571860-13832-1-git-send-email-pktoss@gmail.com> <1295ed070904260544m25d781b1ueaeb3ba058818491@mail.gmail.com> <49F4584C.6000504@redhat.com> <200904270919.27851.rusty@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Pantelis Koukousoulas , kvm@vger.kernel.org To: Rusty Russell Return-path: Received: from mail-bw0-f163.google.com ([209.85.218.163]:60578 "EHLO mail-bw0-f163.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbZD0Aoc (ORCPT ); Sun, 26 Apr 2009 20:44:32 -0400 Received: by bwz7 with SMTP id 7so2011965bwz.37 for ; Sun, 26 Apr 2009 17:44:30 -0700 (PDT) In-Reply-To: <200904270919.27851.rusty@rustcorp.com.au> Sender: kvm-owner@vger.kernel.org List-ID: Rusty Russell wrote: > On Sun, 26 Apr 2009 10:19:16 pm Avi Kivity wrote: > >> Pantelis Koukousoulas wrote: >> >>>> Please copy the virtio maintainer (Rusty Russell ) on >>>> virtio guest patches. >>>> >>>> >>> Well, for now the issue is whether my understanding of qemu/pci-ids.txt and the >>> comment in virtio_pci.c that both say that the full 0x1000 - 0x10ff range of PCI >>> device IDs is donated for virtio_pci devices is correct. >>> >>> >> 0x1000-0x10ff is correct. I don't know where the 0x103f came from. Rusty? >> > > We decided to hedge our bets in case we broke the ABI. > > AFAICT there's no reason to claim the full range until we need it. Wake me > when device #32 is used :) > Would be good to at least include the "experiment range" in case people are making third-party virtio modules and want to play around without replacing virtio-{pci,*}. Regards, Anthony Liguori > Rusty. > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >