From: Thomas Huth <thuth@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC v0 1/2] spapr: Accommadate alignment gaps in hotplug memory region
Date: Mon, 5 Oct 2015 17:24:56 +0200 [thread overview]
Message-ID: <56129648.7090701@redhat.com> (raw)
In-Reply-To: <1444034124-28747-2-git-send-email-bharata@linux.vnet.ibm.com>
On 05/10/15 10:35, Bharata B Rao wrote:
> Size hotplug memory region assuming a 256MB max alignment every slot.
>
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> ---
> hw/ppc/spapr.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index fc5e7d6..2ec509b 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -1792,6 +1792,9 @@ static void ppc_spapr_init(MachineState *machine)
>
> spapr->hotplug_memory.base = ROUND_UP(machine->ram_size,
> SPAPR_HOTPLUG_MEM_ALIGN);
> +
> + /* size hotplug region assuming 256M max alignment per slot */
> + hotplug_mem_size += SPAPR_MEMORY_BLOCK_SIZE * machine->ram_slots;
Could you maybe make the comment here a little bit more verbose? Without
reading the cover letter first, I would not understand this piece of
code ... and I'm afraid that when we look at this code in a couple of
years again, we hit the same problem when the comment is that short.
Thanks,
Thomas
next prev parent reply other threads:[~2015-10-05 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:35 [Qemu-devel] [RFC v0 0/2] Enforce gaps between DIMMs Bharata B Rao
2015-10-05 8:35 ` [Qemu-devel] [RFC v0 1/2] spapr: Accommadate alignment gaps in hotplug memory region Bharata B Rao
2015-10-05 9:05 ` Igor Mammedov
2015-10-06 3:29 ` David Gibson
2015-10-06 8:02 ` Igor Mammedov
2015-10-05 15:24 ` Thomas Huth [this message]
2015-10-05 8:35 ` [Qemu-devel] [RFC v0 2/2] spapr: Force gaps between DIMM's GPA Bharata B Rao
2015-10-05 20:24 ` [Qemu-devel] [RFC v0 0/2] Enforce gaps between DIMMs Michael S. Tsirkin
2015-10-06 8:08 ` Igor Mammedov
2015-10-06 9:33 ` Bharata B Rao
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=56129648.7090701@redhat.com \
--to=thuth@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@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).