From: Peter Xu <peterx@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Lloret, Luis" <luis_lloret@mentor.com>
Subject: Re: [Qemu-devel] [PATCH v2] intel-iommu: Accept 64-bit writes to FEADDR
Date: Mon, 26 Feb 2018 10:54:18 +0800 [thread overview]
Message-ID: <20180226025418.GO18962@xz-mi> (raw)
In-Reply-To: <2f5781cc-ced4-6df0-906e-cd456d722a6e@web.de>
On Sat, Feb 24, 2018 at 09:30:12AM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Xen is doing this [1] and currently triggers an abort.
>
> [1] http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=xen/drivers/passthrough/vtd/iommu.c;h=daaed0abbdd06b6ba3d948ea103aadf02651e83c;hb=refs/heads/master#l1108
>
> Reported-by: Luis Lloret <luis_lloret@mentor.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Thanks, Jan.
Reviewed-by: Peter Xu <peterx@redhat.com>
> ---
> hw/i386/intel_iommu.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index 2e841cde27..fb31de9416 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -2129,8 +2129,15 @@ static void vtd_mem_write(void *opaque, hwaddr addr,
>
> /* Fault Event Address Register, 32-bit */
> case DMAR_FEADDR_REG:
> - assert(size == 4);
> - vtd_set_long(s, addr, val);
> + if (size == 4) {
> + vtd_set_long(s, addr, val);
> + } else {
> + /*
> + * While the register is 32-bit only, some guests (Xen...) write to
> + * it with 64-bit.
> + */
> + vtd_set_quad(s, addr, val);
> + }
> break;
>
> /* Fault Event Upper Address Register, 32-bit */
--
Peter Xu
prev parent reply other threads:[~2018-02-26 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 11:26 [Qemu-devel] [PATCH] intel-iommu: Accept 64-bit writes to FEADDR Jan Kiszka
2018-02-22 4:40 ` Peter Xu
2018-02-24 8:30 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2018-02-26 2:54 ` 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=20180226025418.GO18962@xz-mi \
--to=peterx@redhat.com \
--cc=jan.kiszka@web.de \
--cc=luis_lloret@mentor.com \
--cc=mst@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 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).