From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: lvivier@redhat.com, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
groug@kaod.org, clg@kaod.org
Subject: Re: [for-5.0 4/4] spapr: Correct clamping of RMA to Node 0 size
Date: Tue, 10 Dec 2019 16:21:38 +1100 [thread overview]
Message-ID: <20191210052138.GI207300@umbus.fritz.box> (raw)
In-Reply-To: <6bdb09b2-2d08-f997-30a2-5ec417c8b914@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Tue, Dec 03, 2019 at 03:18:37PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 29/11/2019 12:35, David Gibson wrote:
> > The Real Mode Area (RMA) needs to fit within Node 0 in NUMA configurations.
> > We use a helper function spapr_node0_size() to calculate this.
> >
> > But that function doesn't actually get the size of Node 0, it gets the
> > minimum size of all nodes, ever since b082d65a300 "spapr: Add a helper for
> > node0_size calculation". That was added, apparently, because Node 0 in
> > qemu's terms might not have corresponded to Node 0 in PAPR terms (i.e. the
> > node with memory at address 0).
>
>
> After looking at this closely, I think the idea was that the first
> node(s) may have only CPUs but not memory, in this case
> node#0.node_mem==0 and things crash:
Ah! Excellent point - I misread what the existing node0_size()
function was doing. Corrected for the next 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 --]
prev parent reply other threads:[~2019-12-10 5:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 1:35 [for-5.0 0/4] Fixes for RMA size calculation David Gibson
2019-11-29 1:35 ` [for-5.0 1/4] spapr,ppc: Simplify signature of kvmppc_rma_size() David Gibson
2019-12-02 7:45 ` Cédric Le Goater
2019-12-02 8:55 ` Greg Kurz
2019-12-02 18:18 ` Cédric Le Goater
2019-12-10 3:58 ` David Gibson
2019-12-03 3:32 ` Alexey Kardashevskiy
2019-11-29 1:35 ` [for-5.0 2/4] spapr: Don't attempt to clamp RMA to VRMA constraint David Gibson
2019-12-03 3:33 ` Alexey Kardashevskiy
2019-11-29 1:35 ` [for-5.0 3/4] spapr: Clean up RMA size calculation David Gibson
2019-12-03 3:44 ` Alexey Kardashevskiy
2019-12-03 5:06 ` Alexey Kardashevskiy
2019-12-10 5:44 ` David Gibson
2019-12-10 5:29 ` David Gibson
2019-11-29 1:35 ` [for-5.0 4/4] spapr: Correct clamping of RMA to Node 0 size David Gibson
2019-12-03 4:18 ` Alexey Kardashevskiy
2019-12-10 5:21 ` David Gibson [this message]
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=20191210052138.GI207300@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--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).