qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: pbonzini@redhat.com, david@gibson.dropbear.id.au,
	qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/6] Refactoring pc_dimm_plug and NUMA node lookup API
Date: Mon, 29 Jun 2015 19:23:10 +0530	[thread overview]
Message-ID: <20150629135310.GK5569@in.ibm.com> (raw)
In-Reply-To: <20150629143209.0ad4de0d@nial.brq.redhat.com>

On Mon, Jun 29, 2015 at 02:32:09PM +0200, Igor Mammedov wrote:
> On Mon, 29 Jun 2015 13:50:21 +0530
> Bharata B Rao <bharata@linux.vnet.ibm.com> wrote:
> 
> > Hi,
> > 
> > Here is the v4 of the patchset that refactors pc_dimm_plug and adds
> > an API to lookup NUMA node by address.
> > 
> > - Refactoring pc_dimm_plug() helps other architectures like PowerPC
> >   to make use of common code.
> > - API to lookup NUMA node id by address is required to support memory
> >   hotplug on PowerPC sPAPR guests.
> > 
> > In addition to pc_dimm_plug() reorganization and NUMA node lookup
> > API, this patchset also carries a patch to abort when
> > HotplugHandlerClass::plug() fails for pc machine.
> > 
> > The patchset that adds memory hotplug support to PowerPC sPAPR which
> > was posted at
> > http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg06574.html
> > depends on this patchset.
> > 
> > Changes in v4:
> > -------------
> > - Ensure memory range information is stored in node_info[0] for
> >   non-NUMA configurations. (5/6)
> > - Ensure numa_get_node() API looks up the given address in node 0
> >   for non-NUMA configurations. (6/6)
> > 
> > In addition the following changes based on Igor's review:
> > 
> > - hhc->plug() shouldn't fail for PC arch, hence don't try to recover
> >   by calling pc_dimm_memory_unplug(). (2/6)
> > - Use pc_dimm_memory_unplug() from pc_dimm_unplug(). (2/6)
> > - Add a patch to use error_abort in hhc->plug(). (3/6)
> > - Store exact address range (start, end and not end+1) in numa_info
> >   and modify the lookup logic accordingly. (4/6, 6/6)
> > 
> > v3: http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg06768.html
> > v2: https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg05157.html
> > v1: https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg03212.html
> > v0: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg01078.html
> > 
> > Bharata B Rao (6):
> >   pc,pc-dimm: Extract hotplug related fields in PCMachineState to a
> >     structure
> >   pc,pc-dimm: Factor out reusable parts in pc_dimm_plug to a separate
> >     routine
> >   pc: Abort if HotplugHandlerClass::plug() fails
> >   numa,pc-dimm: Store pc-dimm memory information in numa_info
> >   numa: Store boot memory address range in node_info
> >   numa: API to lookup NUMA node by address
> > 
> >  hw/i386/acpi-build.c     |  2 +-
> >  hw/i386/pc.c             | 84 +++++++------------------------------------
> >  hw/mem/pc-dimm.c         | 84 +++++++++++++++++++++++++++++++++++++++++++
> >  include/hw/i386/pc.h     |  7 ++--
> >  include/hw/mem/pc-dimm.h | 15 ++++++++
> >  include/sysemu/numa.h    | 11 ++++++
> >  numa.c                   | 94 ++++++++++++++++++++++++++++++++++++++++++++++++
> >  7 files changed, 219 insertions(+), 78 deletions(-)
> > 
> 
> tested wrt PC memory hotplug, hence for series
> 
> Tested-by: Igor Mammedov <imammedo@redhat.com>

Thanks a lot.

I have tested this with out-of-the-tree PowerPC sPAPR memory hotplug
patchset for scenarios like hotplugging memory to non-NUMA guest,
single and multiple NUMA node guest and guest with memory-less nodes.

Regards,
Bharata.

  reply	other threads:[~2015-06-29 13:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29  8:20 [Qemu-devel] [PATCH v4 0/6] Refactoring pc_dimm_plug and NUMA node lookup API Bharata B Rao
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 1/6] pc, pc-dimm: Extract hotplug related fields in PCMachineState to a structure Bharata B Rao
2015-06-29  8:49   ` Igor Mammedov
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 2/6] pc, pc-dimm: Factor out reusable parts in pc_dimm_plug to a separate routine Bharata B Rao
2015-06-29 11:52   ` Igor Mammedov
2015-06-30  2:53   ` David Gibson
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 3/6] pc: Abort if HotplugHandlerClass::plug() fails Bharata B Rao
2015-06-29 11:53   ` Igor Mammedov
2015-06-30  2:54   ` David Gibson
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 4/6] numa, pc-dimm: Store pc-dimm memory information in numa_info Bharata B Rao
2015-06-29 12:08   ` Igor Mammedov
2015-06-29 13:41     ` Bharata B Rao
2015-06-29 14:53       ` Igor Mammedov
2015-07-02  4:07         ` Bharata B Rao
2015-06-30  2:55   ` David Gibson
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 5/6] numa: Store boot memory address range in node_info Bharata B Rao
2015-06-30  2:56   ` David Gibson
2015-06-29  8:20 ` [Qemu-devel] [PATCH v4 6/6] numa: API to lookup NUMA node by address Bharata B Rao
2015-06-30  2:57   ` David Gibson
2015-06-29 12:32 ` [Qemu-devel] [PATCH v4 0/6] Refactoring pc_dimm_plug and NUMA node lookup API Igor Mammedov
2015-06-29 13:53   ` Bharata B Rao [this message]
2015-06-30 19:39 ` Eduardo Habkost

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=20150629135310.GK5569@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).