All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: mdroth@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v0 0/5] spapr-next: Memory hotplug updates
Date: Wed, 12 Aug 2015 11:32:38 +1000	[thread overview]
Message-ID: <20150812013238.GE19634@voom.fritz.box> (raw)
In-Reply-To: <1438580143-587-1-git-send-email-bharata@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

On Mon, Aug 03, 2015 at 11:05:38AM +0530, Bharata B Rao wrote:
> This patchset includes some updates to sPAPR memory hotplug code that
> currently resides in spapr-next branch of David Gibson's tree.
> 
> The main change here is to use drc-count hotplug identifier type for memory
> hotplug. Currently we use drc-index type of hotplug identifier for
> memory, which means that we send one EPOW event to guest on hotplug
> of each LMB. Guest kernel has limited buffer space to hold these events
> and we can easily overflow this buffer leading to missing of memory
> hotplug events. After we switch to drc-count type of hotplug identifier,
> we will send only one event to guest on hotplugging each pc-dimm device
> thereby reducing the chances of guest rtas buffer overflow. This change
> allows us to hotplug huge amounts of memory (>16G) in one pc-dimm
> hotplug request.
> 
> Another change here is to not include information about memory specified
> using -m option in ibm,drc-names, ibm,drc-indexes and
> ibm,dynamic-memory-reconfiguration nodes thus having only truly DR capable
> memory in these DT nodes/properties.
> 
> Bharata B Rao (5):
>   spapr: Provide better error message when slots exceed max allowed
>   spapr: Populate ibm,associativity-lookup-arrays correctly for non-NUMA
>   spapr: Revert to memory@XXXX representation for non-hotplugged memory
>   spapr: Support hotplug by specifying DRC count
>   spapr: Move memory hotplug to RTAS_LOG_V6_HP_ID_DRC_COUNT type
> 
>  hw/ppc/spapr.c         | 58 +++++++++++++-------------------------------------
>  hw/ppc/spapr_events.c  | 47 ++++++++++++++++++++++++++++++++--------
>  hw/ppc/spapr_pci.c     |  4 ++--
>  include/hw/ppc/spapr.h |  8 +++++--
>  4 files changed, 61 insertions(+), 56 deletions(-)

I've merged patches 1..3/5 into spapr-next.  4 & 5 I need to think
about a bit more.

-- 
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: Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-08-12  2:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03  5:35 [Qemu-devel] [RFC PATCH v0 0/5] spapr-next: Memory hotplug updates Bharata B Rao
2015-08-03  5:35 ` [Qemu-devel] [RFC PATCH v0 1/5] spapr: Provide better error message when slots exceed max allowed Bharata B Rao
2015-08-03  6:43   ` David Gibson
2015-08-03  5:35 ` [Qemu-devel] [RFC PATCH v0 2/5] spapr: Populate ibm, associativity-lookup-arrays correctly for non-NUMA Bharata B Rao
2015-08-03  5:35 ` [Qemu-devel] [RFC PATCH v0 3/5] spapr: Revert to memory@XXXX representation for non-hotplugged memory Bharata B Rao
2015-08-04 14:33   ` Nathan Fontenot
2015-08-05  3:42     ` Bharata B Rao
2015-08-03  5:35 ` [Qemu-devel] [RFC PATCH v0 4/5] spapr: Support hotplug by specifying DRC count Bharata B Rao
2015-08-03  6:55   ` David Gibson
2015-08-03  7:53     ` Bharata B Rao
2015-08-03 22:32       ` Michael Roth
2015-08-04  4:36         ` David Gibson
2015-08-03  5:35 ` [Qemu-devel] [RFC PATCH v0 5/5] spapr: Move memory hotplug to RTAS_LOG_V6_HP_ID_DRC_COUNT type Bharata B Rao
2015-08-12  1:32 ` 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=20150812013238.GE19634@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=nfont@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.