All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: Jan Kiszka <jan.kiszka-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] qemu: fix some warnings
Date: Mon, 21 Jan 2008 08:22:59 -0600	[thread overview]
Message-ID: <20080121142259.GC28468@tapir> (raw)
In-Reply-To: <47949413.4060804-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>

On Mon, Jan 21, 2008 at 01:46:11PM +0100, Jan Kiszka wrote:
> Here are 4 more warnings fixes (actually, I should sent 2 of them to
> qemu...). Nothing critical, just less noise during compilation.

probably a good idea having them in independent patches as they are unrelated
(other by the fact that they are all warnings in current git).

> Index: b/qemu/vl.c
> ===================================================================
> --- a/qemu/vl.c
> +++ b/qemu/vl.c
> @@ -8862,7 +8862,7 @@ int main(int argc, char **argv)
>                  if (ram_size <= 0)
>                      help(1);
>                  if (ram_size > PHYS_RAM_MAX_SIZE) {
> -                    fprintf(stderr, "qemu: at most %d MB RAM can be simulated\n",
> +                    fprintf(stderr, "qemu: at most %llu MB RAM can be simulated\n",
>                              PHYS_RAM_MAX_SIZE / (1024 * 1024));

using TARGET_FMT_lu instead of "%llu" would seem more appropriate here because
this is meant to reflect a physical memory address, but then the fact that kvm
is using the x64_64 target also for 32 bit will mean that the definition of
PHYS_RAM_MAX_SIZE has to be made somehow also HOST specific.

for my take on that (which will need to be updated with your version of the 
exec.c changes and re-tested) look at :

  http://tapir.sajinet.com.pe/gentoo/portage/app-emulation/kvm/files/kvm-51-qemu-ramaddr.patch

Carlo

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-01-21 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 12:46 [PATCH] qemu: fix some warnings Jan Kiszka
     [not found] ` <47949413.4060804-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2008-01-21 13:06   ` Jan Kiszka
     [not found]     ` <479498B9.1000005-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2008-01-21 14:00       ` Carlo Marcelo Arenas Belon
2008-01-24  6:34       ` Avi Kivity
2008-01-21 14:22   ` Carlo Marcelo Arenas Belon [this message]
2008-01-22 10:06     ` Jan Kiszka

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=20080121142259.GC28468@tapir \
    --to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
    --cc=jan.kiszka-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.