qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC qom-next 4/4] pcie_port: Turn PCIEPort and PCIESlot into abstract QOM types
Date: Tue, 23 Jul 2013 13:21:13 +0200	[thread overview]
Message-ID: <51EE6729.1010403@redhat.com> (raw)
In-Reply-To: <51EE593F.4090101@suse.de>

  Hi,

> Okay, so if it's just PCIe, then XHCI is the oddball preventing moving
> it into VMSTATE_PCIE_DEVICE(). XHCI has VMSTATE_MSIX() in its place,
> also operating on PCIDevice.

Given that live migration support for xhci was added post-1.5 so we
don't have a release with it yet this shouldn't be a blocker in case we
get this sorted in time for 1.6.

> Is there a way to detect use of AER or MSIX to place those into
> subsections of VMSTATE_PCIE_DEVICE()?

There is msix_enabled() ...

Dunno about AER.

cheers,
  Gerd

  reply	other threads:[~2013-07-23 11:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-21 14:09 [Qemu-devel] [PATCH RFC qom-next 0/4] QOM'ification of pci-bridge types Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 1/4] pci-bridge: Turn into abstract QOM type Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 2/4] pci-bridge-dev: QOM parent field cleanup Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 3/4] pci-bridge/i82801b11: Rename parent field Andreas Färber
2013-07-21 14:09 ` [Qemu-devel] [PATCH RFC qom-next 4/4] pcie_port: Turn PCIEPort and PCIESlot into abstract QOM types Andreas Färber
2013-07-21 20:26   ` Michael S. Tsirkin
2013-07-22 17:42     ` Andreas Färber
2013-07-22 19:34       ` Michael S. Tsirkin
2013-07-22 20:29     ` Anthony Liguori
2013-07-22 21:04       ` Andreas Färber
2013-07-23  7:07         ` Michael S. Tsirkin
2013-07-23  9:10           ` Andreas Färber
2013-07-23  9:59             ` Michael S. Tsirkin
2013-07-23 10:21               ` Andreas Färber
2013-07-23 11:21                 ` Gerd Hoffmann [this message]
2013-07-23 12:35                   ` Michael S. Tsirkin
2013-07-23  7:04       ` Michael S. Tsirkin
2013-07-28 12:36       ` Andreas Färber
2013-07-28 12:58         ` Michael S. Tsirkin
2013-07-21 20:26 ` [Qemu-devel] [PATCH RFC qom-next 0/4] QOM'ification of pci-bridge types Michael S. Tsirkin
2013-07-22 17:22   ` Andreas Färber
2013-07-22 22:05     ` Andreas Färber

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=51EE6729.1010403@redhat.com \
    --to=kraxel@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=mst@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).