From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] hw/virtio: Add PCIe capability to virtio devices
Date: Tue, 13 Oct 2015 10:13:37 +0200 [thread overview]
Message-ID: <1444724017.19915.35.camel@redhat.com> (raw)
In-Reply-To: <20151012183823-mutt-send-email-mst@redhat.com>
On Mo, 2015-10-12 at 18:42 +0300, Michael S. Tsirkin wrote:
> On Mon, Oct 12, 2015 at 06:17:54PM +0300, Marcel Apfelbaum wrote:
> > The virtio devices are converted to PCI-Express
> > if they are plugged into a PCI-Express bus and
> > the 'modern' protocol is enabled.
> >
> > Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
> > ---
> >
> > This is an RFC because all it does it adds the PCIe capability and nothing more.
>
> Express capability is easy.
> But if you go over express space you will see that a bunch of
> other capabilities are required, such as PM capability etc.
> These might need more work.
Also what about the legacy io bar? I guess we'd better avoid that for
express devices.
Maybe it makes sense to add virtio-*-pcie devices (virtio-1.0 only, with
pcie caps)?
cheers,
Gerd
next prev parent reply other threads:[~2015-10-13 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 15:17 [Qemu-devel] [PATCH RFC] hw/virtio: Add PCIe capability to virtio devices Marcel Apfelbaum
2015-10-12 15:42 ` Michael S. Tsirkin
2015-10-13 8:13 ` Gerd Hoffmann [this message]
2015-10-13 8:44 ` Michael S. Tsirkin
2015-10-13 14:31 ` Marcel Apfelbaum
2015-10-13 14:47 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2015-10-13 8:41 [Qemu-devel] [PATCH v3 0/2] PCI-e device multi-function hot-add support Cao jin
2015-10-13 8:41 ` [Qemu-devel] [PATCH v3 2/2] remove function during multi-function hot-add Cao jin
2015-10-13 8:48 ` [Qemu-devel] [PATCH RFC] hw/virtio: Add PCIe capability to virtio devices Michael S. Tsirkin
2015-10-13 12:19 ` Cao jin
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=1444724017.19915.35.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=marcel@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).