From: Marcel Apfelbaum <marcel@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com,
Eduardo Habkost <ehabkost@redhat.com>,
kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3] hw/virtio: Add PCIe capability to virtio devices
Date: Mon, 2 Nov 2015 12:01:06 +0200 [thread overview]
Message-ID: <56373462.2050601@redhat.com> (raw)
In-Reply-To: <20151102105425.32230aca.cornelia.huck@de.ibm.com>
On 11/02/2015 11:54 AM, Cornelia Huck wrote:
> On Mon, 2 Nov 2015 11:20:50 +0200
> Marcel Apfelbaum <marcel@redhat.com> wrote:
>
>> On 11/02/2015 11:07 AM, Cornelia Huck wrote:
>>> On Sun, 1 Nov 2015 11:15:24 +0200
>>> Marcel Apfelbaum <marcel@redhat.com> wrote:
>>>
>>>> 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?
>>>
>>> net and scsi already defaulted any_layout to true before.
>>>
>>> Are any others missing?
>>>
>>
>> Hi,
>>
>> The whole list is:
>> name "virtio-blk-pci", bus PCI, alias "virtio-blk"
>> name "virtio-scsi-pci", bus PCI
>> name "virtio-net-pci", bus PCI, alias "virtio-net"
>> name "virtio-input-host-pci", bus PCI
>> name "virtio-keyboard-pci", bus PCI
>> name "virtio-mouse-pci", bus PCI
>> name "virtio-serial-pci", bus PCI, alias "virtio-serial"
>> name "virtio-tablet-pci", bus PCI
>> name "virtio-gpu-pci", bus PCI
>> name "virtio-balloon-pci", bus PCI, alias "virtio-balloon"
>> name "virtio-rng-pci", bus PCI
>>
>>
>> HW_COMPAT_2_3 has:
>> - virtio-blk-pci
>> - virtio-balloon-pci
>> - virtio-serial-pci
>> - virtio-9p-pci
>> - virtio-rng-pci
>>
>> You mentioned:
>> - virtio-scsi-pci
>> - virtio-net-pci
>>
>> I guess the remaining list is:
>> - virtio-input-host-pci
>> - virtio-keyboard-pci
>> - virtio-mouse-pci
>> - virtio-tablet-pci
>> - virtio-gpu-pci
>>
>> I don't know if is is applicable to them, or if they have it defaulted to any_layout,
>> however the above devices are part of QEMU 2.3.
>
> Hm, unless I'm fumbling git commands here, they were all added post-2.3?
I misspoke, I wanted to say that when I run (latest master branch):
<qemu-bin> -M pc-q35-2.3 -device help 2>&1 | grep virtio | grep pci
the devices are there.
>
> (And all of them seem to force virtio-1 anyway.)
OK. Thanks for looking into it!
Marcel
>
next prev parent reply other threads:[~2015-11-02 10:01 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
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 [this message]
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=56373462.2050601@redhat.com \
--to=marcel@redhat.com \
--cc=cornelia.huck@de.ibm.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).