From: Gerd Hoffmann <kraxel@redhat.com>
To: Pantelis Koukousoulas <pktoss@gmail.com>
Cc: 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 11:01:13 +0200 [thread overview]
Message-ID: <49F57459.7070409@redhat.com> (raw)
In-Reply-To: <1295ed070904270139g5dc0b634hc7f13b38c814bccd@mail.gmail.com>
On 04/27/09 10:39, Pantelis Koukousoulas wrote:
>> I'd suggest to exclude the experimental range by default (enable via module
>> parameter) to make clear it isn't for regular use.
>
> 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.
> The module parameter parsing code is afaict
> provided by the end-driver (e.g., virtio-net) which only speaks virtio and has
> no idea there is an actual PCI device in the backend.
virtio_pci is a separate module and can have parameters too.
cheers,
Gerd
next prev parent reply other threads:[~2009-04-27 9:01 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 [this message]
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
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=49F57459.7070409@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.