From: Wei Liu <wei.liu2@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH qemu-traditional] ioreq: Support 32-bit default_ioport_* accesses
Date: Mon, 23 May 2016 14:42:52 +0100 [thread overview]
Message-ID: <20160523134252.GA22076@citrix.com> (raw)
In-Reply-To: <1463752360-11311-1-git-send-email-boris.ostrovsky@oracle.com>
On Fri, May 20, 2016 at 09:52:40AM -0400, Boris Ostrovsky wrote:
> Recent changes in ACPICA (specifically, Linux commit 66b1ed5aa8dd ("ACPICA:
> ACPI 2.0, Hardware: Add access_width/bit_offset support for
> acpi_hw_write()") result in guests issuing 32-bit accesses to IO space.
>
> QEMU needs to be able to handle them.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-23 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 13:52 [PATCH qemu-traditional] ioreq: Support 32-bit default_ioport_* accesses Boris Ostrovsky
2016-05-23 12:02 ` Wei Liu
2016-05-23 13:02 ` Boris Ostrovsky
2016-05-23 13:05 ` Wei Liu
2016-05-23 13:42 ` Wei Liu [this message]
2016-05-25 14:26 ` Ian Jackson
2016-05-25 14:35 ` Ian Jackson
2016-05-25 15:08 ` Boris Ostrovsky
2016-05-25 15:22 ` Ian Jackson
2016-05-25 15:36 ` Boris Ostrovsky
2016-05-25 16:03 ` Jan Beulich
2016-05-25 16:09 ` Ian Jackson
2016-05-25 16:51 ` Boris Ostrovsky
2016-05-25 16:57 ` Boris Ostrovsky
2016-05-26 14:00 ` Ian Jackson
2016-05-25 16:02 ` Jan Beulich
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=20160523134252.GA22076@citrix.com \
--to=wei.liu2@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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).