From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Sergio Lopez <slp@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
imammedo@redhat.com, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2 2/4] microvm: drop max-ram-below-4g support
Date: Thu, 28 May 2020 15:42:23 +0200 [thread overview]
Message-ID: <16e2f252-741e-59ec-9e02-aaf5363bc9f3@redhat.com> (raw)
In-Reply-To: <20200528134035.32025-3-kraxel@redhat.com>
On 5/28/20 3:40 PM, Gerd Hoffmann wrote:
> Not useful for microvm and allows users to shoot themself
> into the foot (make ram + mmio overlap).
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/i386/microvm.c | 19 -------------------
> 1 file changed, 19 deletions(-)
>
> diff --git a/hw/i386/microvm.c b/hw/i386/microvm.c
> index 44f940813b07..5e931975a06d 100644
> --- a/hw/i386/microvm.c
> +++ b/hw/i386/microvm.c
> @@ -173,25 +173,6 @@ static void microvm_memory_init(MicrovmMachineState *mms)
> ram_addr_t lowmem = 0xc0000000; /* 3G */
> int i;
>
> - /*
> - * Handle the machine opt max-ram-below-4g. It is basically doing
> - * min(qemu limit, user limit).
> - */
> - if (!x86ms->max_ram_below_4g) {
> - x86ms->max_ram_below_4g = 4 * GiB;
> - }
> - if (lowmem > x86ms->max_ram_below_4g) {
> - lowmem = x86ms->max_ram_below_4g;
> - if (machine->ram_size - lowmem > lowmem &&
> - lowmem & (1 * GiB - 1)) {
> - warn_report("There is possibly poor performance as the ram size "
> - " (0x%" PRIx64 ") is more then twice the size of"
> - " max-ram-below-4g (%"PRIu64") and"
> - " max-ram-below-4g is not a multiple of 1G.",
> - (uint64_t)machine->ram_size, x86ms->max_ram_below_4g);
> - }
> - }
> -
> if (machine->ram_size > lowmem) {
> x86ms->above_4g_mem_size = machine->ram_size - lowmem;
> x86ms->below_4g_mem_size = lowmem;
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-05-28 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 13:40 [PATCH v2 0/4] microvm: memory config tweaks Gerd Hoffmann
2020-05-28 13:40 ` [PATCH v2 1/4] microvm: use 3G split unconditionally Gerd Hoffmann
2020-05-28 13:40 ` [PATCH v2 2/4] microvm: drop max-ram-below-4g support Gerd Hoffmann
2020-05-28 13:42 ` Philippe Mathieu-Daudé [this message]
2020-05-28 13:40 ` [PATCH v2 3/4] x86: move max-ram-below-4g to pc Gerd Hoffmann
2020-05-28 13:40 ` [PATCH v2 4/4] microvm: move virtio base to 0xfeb00000 Gerd Hoffmann
2020-05-28 20:58 ` [PATCH v2 0/4] microvm: memory config tweaks no-reply
2020-05-29 7:03 ` Igor Mammedov
2020-05-28 21:04 ` no-reply
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=16e2f252-741e-59ec-9e02-aaf5363bc9f3@redhat.com \
--to=philmd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=slp@redhat.com \
/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).