From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Yi Liu <yi.l.liu@intel.com>, Yi Sun <yi.y.sun@linux.intel.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] intel_iommu: misc scalable mode fixes for 4.0
Date: Wed, 3 Apr 2019 16:58:02 +0800 [thread overview]
Message-ID: <20190403085802.GA3453@xz-x1> (raw)
In-Reply-To: <20190329061422.7926-1-peterx@redhat.com>
On Fri, Mar 29, 2019 at 02:14:20PM +0800, Peter Xu wrote:
> v2:
> - patch 2: use "1" instead of "sizeof(bool)" for VMSTATE_UNUSED
> because sizeof(bool) can be >1 depends on definition [Dave]
>
> The first patch is the important one. It should fix up a migration
> issue that Dave reported between 3.1<->4.0. The second patch is born
> only because I noticed it when drafting patch 1 and I think we can
> probably do that too together as a fixup to the scalable patchset for
> 4.0.
Ping - just want to make sure this series won't miss 4.0. Thanks,
--
Peter Xu
parent reply other threads:[~2019-04-03 8:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190329061422.7926-1-peterx@redhat.com>]
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=20190403085802.GA3453@xz-x1 \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@linux.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).