From: Rusty Russell <rusty@rustcorp.com.au>
To: Pantelis Koukousoulas <pktoss@gmail.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] Assign the correct pci id range to virtio_pci
Date: Mon, 4 May 2009 11:23:32 +0930 [thread overview]
Message-ID: <200905041123.33458.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1295ed070904262023h5efc21a3u768960d3f246fc2d@mail.gmail.com>
On Mon, 27 Apr 2009 12:53:25 pm Pantelis Koukousoulas wrote:
> On Mon, Apr 27, 2009 at 3:44 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> > 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,*}.
>
> I 'd be happy with a simple comment explaining the 0x103f (e.g.,
> /* Not yet using the full 0x1000 - 0x10ef to hedge our bets in case we
> broke the ABI.*/
> as explained above)
Thanks, I like your patch.
Where did this idea of "experimental" range come from, BTW? I prefer your
module cmdline approach, as it discourages deployment with such numbers.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-05-04 1:53 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
2009-04-27 3:23 ` Pantelis Koukousoulas
2009-05-04 1:53 ` Rusty Russell [this message]
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=200905041123.33458.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pktoss@gmail.com \
/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