From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/4] virtio-pci: add flags to enable/disable legacy/modern
Date: Wed, 18 Feb 2015 11:32:55 +0100 [thread overview]
Message-ID: <1424255575.6014.54.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1424163833.6014.25.camel@nilsson.home.kraxel.org>
On Di, 2015-02-17 at 10:03 +0100, Gerd Hoffmann wrote:
> On Di, 2015-02-17 at 09:42 +0100, Michael S. Tsirkin wrote:
> > On Tue, Feb 17, 2015 at 09:23:35AM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > Should we forbid setting both legacy and modern at the same time?
> > >
> > > No, this is explicitly allowed in the spec and it is needed for the
> > > transition from legacy to modern.
> > >
> > > cheers,
> > > Gerd
> >
> > But !legacy && !modern aren't legal together, correct?
>
> That doesn't make sense indeed.
What is the state of markus "convert pci to realize" patch series btw?
Convert virtio-pci too, then throw an error in virtio_pci_realize would
be the best way to catch this I think.
cheers,
Gerd
next prev parent reply other threads:[~2015-02-18 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 16:33 [Qemu-devel] [PATCH v2 0/4] virtio-pci: a few proxy tweaks Gerd Hoffmann
2015-02-16 16:33 ` [Qemu-devel] [PATCH v2 1/4] virtio-pci: add flags to enable/disable legacy/modern Gerd Hoffmann
2015-02-17 5:12 ` Fam Zheng
2015-02-17 8:23 ` Gerd Hoffmann
2015-02-17 8:42 ` Michael S. Tsirkin
2015-02-17 9:03 ` Gerd Hoffmann
2015-02-18 10:32 ` Gerd Hoffmann [this message]
2015-02-18 11:40 ` Michael S. Tsirkin
2015-02-16 16:33 ` [Qemu-devel] [PATCH v2 2/4] virtio-pci: make QEMU_VIRTIO_PCI_QUEUE_MEM_MULT smaller Gerd Hoffmann
2015-02-16 16:33 ` [Qemu-devel] [PATCH v2 3/4] virtio-pci: make pci bars configurable Gerd Hoffmann
2015-02-16 16:33 ` [Qemu-devel] [PATCH v2 4/4] virtio-pci: make modern bar 64bit prefetchable Gerd Hoffmann
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=1424255575.6014.54.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.com \
--cc=famz@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).