From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] intel_iommu: handle invalid ce for shadow sync
Date: Tue, 23 Oct 2018 23:17:37 +0100 [thread overview]
Message-ID: <20181023221712.GA12892@xz-x1.hotspot.internet-for-guests.com> (raw)
In-Reply-To: <20181009074543.6013-1-peterx@redhat.com>
Hi, Michael,
Just a kind reminder that this series has got enough ACKs and please
consider to merge it in your next pull. Thanks!
On Tue, Oct 09, 2018 at 03:45:41PM +0800, Peter Xu wrote:
> v3:
> - pick r-b
> - return when -VTD_FR_CONTEXT_ENTRY_P is detected (v1 is correct here,
> but I did wrong thing when splitting the patch in v2) [Eric]
>
> v2:
> - split patch into more, remove useless comment [Eric]
> - remove one error_report_once() when rework the code [Jason]
>
> This series fixes a QEMU crash reported here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1627272
>
> Please review, thanks.
>
> Peter Xu (2):
> intel_iommu: move ce fetching out when sync shadow
> intel_iommu: handle invalid ce for shadow sync
>
> dtc | 2 +-
> hw/i386/intel_iommu.c | 55 +++++++++++++++++++++++--------------------
> 2 files changed, 30 insertions(+), 27 deletions(-)
>
> --
> 2.17.1
>
Regards,
--
Peter Xu
prev parent reply other threads:[~2018-10-23 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:45 [Qemu-devel] [PATCH v3 0/2] intel_iommu: handle invalid ce for shadow sync Peter Xu
2018-10-09 7:45 ` [Qemu-devel] [PATCH v3 1/2] intel_iommu: move ce fetching out when sync shadow Peter Xu
2018-10-09 7:45 ` [Qemu-devel] [PATCH v3 2/2] intel_iommu: handle invalid ce for shadow sync Peter Xu
2018-10-09 7:55 ` Auger Eric
2018-10-09 8:59 ` [Qemu-devel] [PATCH v3 0/2] " Maxime Coquelin
2018-10-23 22:17 ` Peter Xu [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=20181023221712.GA12892@xz-x1.hotspot.internet-for-guests.com \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=pezhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.