From: Igor Mammedov <imammedo@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Sergio Lopez <slp@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
philmd@redhat.com, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 2/3] microvm: drop max-ram-below-4g support
Date: Mon, 25 May 2020 18:44:18 +0200 [thread overview]
Message-ID: <20200525184418.1c91e340@redhat.com> (raw)
In-Reply-To: <20200525134101.24740-3-kraxel@redhat.com>
On Mon, 25 May 2020 15:41:00 +0200
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Not useful for microvm and allows users to shot themself
s/shot/shoot/
> into the foot (make ram + mmio overlap).
also see my toher reply to previous version, parhaps we can drop some more logic here
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@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 44c08f8a5ab0..4b6ec2bbe331 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 = 0x80000000; /* 2G */
> 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;
next prev parent reply other threads:[~2020-05-25 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 13:40 [PATCH 0/3] microvm: memory config tweaks Gerd Hoffmann
2020-05-25 13:40 ` [PATCH 1/3] microvm: use 2G split unconditionally Gerd Hoffmann
2020-05-25 13:41 ` [PATCH 2/3] microvm: drop max-ram-below-4g support Gerd Hoffmann
2020-05-25 16:44 ` Igor Mammedov [this message]
2020-05-25 13:41 ` [PATCH 3/3] x86: move max-ram-below-4g to pc Gerd Hoffmann
2020-05-25 13:46 ` Philippe Mathieu-Daudé
2020-05-25 13:56 ` [PATCH 0/3] microvm: memory config tweaks Paolo Bonzini
2020-05-26 1:47 ` no-reply
2020-05-26 1:52 ` 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=20200525184418.1c91e340@redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).