From: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 for-2.5] virtio-pci: Set the QEMU_PCI_CAP_EXPRESS capability early in its DeviceClass realize method
Date: Wed, 2 Dec 2015 19:12:47 +0200 [thread overview]
Message-ID: <20151202191247.7326c7a3@halley> (raw)
In-Reply-To: <20151202184610-mutt-send-email-mst@redhat.com>
Hi Michael,
On Wed, 2 Dec 2015 18:49:24 +0200 "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Dec 02, 2015 at 05:11:28PM +0200, Marcel Apfelbaum wrote:
> > The only thing I want to mention here, (see earlier discussion: https://www.mail-archive.com/qemu-devel@nongnu.org/msg338963.html)
> > is that in some cases the PCI config space will have PCIe length, even if the device is not express.
> >
> > To be more precise, the only interesting scenario is when we plug a virtio device directly into
> > the root complex, in this case we'll have a PCI device with a PCIe config space.
> >
> > However this happens for other devices as well, it looks like a common practice.
>
> Problem is, if this happens migration breaks as we
> changed config space size from 2.4.
Correct me if wrong, but as long as a pre 2.5 hardware is used, Marcel's
x-disable-pcie gets on (see HW_COMPAT_2_4), thus the device will not be
a "pci_is_express", and it will have a small config space size. Isn't it
so?
Regards,
Shmulik
next prev parent reply other threads:[~2015-12-02 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:33 [Qemu-devel] [PATCH v2 for-2.5] virtio-pci: Set the QEMU_PCI_CAP_EXPRESS capability early in its DeviceClass realize method Shmulik Ladkani
2015-12-02 15:11 ` Marcel Apfelbaum
2015-12-02 16:49 ` Michael S. Tsirkin
2015-12-02 17:12 ` Shmulik Ladkani [this message]
2015-12-02 17:19 ` Michael S. Tsirkin
2015-12-02 17:21 ` Marcel Apfelbaum
2015-12-02 17:22 ` Michael S. Tsirkin
2015-12-02 17:50 ` Shmulik Ladkani
2015-12-02 17:09 ` Michael S. Tsirkin
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=20151202191247.7326c7a3@halley \
--to=shmulik.ladkani@ravellosystems.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).