linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [3/3] powerpc/pseries: Cleanup property cloning in memory dlpar
Date: Thu, 3 Mar 2016 21:45:41 -0600	[thread overview]
Message-ID: <56D904E5.1030904@linux.vnet.ibm.com> (raw)
In-Reply-To: <1456883226.24490.4.camel@ellerman.id.au>

On 03/01/2016 07:47 PM, Michael Ellerman wrote:
> On Wed, 2016-03-02 at 10:02 +1100, Michael Ellerman wrote:
>> On Wed, 2016-10-02 at 17:13:29 UTC, Nathan Fontenot wrote:
>>> Now that the DLPAR add/remove flow updates the ibm,dynamic-memory device
>>> tree property each time we add or remove a LMB the work needed to clone
>>> this property can be reduced.
>>>
>>> Prior to performing any memory DLPAR operation we now clone the device
>>> tree property once and convert it to cpu format. This copy is then used
>>> to walk through LMBs as we process them and is thrown away when we
>>> are finished. There is no longer a need to convert the entire property to
>>> cpu format and then back to BE every time we update it, we can just parse
>>> it in its native BE format and update the one LMB we need to modify
>>> before updating the property.
>>>
>>> This patch removes the BE => cpu conversion step in the clone routine and
>>> creates a drconf_property_to_cpu() routine to make this conversion for the
>>> one time we need to convert the entire property. This then allows us
>>> to remove dlpar_update_drconf_property() since we can now do everything
>>> in dlpar_update_device_tree_lmb().
>>
>> Hi Nathan,
>>
>> This sounds like a good cleanup on the face of it.
>>
>> But even with it applied I still see a boat load of endian errors from sparse
>> in this file. That worries me, can you please try and fix them.
> 
> I can merge patches 1 and 2 if you like, and leave this one for you to fixup?
> Or I can just wait for a v2 of the whole series. Let me know which you'd
> prefer.
> 

If you don't mind merging patches 1 and 2 I will send out a new cleanup patch
to fix the issues with patch 3 of the series.

Thanks,
-Nathan

      reply	other threads:[~2016-03-04  3:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 17:08 [PATCH 0/3] powerpc/pseries: Update affinity index during memory dlpar Nathan Fontenot
2016-02-10 17:10 ` [PATCH 1/3] powerpc/pseries: Refactor dlpar_add_lmb() code Nathan Fontenot
2016-04-11 12:35   ` [1/3] " Michael Ellerman
2016-02-10 17:12 ` [PATCH 2/3] powerpc/pseries: Update LMB associativity index during DLPAR add/remove Nathan Fontenot
2016-04-11 12:35   ` [2/3] " Michael Ellerman
2016-02-10 17:13 ` [PATCH 3/3] powerpc/pseries: Cleanup property cloning in memory dlpar Nathan Fontenot
2016-03-01 23:02   ` [3/3] " Michael Ellerman
2016-03-02  1:47     ` Michael Ellerman
2016-03-04  3:45       ` Nathan Fontenot [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=56D904E5.1030904@linux.vnet.ibm.com \
    --to=nfont@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).