From: Marcel Apfelbaum <marcel@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: kraxel@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3] hw/virtio: Add PCIe capability to virtio devices
Date: Sun, 1 Nov 2015 11:15:24 +0200 [thread overview]
Message-ID: <5635D82C.6030400@redhat.com> (raw)
In-Reply-To: <20151030152048.GQ4180@thinpad.lan.raisama.net>
On 10/30/2015 05:20 PM, Eduardo Habkost wrote:
> On Thu, Oct 29, 2015 at 01:56:28PM +0200, Marcel Apfelbaum wrote:
> [...]
>> index 095de5d..0a08531 100644
>> --- a/include/hw/compat.h
>> +++ b/include/hw/compat.h
>> @@ -2,7 +2,51 @@
>> #define HW_COMPAT_H
>>
>> #define HW_COMPAT_2_4 \
>> - /* empty */
>> + {\
>> + .driver = "virtio-blk-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>
> Why not a single virtio-pci.disable-pcie=on entry, instead of one entry
> for each subclass?
Hi,
Thanks for pointing that out, that being said, I am a little embarrassed
because I did think of it, but seeing HW_COMPAT 2_3 (any_layout) I assumed this
would not work, my bad.
By the way, HW_COMPAT_2_3 sets any-layout to off only for a few virtio devices,
not for all. Does anybody know if is in purpose or can we do the same for them too?
I'll send an updated version shortly,
Thanks
Marcel
>
>> + },{\
>> + .driver = "virtio-scsi-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-net-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-input-host-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-keyboard-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-mouse-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-serial-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-tablet-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-gpu-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-balloon-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },{\
>> + .driver = "virtio-rng-pci",\
>> + .property = "disable-pcie",\
>> + .value = "on",\
>> + },
>>
>> #define HW_COMPAT_2_3 \
>> {\
>> --
>> 2.1.0
>>
>
next prev parent reply other threads:[~2015-11-01 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 11:56 [Qemu-devel] [PATCH V3] hw/virtio: Add PCIe capability to virtio devices Marcel Apfelbaum
2015-10-30 15:20 ` Eduardo Habkost
2015-11-01 9:15 ` Marcel Apfelbaum [this message]
2015-11-02 9:07 ` Cornelia Huck
2015-11-02 9:20 ` Marcel Apfelbaum
2015-11-02 9:54 ` Cornelia Huck
2015-11-02 10:01 ` Marcel Apfelbaum
2015-11-02 12:05 ` Cornelia Huck
2015-11-02 12:12 ` Marcel Apfelbaum
2015-11-05 17:42 ` Eduardo Habkost
2015-11-05 18:22 ` Dr. David Alan Gilbert
2015-11-05 18:44 ` Marcel Apfelbaum
2015-11-05 18:51 ` Dr. David Alan Gilbert
2015-11-02 9:42 ` Greg Kurz
2015-11-02 9:53 ` Marcel Apfelbaum
2015-11-08 17:10 ` Michael S. Tsirkin
2015-11-08 18:13 ` Marcel Apfelbaum
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=5635D82C.6030400@redhat.com \
--to=marcel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).