qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: qemu-devel@nongnu.org, alistair23@gmail.com, armbru@redhat.com,
	pbonzini@redhat.com, Don Slutz <dslutz@verizon.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/7] hw/i386: Improve some of the warning messages
Date: Mon, 4 Sep 2017 11:17:48 -0300	[thread overview]
Message-ID: <20170904141748.GU7570@localhost.localdomain> (raw)
In-Reply-To: <5bf40ca8376c537ac05dd848a84e072a88a1d939.1504228916.git.alistair.francis@xilinx.com>

On Fri, Sep 01, 2017 at 09:51:05AM -0700, Alistair Francis wrote:
[...]
> diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
> index 169a214d50..435eb2c458 100644
> --- a/hw/i386/pc_q35.c
> +++ b/hw/i386/pc_q35.c
> @@ -101,9 +101,11 @@ static void pc_q35_init(MachineState *machine)
>          lowmem = pcms->max_ram_below_4g;
>          if (machine->ram_size - lowmem > lowmem &&
>              lowmem & ((1ULL << 30) - 1)) {
> -            warn_report("Large machine and max_ram_below_4g(%"PRIu64
> -                        ") not a multiple of 1G; possible bad performance.",
> -                        pcms->max_ram_below_4g);
> +            warn_report("Large machine as the ram size (0x%" PRIx64 ") is more"
> +                        " then twice the size of the internal limit"
> +                        " (0x%" PRIx64 ") and max-ram-below-4g (%"PRIu64")"
> +                        " note a multiple of 1G; possible bad performance.",
> +                        machine->ram_size, lowmem, pcms->max_ram_below_4g);

Here lowmem and max_ram_below_4g have exactly the same value,
don't they?  There's no internal limit involved in this logic,
only max_ram_below_4g and ram_size.

-- 
Eduardo

  reply	other threads:[~2017-09-04 14:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 16:51 [Qemu-devel] [PATCH v3 0/7] More warning reporting fixed Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 1/7] hw/i386: Improve some of the warning messages Alistair Francis
2017-09-04 14:17   ` Eduardo Habkost [this message]
2017-09-05 17:32     ` Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 2/7] Convert remaining error_report() to warn_report() Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 3/7] Convert single line fprintf(.../n) " Alistair Francis
2017-09-01 20:52   ` James Hogan
2017-09-05 17:46     ` Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 4/7] Convert multi-line fprintf() " Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 5/7] General warn report fixups Alistair Francis
2017-09-08  9:17   ` Markus Armbruster
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 6/7] Makefile: Remove libqemustub.a Alistair Francis
2017-09-01 16:51 ` [Qemu-devel] [PATCH v3 7/7] Convert remaining single line fprintf() to warn_report() Alistair Francis
2017-09-08  9:22   ` Markus Armbruster
2017-09-08 16:38     ` Alistair Francis
2017-09-01 17:17 ` [Qemu-devel] [PATCH v3 0/7] More warning reporting fixed no-reply
2017-09-01 18:01   ` Alistair Francis

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=20170904141748.GU7570@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=alistair.francis@xilinx.com \
    --cc=alistair23@gmail.com \
    --cc=armbru@redhat.com \
    --cc=dslutz@verizon.com \
    --cc=pbonzini@redhat.com \
    --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 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).