qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 0/6] spapr: rework memory nodes
Date: Mon, 21 Jul 2014 13:15:18 +1000	[thread overview]
Message-ID: <53CC85C6.4070501@ozlabs.ru> (raw)
In-Reply-To: <1404357007-29507-1-git-send-email-aik@ozlabs.ru>

On 07/03/2014 01:10 PM, Alexey Kardashevskiy wrote:
> c4177479 "spapr: make sure RMA is in first mode of first memory node"
> introduced regression which prevents from running guests with memoryless
> NUMA node#0 which may happen on real POWER8 boxes and which would make
> sense to debug in QEMU.
> 
> This patchset aim is to fix that and also fix various code problems in
> memory nodes generation.
> 
> These 2 patches could be merged (the resulting patch looks rather ugly):
> spapr: Use DT memory node rendering helper for other nodes
> spapr: Move DT memory node rendering to a helper
> 
> 
> Alex, there are "numa: enable sparse node numbering ..." patches from Nish,
> which set can go first so the other could rebase on top of it? Thanks!


Ping. This is for 2.2 indeed.


> 
> 
> 
> Changes:
> v3:
> * fixed bug with ram_size bigger than the only NUMA node
> * fixed bug with 64bit addresses in memory node creation loop
> 
> v2:
> * minor cosmetic change in spapr_node0_size()
> * spapr_populate_memory() fixed to work in a no-numa config
> * patch changing max numa nodes is removed
> 
> Please comment. Thanks!
> 
> 
> 
> 
> Alexey Kardashevskiy (6):
>   spapr: Move DT memory node rendering to a helper
>   spapr: Use DT memory node rendering helper for other nodes
>   spapr: Refactor spapr_populate_memory() to allow memoryless nodes
>   spapr: Split memory nodes to power-of-two blocks
>   spapr: Add a helper for node0_size calculation
>   spapr: Fix ibm,associativity for memory nodes
> 
>  hw/ppc/spapr.c | 111 ++++++++++++++++++++++++++++++++-------------------------
>  1 file changed, 63 insertions(+), 48 deletions(-)
> 


-- 
Alexey

  parent reply	other threads:[~2014-07-21  3:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  3:10 [Qemu-devel] [PATCH v3 0/6] spapr: rework memory nodes Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 1/6] spapr: Move DT memory node rendering to a helper Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 2/6] spapr: Use DT memory node rendering helper for other nodes Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 3/6] spapr: Refactor spapr_populate_memory() to allow memoryless nodes Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 4/6] spapr: Split memory nodes to power-of-two blocks Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 5/6] spapr: Add a helper for node0_size calculation Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 6/6] spapr: Fix ibm, associativity for memory nodes Alexey Kardashevskiy
2014-07-21  3:15 ` Alexey Kardashevskiy [this message]
2014-07-28 11:02   ` [Qemu-devel] [PATCH v3 0/6] spapr: rework " Alexander Graf

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=53CC85C6.4070501@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=nacc@linux.vnet.ibm.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).