From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking
Date: Mon, 22 Aug 2011 09:42:06 -0500 [thread overview]
Message-ID: <4E526ABE.6060402@codemonkey.ws> (raw)
In-Reply-To: <1313048426-17273-1-git-send-email-avi@redhat.com>
On 08/11/2011 02:40 AM, Avi Kivity wrote:
> The memory API automatically cracks wide memory accesses into narrower
> (usually byte) accesses when needed. Unfortunately this wasn't implemented
> for ioports, leading to an lsi53c895a failure.
>
> This series implements cracking for ioports as well.
>
> Note that the dual implementation is due to the fact the memory API is layered
> on top of the original qemu API; eventually the same code will be used for
> both ioports and mmio.
>
> Avi Kivity (2):
> memory: abstract cracking of write access ops into a function
> memory: crack wide ioport accesses into smaller ones when needed
>
> memory.c | 120 +++++++++++++++++++++++++++++++++++++++----------------------
> 1 files changed, 77 insertions(+), 43 deletions(-)
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2011-08-22 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 7:40 [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking Avi Kivity
2011-08-11 7:40 ` [Qemu-devel] [PATCH 1/2] memory: abstract cracking of write access ops into a function Avi Kivity
2011-08-11 7:40 ` [Qemu-devel] [PATCH 2/2] memory: crack wide ioport accesses into smaller ones when needed Avi Kivity
2011-08-11 8:25 ` [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking Gerhard Wiesinger
2011-08-11 8:27 ` Avi Kivity
2011-08-11 8:29 ` Avi Kivity
2011-08-11 9:01 ` Gerhard Wiesinger
2011-08-11 9:44 ` Avi Kivity
2011-08-11 16:08 ` Gerhard Wiesinger
2011-08-11 16:20 ` Avi Kivity
2011-08-11 16:22 ` Avi Kivity
2011-08-11 19:01 ` Gerhard Wiesinger
2011-08-22 10:46 ` Avi Kivity
2011-08-11 16:11 ` Gerhard Wiesinger
2011-08-11 16:15 ` Avi Kivity
2011-08-22 14:42 ` Anthony Liguori [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=4E526ABE.6060402@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lists@wiesinger.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).