From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH] address_space_translate: do not cross page boundaries
Date: Thu, 30 Jan 2014 14:38:46 +0100 [thread overview]
Message-ID: <52EA55E6.90708@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401301223350.4373@kaball.uk.xensource.com>
Il 30/01/2014 13:46, Stefano Stabellini ha scritto:
> The following commit:
>
> commit 149f54b53b7666a3facd45e86eece60ce7d3b114
> Author: Paolo Bonzini <pbonzini@redhat.com>
> Date: Fri May 24 12:59:37 2013 +0200
>
> memory: add address_space_translate
>
> breaks Xen support in QEMU, in particular the Xen mapcache. The effect
> is that one Windows XP installation out of ten would end up with BSOD.
>
> The reason is that after this commit l in address_space_rw can span a
> page boundary, however qemu_get_ram_ptr still calls xen_map_cache asking
> to map a single page (if block->offset == 0).
>
> Fix the issue by reverting to the previous behaviour: do not return a
> length from address_space_translate_internal that can span a page
> boundary.
>
> Also in address_space_translate do not ignore the length returned by
> address_space_translate_internal.
>
> This patch should be backported to QEMU 1.6.x.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Signed-off-by: Anthony Perard <anthony.perard@citrix.com>
Tested-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-stable@nongnu.org
> ---
> exec.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 667a718..f3797b7 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -251,7 +251,7 @@ address_space_translate_internal(AddressSpaceDispatch *d, hwaddr addr, hwaddr *x
> hwaddr *plen, bool resolve_subpage)
> {
> MemoryRegionSection *section;
> - Int128 diff;
> + Int128 diff, diff_page;
>
> section = address_space_lookup_region(d, addr, resolve_subpage);
> /* Compute offset within MemoryRegionSection */
> @@ -260,7 +260,9 @@ address_space_translate_internal(AddressSpaceDispatch *d, hwaddr addr, hwaddr *x
> /* Compute offset within MemoryRegion */
> *xlat = addr + section->offset_within_region;
>
> + diff_page = int128_make64(((addr & TARGET_PAGE_MASK) + TARGET_PAGE_SIZE) - addr);
> diff = int128_sub(section->mr->size, int128_make64(addr));
> + diff = int128_min(diff, diff_page);
> *plen = int128_get64(int128_min(diff, int128_make64(*plen)));
> return section;
> }
> @@ -275,7 +277,7 @@ MemoryRegion *address_space_translate(AddressSpace *as, hwaddr addr,
> hwaddr len = *plen;
>
> for (;;) {
> - section = address_space_translate_internal(as->dispatch, addr, &addr, plen, true);
> + section = address_space_translate_internal(as->dispatch, addr, &addr, &len, true);
> mr = section->mr;
>
> if (!mr->iommu_ops) {
>
>
prev parent reply other threads:[~2014-01-30 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 12:46 [PATCH] address_space_translate: do not cross page boundaries Stefano Stabellini
2014-01-30 13:38 ` Paolo Bonzini [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=52EA55E6.90708@redhat.com \
--to=pbonzini@redhat.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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).