qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Meador Inge <meadori@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi, paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Probe the guest memory space when using -R
Date: Wed, 1 Aug 2012 13:47:06 -0500	[thread overview]
Message-ID: <501979AA.9030606@codesourcery.com> (raw)
In-Reply-To: <1343357402-20685-1-git-send-email-meadori@codesourcery.com>

Ping.

On 07/26/2012 09:50 PM, Meador Inge wrote:
> Hi,
> 
> This patch series fixes an issue that was discussed here [1] where using -R
> can cause QEMU to fail to setup the guest address space because the guest base
> validation fails.  I fixed this issue by (1) refactoring the guest space
> probing code into a single function for initializing the guest space and (2) by 
> calling the guest space initialization code for both the case of reserving the
> guest space upfront (-R) and the case where the initial memory space base/size
> are gleaned from an ELF image.
> 
> Tested by going through various combinations of -R <size>, -B <base>,
> -B <base> -R <size>, and neither -R or -B passed.  I also ran the libstdc++
> testsuite through the MIPS, ARM, and Power usermode emulators with -R set.
> No regressions.
> 
> NOTE: This does not fix the problem that was raised concerning mapped the
> full 32-bit address space on a 64-bit system.  That will need to be another
> patch.
> 
> - Changes since v1:
> 
>    * Replaced '!host_start && !host_size' error check in 'init_guest_space'
>      with an assert.
> 
>    * Ensured that 'guest_validate_base' is passed the true guest base instead
>      of the current host start address.
> 
>    * s/init_guest_space(..., 0)/init_guest_space(..., false);/
> 
>    * Fixed typo in 'init_guest_space' header comment.
> 
> [1] http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg04508.html
> 
> Signed-off-by: Meador Inge <meadori@codesourcery.com>
> 
> Meador Inge (2):
>   linux-user: Factor out guest space probing into a function
>   linux-user: Use init_guest_space when -R and -B are specified
> 
>  linux-user/elfload.c |  161 ++++++++++++++++++++++++++++++++++++++------------
>  linux-user/main.c    |   35 ++---------
>  linux-user/qemu.h    |   15 ++++-
>  3 files changed, 140 insertions(+), 71 deletions(-)
> 


-- 
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software

  parent reply	other threads:[~2012-08-01 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  2:50 [Qemu-devel] [PATCH v2 0/2] Probe the guest memory space when using -R Meador Inge
2012-07-27  2:50 ` [Qemu-devel] [PATCH v2 1/2] linux-user: Factor out guest space probing into a function Meador Inge
2012-08-13 14:51   ` Peter Maydell
2012-07-27  2:50 ` [Qemu-devel] [PATCH v2 2/2] linux-user: Use init_guest_space when -R and -B are specified Meador Inge
2012-08-13 14:52   ` Peter Maydell
2012-08-13 16:08     ` Meador Inge
2012-08-01 18:47 ` Meador Inge [this message]
2012-08-10 21:35   ` [Qemu-devel] [PATCH v2 0/2] Probe the guest memory space when using -R Meador Inge

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=501979AA.9030606@codesourcery.com \
    --to=meadori@codesourcery.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).