From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Greg Kurz <groug@kaod.org>,
clg@kaod.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Correct RAM size calculation for HPT resizing
Date: Wed, 11 Oct 2017 11:04:53 +1100 [thread overview]
Message-ID: <20171011000453.GC10496@umbus.fritz.box> (raw)
In-Reply-To: <955ac977-e20b-4c55-bbaa-a51c41f2bed3@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
On Tue, Oct 10, 2017 at 05:21:53PM +0200, Laurent Vivier wrote:
> On 10/10/2017 16:44, Greg Kurz wrote:
> > On Wed, 11 Oct 2017 00:21:59 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> >> In order to prevent the guest from forcing the allocation of large amounts
> >> of qemu memory (or host kernel memory, in the case of KVM HV), we limit
> >> the size of Hashed Page Table (HPT) it is allowed to allocated, based on
> >> its RAM size.
> >>
> >> However, the current calculation is not correct: it only adds up the size
> >> of plugged memory, ignoring the base memory size. This patch corrects it.
> >>
> >> While we're there, use get_plugged_memory_size() instead of directly
> >> calling pc_existing_dimms_capacity(). The only difference is that it
> >> will abort on failure, which is right: a failure here indicates something
> >> wrong within qemu.
> >>
> >> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> >> ---
> >> hw/ppc/spapr_hcall.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> >> index 8d72bb7c1c..06af1b15c0 100644
> >> --- a/hw/ppc/spapr_hcall.c
> >> +++ b/hw/ppc/spapr_hcall.c
> >> @@ -494,7 +494,7 @@ static target_ulong h_resize_hpt_prepare(PowerPCCPU *cpu,
> >> return H_PARAMETER;
> >> }
> >>
> >> - current_ram_size = pc_existing_dimms_capacity(&error_fatal);
> >> + current_ram_size = ram_size + get_plugged_memory_size();
> >
> > current_ram_size is initialized earlier in this function:
> >
> > uint64_t current_ram_size = MACHINE(spapr)->ram_size;
> >
> > which is is initialized to ram_size in vl.c. Why not doing:
> >
> > current_ram_size += get_plugged_memory_size();
> >
> > ?
>
> I agree, it seems like the original intend of the first patch...
Yes, I think so. However, splitting the calculation like that
demonstrably misread someone reading the code (i.e. me), so I'm going
to just ditch the initializerin the new spin.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-11 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 13:21 [Qemu-devel] [PATCH] spapr: Correct RAM size calculation for HPT resizing David Gibson
2017-10-10 13:59 ` Laurent Vivier
2017-10-10 14:44 ` Greg Kurz
2017-10-10 15:21 ` Laurent Vivier
2017-10-11 0:04 ` David Gibson [this message]
2017-10-10 15:10 ` [Qemu-devel] [Qemu-ppc] " Andrea Bolognani
2017-10-10 23:20 ` David Gibson
2017-10-10 15:16 ` [Qemu-devel] " 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=20171011000453.GC10496@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).