From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Assign the correct pci id range to virtio_pci
Date: Mon, 27 Apr 2009 09:19:27 +0930
Message-ID: <200904270919.27851.rusty@rustcorp.com.au>
References: <1240571860-13832-1-git-send-email-pktoss@gmail.com> <1295ed070904260544m25d781b1ueaeb3ba058818491@mail.gmail.com> <49F4584C.6000504@redhat.com>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Pantelis Koukousoulas <pktoss@gmail.com>, kvm@vger.kernel.org,
	Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from ozlabs.org ([203.10.76.45]:43854 "EHLO ozlabs.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753351AbZDZXtf (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 26 Apr 2009 19:49:35 -0400
In-Reply-To: <49F4584C.6000504@redhat.com>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Sun, 26 Apr 2009 10:19:16 pm Avi Kivity wrote:
> Pantelis Koukousoulas wrote:
> >> Please copy the virtio maintainer (Rusty Russell <rusty@rustcorp.com.au>) 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 :)

Rusty.