From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC for-1.6 qom-next 0/3] PCIe VMState cleanups for 1.6
Date: Sun, 28 Jul 2013 18:52:40 +0300 [thread overview]
Message-ID: <20130728155240.GA7458@redhat.com> (raw)
In-Reply-To: <51F531C6.8010302@suse.de>
On Sun, Jul 28, 2013 at 04:59:18PM +0200, Andreas Färber wrote:
> Am 28.07.2013 16:08, schrieb Michael S. Tsirkin:
> > On Sun, Jul 28, 2013 at 03:41:07AM +0200, Andreas Färber wrote:
> >> Hello Michael and Gerd,
> >>
> >> As discussed, this series attempts to clean up PCIe devices fiddling with
> >> individual PCIe VMState fields. It is based on my qom-next queue, containing
> >> type and field changes for PCIe devices.
> >>
> >> Patch 1 assumes the following are equivalent:
> >> a) - Struct A
> >> - Field Aa
> >> ...
> >> - Field X
> >> ...
> >> b) - Struct A
> >> - Field Aa
> >> ...
> >> - Field X
> >>
> >> Patch 2 relies on XHCI not being released yet, thus no compatibiliy concerns.
> >>
> >> Patch 3 assumes the following are equivalent:
> >> a) - Struct A
> >> - Field Aa
> >> ...
> >> - Field X
> >> b) - Struct A
> >> - Field Aa
> >> ...
> >> - Subsection Ax
> >> - Field X
> >>
> >> CC'ing Juan to verify which of these are correct/safe.
> >
> > As far as I know 2a and 2b are not equivalent: subsections
> > are serialized in the file.
>
> I'm guessing you mean scenarios 3a and 3b. Too bad.
>
> But when we want to unify PCI and PCIe as you suggested elsewhere,
> introducing a PCIe-only subsection in patch 2 seems a bad idea.
>
> In that case we could use VMSTATE_STRUCT_TEST(), I'll look into that.
Right.
> Using that I think we can postpone this beyond 1.6, since XHCI is not
> initializing AER.
>
> Series formally retracted.
>
> > You really should test by migrating to file (e.g. before
> > starting the guest) and checking.
> > Also, migrate to file from before patch and load after patch.
>
> OK. For virtio and NICs that's trivial and for the ioh there's
> docs/q35-chipset.cfg.
>
> How do I use and test those xio upstream/downstream PCIe devices?
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-07-28 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 1:41 [Qemu-devel] [PATCH RFC for-1.6 qom-next 0/3] PCIe VMState cleanups for 1.6 Andreas Färber
2013-07-28 1:41 ` [Qemu-devel] [PATCH RFC for-1.6 qom-next 1/3] pcie: Move AER log into VMSTATE_PCIE_DEVICE() Andreas Färber
2013-07-28 1:41 ` [Qemu-devel] [PATCH RFC for-1.6 qom-next 2/3] pci: Add MSIX subsection for vmstate_pcie_device Andreas Färber
2013-07-28 1:41 ` [Qemu-devel] [PATCH RFC for-1.6 qom-next 3/3] pci: Move AER log into VMStateSubsection Andreas Färber
2013-07-28 13:44 ` [Qemu-devel] [PATCH RFC for-1.6 qom-next 0/3] PCIe VMState cleanups for 1.6 Andreas Färber
2013-07-28 14:26 ` Andreas Färber
2013-07-28 14:08 ` Michael S. Tsirkin
2013-07-28 14:59 ` Andreas Färber
2013-07-28 15:52 ` Michael S. Tsirkin [this message]
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=20130728155240.GA7458@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).