qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <don.slutz@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: hpoussin@reactos.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH 0/2] exec: fixes for access clamping
Date: Thu, 18 Jun 2015 17:31:39 -0400	[thread overview]
Message-ID: <558338BB.5080106@Gmail.com> (raw)
In-Reply-To: <1434642231-24608-1-git-send-email-pbonzini@redhat.com>

On 06/18/15 11:43, Paolo Bonzini wrote:
> The first patch fixes the remaining problems with Peter Crosthwaite's
> access clamping patch (which broke kvmvapic and hence Windows XP/2003).
> The second patch actually puts the clamping to good use: by fixing
> address_space_translate_internal, the MIPS rc4030 emulation does not need
> anymore the address_space_rw hack.
> 
> Please test!
> 

My testing on vmport says that this change also fixed:

Subject: [BUGFIX][PATCH v7 1/9] vmport: The io memory region needs to be
at least a size of 4
Date: Fri, 12 Jun 2015 10:05:48 -0400
Message-Id: <1434117956-4929-2-git-send-email-dslutz@verizon.com>

So as long as this change goes in, the patch "vmport: The io memory
region" will be dropped.

   -Don Slutz

> Paolo
> 
> Paolo Bonzini (2):
>   exec: do not clamp accesses to MMIO regions
>   exec: clamp accesses against the MemoryRegionSection
> 
>  exec.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 

  parent reply	other threads:[~2015-06-18 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 15:43 [Qemu-devel] [PATCH 0/2] exec: fixes for access clamping Paolo Bonzini
2015-06-18 15:43 ` [Qemu-devel] [PATCH 1/2] exec: do not clamp accesses to MMIO regions Paolo Bonzini
2015-06-18 15:43 ` [Qemu-devel] [PATCH 2/2] exec: clamp accesses against the MemoryRegionSection Paolo Bonzini
2015-06-18 19:32 ` [Qemu-devel] [PATCH 0/2] exec: fixes for access clamping Hervé Poussineau
2015-06-18 21:31 ` Don Slutz [this message]
2015-06-18 23:09 ` Mark Cave-Ayland

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=558338BB.5080106@Gmail.com \
    --to=don.slutz@gmail.com \
    --cc=aurelien@aurel32.net \
    --cc=hpoussin@reactos.org \
    --cc=pbonzini@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).