From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Avi Kivity <avi@redhat.com>,
Pantelis Koukousoulas <pktoss@gmail.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] Assign the correct pci id range to virtio_pci
Date: Sun, 26 Apr 2009 19:44:24 -0500 [thread overview]
Message-ID: <49F4FFE8.9010603@codemonkey.ws> (raw)
In-Reply-To: <200904270919.27851.rusty@rustcorp.com.au>
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 <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 :)
>
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
>
next prev parent reply other threads:[~2009-04-27 0:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 11:17 [PATCH] Assign the correct pci id range to virtio_pci Pantelis Koukousoulas
2009-04-24 13:19 ` Anthony Liguori
[not found] ` <49F55DD1.8020506@redhat.com>
2009-04-27 8:39 ` Pantelis Koukousoulas
2009-04-27 9:01 ` Gerd Hoffmann
2009-04-27 9:11 ` Pantelis Koukousoulas
2009-04-27 9:16 ` Gerd Hoffmann
2009-04-27 9:24 ` Avi Kivity
2009-04-27 11:45 ` Pantelis Koukousoulas
2009-04-27 11:56 ` Avi Kivity
2009-04-28 14:42 ` Pantelis Koukousoulas
2009-04-28 15:19 ` Gerd Hoffmann
2009-04-29 7:47 ` Pantelis Koukousoulas
2009-04-26 10:36 ` Avi Kivity
2009-04-26 12:44 ` Pantelis Koukousoulas
2009-04-26 12:49 ` Avi Kivity
2009-04-26 23:49 ` Rusty Russell
2009-04-27 0:44 ` Anthony Liguori [this message]
2009-04-27 3:23 ` Pantelis Koukousoulas
2009-05-04 1:53 ` Rusty Russell
2009-05-04 2:32 ` Pantelis Koukousoulas
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=49F4FFE8.9010603@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pktoss@gmail.com \
--cc=rusty@rustcorp.com.au \
/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