qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Zeng Guang <guang.zeng@intel.com>
Cc: Juan Quintela <quintela@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	wei.w.wang@intel.com, Jiri Slaby <jslaby@suse.cz>,
	chao.gao@intel.com
Subject: Re: [PATCH v2] hw/misc/edu: support pci device state migration
Date: Thu, 23 Jul 2020 11:39:45 +0100	[thread overview]
Message-ID: <CAFEAcA94d5s6fqabi39pVQnJPJrwXOkk4XeTMmCMD_ji7Vh4Hg@mail.gmail.com> (raw)
In-Reply-To: <20200723084355.18370-1-guang.zeng@intel.com>

On Thu, 23 Jul 2020 at 10:01, Zeng Guang <guang.zeng@intel.com> wrote:
>
> Currently edu device doesn't support live migration. Part of PCI
> configuration information would be lost after migration.
>
> PCI device state in source VM:
>      Bus  0, device   3, function 0:
>      Class 0255: PCI device 1234:11e8
>      PCI subsystem 1af4:1100
>      IRQ 11, pin A
>      BAR0: 32 bit memory at 0xfea00000 [0xfeafffff].
>      id ""
>
> PCI device state in destination VM:
>      Bus  0, device   3, function 0:
>      Class 0255: PCI device 1234:11e8
>      PCI subsystem 1af4:1100
>      IRQ 0, pin A
>      BAR0: 32 bit memory at 0xffffffffffffffff [0x000ffffe].
>      id ""
>
> Add VMState for edu device to support migration.
>
> Signed-off-by: Gao Chao <chao.gao@intel.com>
> Signed-off-by: Zeng Guang <guang.zeng@intel.com>
> Reviewed-by: Wei Wang <wei.w.wang@intel.com>


Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

thanks
-- PMM


      reply	other threads:[~2020-07-23 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  8:43 [PATCH v2] hw/misc/edu: support pci device state migration Zeng Guang
2020-07-23 10:39 ` Peter Maydell [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=CAFEAcA94d5s6fqabi39pVQnJPJrwXOkk4XeTMmCMD_ji7Vh4Hg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=chao.gao@intel.com \
    --cc=david@redhat.com \
    --cc=guang.zeng@intel.com \
    --cc=jslaby@suse.cz \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wei.w.wang@intel.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).