From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] linux-user: Detect and fix 32-bit guest on 64-bit host issues - v2
Date: Thu, 21 Aug 2008 14:41:12 -0500 [thread overview]
Message-ID: <48ADC4D8.2000001@codemonkey.ws> (raw)
In-Reply-To: <48A69B64.7050001@web.de>
Jan Kiszka wrote:
> This series deals with address space mapping issues around h2g/g2h that
> currently exist on 64-bit hosts running 32-bit Linux user-space guests.
>
> The first 3 patches are taken unmodified from -v1 of this series (except
> for a compiler warning fix in 2). The 4th and 5th are new, hopefully
> addressing the bug in page_find_alloc correctly now.
>
> This series fixes the problem reported here:
>
> http://permalink.gmane.org/gmane.comp.emulators.qemu/26987
>
linux-user currently lacks a maintainer so I don't know who the right
person is to review these patches. I'm not at all familiar with the
code myself.
Regards,
Anthony Liguori
> Jan
>
>
>
>
>
prev parent reply other threads:[~2008-08-21 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 9:28 [Qemu-devel] [PATCH 0/5] linux-user: Detect and fix 32-bit guest on 64-bit host issues - v2 Jan Kiszka
2008-08-16 9:24 ` [Qemu-devel] [PATCH 1/5] linux-user: Safety belt for h2g Jan Kiszka
2008-08-16 9:28 ` [Qemu-devel] [PATCH 2/5] linux-user: Introduce qemu_vmalloc_guest_safe Jan Kiszka
2008-08-16 9:30 ` [Qemu-devel] [PATCH 3/5] linux-user: Allocate guest-reachable descriptor tables Jan Kiszka
2008-08-16 9:38 ` [Qemu-devel] [PATCH 5/5] linux-user: Fix h2g usage in page_find_alloc Jan Kiszka
2008-08-16 9:39 ` [Qemu-devel] [PATCH 4/5] linux-user: Introduce h2g_valid Jan Kiszka
2008-08-21 19:41 ` 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=48ADC4D8.2000001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.