From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, patches@linaro.org,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
"Brad Smith" <brad@comstyle.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v2] bsd-user: fix compile failure
Date: Thu, 12 Apr 2012 18:35:26 +0200 [thread overview]
Message-ID: <4F87044E.3000000@weilnetz.de> (raw)
In-Reply-To: <1334231021-25886-1-git-send-email-peter.maydell@linaro.org>
Am 12.04.2012 13:43, schrieb Peter Maydell:
> bsd-user doesn't actually support reserving a memory area for the
> guest address space, but we need to at least define the reserved_va
> global so that cpu-all.h's RESERVED_VA macro will work correctly.
>
> This fixes a compilation error introduced in commit 39879bb
> which added a use of RESERVED_VA to h2g_valid().
>
> Reported-by: Brad Smith<brad@comstyle.com>
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
> v1->v2 changes: added commit hash accidentally omitted from message
> added reported-by line. no code change.
>
> bsd-user/main.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/bsd-user/main.c b/bsd-user/main.c
> index 48cb715..0689e38 100644
> --- a/bsd-user/main.c
> +++ b/bsd-user/main.c
> @@ -41,6 +41,7 @@ int singlestep;
> unsigned long mmap_min_addr;
> unsigned long guest_base;
> int have_guest_base;
> +unsigned long reserved_va;
> #endif
>
> static const char *interp_prefix = CONFIG_QEMU_INTERP_PREFIX;
Reviewed-by: Stefan Weil <sw@weilnetz.de>
I'll send a patch which changes the data type to uintptr_t later
with my w64 patches.
next prev parent reply other threads:[~2012-04-12 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 11:43 [Qemu-trivial] [PATCH v2] bsd-user: fix compile failure Peter Maydell
2012-04-12 16:35 ` Stefan Weil [this message]
2012-04-13 8:57 ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
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=4F87044E.3000000@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=brad@comstyle.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).