From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, imammedo@redhat.com, ehabkost@redhat.com,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v2 0/4] Refactoring pc_dimm_plug and NUMA node lookup API
Date: Wed, 24 Jun 2015 09:04:46 +0530 [thread overview]
Message-ID: <20150624033446.GF26051@in.ibm.com> (raw)
In-Reply-To: <1434690624-8628-1-git-send-email-bharata@linux.vnet.ibm.com>
On Fri, Jun 19, 2015 at 10:40:20AM +0530, Bharata B Rao wrote:
> Hi,
>
> Here is the v2 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.
Igor,
I have tested basic x86 memory hotplug with this pc_dimm_plug reorganization.
Does this reorganization look correct to you ?
Is there a chance for this patchset to make it to 2.4 ?
Regards,
Bharata.
next prev parent reply other threads:[~2015-06-24 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 5:10 [Qemu-devel] [PATCH v2 0/4] Refactoring pc_dimm_plug and NUMA node lookup API Bharata B Rao
2015-06-19 5:10 ` [Qemu-devel] [PATCH v2 1/4] pc, pc-dimm: Factor out reusable parts in pc_dimm_plug to a separate routine Bharata B Rao
2015-06-24 11:11 ` Bharata B Rao
2015-06-25 13:27 ` Igor Mammedov
2015-06-19 5:10 ` [Qemu-devel] [PATCH v2 2/4] numa, pc-dimm: Store pc-dimm memory information in numa_info Bharata B Rao
2015-06-19 5:10 ` [Qemu-devel] [PATCH v2 3/4] numa: Store boot memory address range in node_info Bharata B Rao
2015-06-22 2:55 ` David Gibson
2015-06-19 5:10 ` [Qemu-devel] [PATCH v2 4/4] numa: API to lookup NUMA node by address Bharata B Rao
2015-06-24 3:34 ` Bharata B Rao [this message]
2015-06-25 11:52 ` [Qemu-devel] [PATCH v2 0/4] Refactoring pc_dimm_plug and NUMA node lookup API Igor Mammedov
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=20150624033446.GF26051@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).