From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Pantelis Koukousoulas <pktoss@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
kvm@vger.kernel.org
Subject: Re: [PATCH] Assign the correct pci id range to virtio_pci
Date: Mon, 27 Apr 2009 12:24:47 +0300 [thread overview]
Message-ID: <49F579DF.4050505@redhat.com> (raw)
In-Reply-To: <49F57802.9040208@redhat.com>
Gerd Hoffmann wrote:
> On 04/27/09 11:11, Pantelis Koukousoulas wrote:
>>>> Module parameter on what?
>>> virtio_pci.ko
>>>
>>> Then you'll do something like this ...
>>>
>>> echo "options virtio_pci experimental=1">> /etc/modprobe.d/virtio.conf
>>>
>>> ... to enable the experimental IDs.
>>
>> Ok, I can sure live with such an arrangement :)
>> Should the entire 0x10f0-0x10ff range be enabled by this option or
>> just a subset?
>> (and if a subset, how large, 4 IDs, more ?)
>
> That roughly matches the number of non-experimental IDs (1/4 of the
> complete range), so 4 IDs looks good to me.
Or maybe
modprobe virtio-pci claim=0x10f2 claim=0x10f7
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-27 9:24 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 [this message]
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
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=49F579DF.4050505@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@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