qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Leonardo Bras <leonardo@linux.ibm.com>
To: Bharata B Rao <bharata.rao@gmail.com>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: Bharata B Rao <bharata.rao@in.ibm.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 1/1] ppc/spapr: Add hotplugged flag on DIMM LMBs on drmem_v2
Date: Thu, 02 Apr 2020 14:11:12 -0300	[thread overview]
Message-ID: <e9caef7692520a63aad60d418a20f2d7cf58fcdc.camel@linux.ibm.com> (raw)
In-Reply-To: <CAGZKiBpO4HxrE06dT39sj95_qcTvQK_g5Ev5TKC5T9wimphM_Q@mail.gmail.com>

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

Hello Bharata, thank you for reviewing and testing!

During review of this new flag, it was suggested to change it's name to
a better one (on platform's viewpoint). 

So I will have to change the flag name from SPAPR_LMB_FLAGS_HOTPLUGGED
to SPAPR_LMB_FLAGS_HOTREMOVABLE.

Everything should work the same as today.

Best regards,
Leonardo



On Thu, 2020-04-02 at 14:46 +0530, Bharata B Rao wrote:
> On Tue, Mar 10, 2020 at 8:24 AM David Gibson
> <david@gibson.dropbear.id.au> wrote:
> > On Thu, Mar 05, 2020 at 09:22:02PM -0300, Leonardo Bras wrote:
> > > On reboot, all memory that was previously added using object_add and
> > > device_add is placed in this DIMM area.
> > > 
> > > The new SPAPR_LMB_FLAGS_HOTPLUGGED flag helps Linux to put this memory in
> > > the correct memory zone, so no unmovable allocations are made there,
> > > allowing the object to be easily hot-removed by device_del and
> > > object_del.
> > > 
> > > Signed-off-by: Leonardo Bras <leonardo@linux.ibm.com>
> > > 
> > > ---
> > > The new flag was already proposed on Power Architecture documentation,
> > > and it's waiting for approval.
> > > 
> > > I would like to get your comments on this change, but it's still not
> > > ready for being merged.
> > 
> > This looks reasonable to me - at the very least it doesn't look like
> > it could do much harm.
> 
> Looks good to me, also tested with PowerKVM guests.
> 
> Reviewed-by: Bharata B Rao <bharata@linux.ibm.com>
> 
> Regards,
> Bharata.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-04-02 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  0:22 [RFC PATCH 1/1] ppc/spapr: Add hotplugged flag on DIMM LMBs on drmem_v2 Leonardo Bras
2020-03-10  2:39 ` David Gibson
2020-04-02  9:16   ` Bharata B Rao
2020-04-02 17:11     ` Leonardo Bras [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=e9caef7692520a63aad60d418a20f2d7cf58fcdc.camel@linux.ibm.com \
    --to=leonardo@linux.ibm.com \
    --cc=bharata.rao@gmail.com \
    --cc=bharata.rao@in.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --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).