Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1361837

Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps in a macro

From Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>
Newsgroups linux.kernel
Subject Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps in a macro
Date 2016-03-21 14:30 +0100
Message-ID <rf84c-6fl-55@gated-at.bofh.it> (permalink)
References <r7v7z-2Wa-9@gated-at.bofh.it> <r7v7B-2Wa-23@gated-at.bofh.it> <rdNEv-4pc-23@gated-at.bofh.it> <re42C-7Nh-5@gated-at.bofh.it> <recWe-4XN-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 03/19/2016 05:51 AM, Paul Mackerras wrote:
> On Fri, Mar 18, 2016 at 08:23:24PM +0530, Shreyas B Prabhu wrote:
>> Hi Paul,
>>
>> On 03/17/2016 04:45 PM, Paul Mackerras wrote:
>>> On Mon, Feb 29, 2016 at 05:52:59PM +0530, Shreyas B. Prabhu wrote:
>>>> Before entering any idle state which can result in a state loss
>>>> we currently save the context in the stack before entering idle.
>>>> Encapsulate these steps in a macro IDLE_STATE_PREP. Move this
>>>> and other macros to commonly accessible location.
>>>
>>> There are two problems with this.  First, your new macro does much
>>> more than create a stack frame and save some registers.  It also
>>> messes with interrupts and potentially executes a blr instruction.
>>> That is not what people would expect from the name of the macro or the
>>> comments around it.  It also means that it would be hard to reuse the
>>> macro in another place.
>>>
>>> Secondly, I don't think this change helps readability.  Since the
>>> macro is only used in one place, it doesn't reduce the total number of
>>> lines of code, in fact it increases it slightly. 
>>
>> This patch was in preparation for support for new POWER ISA v3 idle
>> states. The idea was to have the common idle preparation steps in a
>> macro which be reused while adding support for the new idle states. With
>> this context do you think this macro with better comments make sense?
> 
> No, it still does too many disparate things.  In particular it's a bad
> idea to embed a blr inside a macro unless the name makes it very clear
> that the macro can cause a return (e.g. the macro name is
> RETURN_IF_<something>).  Yours would need to be called
> MAKE_STACK_FRAME_AND_SAVE_SPRS_AND_HARD_DISABLE_AND_RETURN_IF_IRQ_OCCURRED
> or something. :)
> 

Ok :) . I'll drop this patch and work this differently.

Thanks,
Shreyas

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps  in a macro Paul Mackerras <paulus@ozlabs.org> - 2016-03-17 22:30 +0100
  Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps  in a macro Shreyas B Prabhu <shreyas@linux.vnet.ibm.com> - 2016-03-18 16:00 +0100
    Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps  in a macro Paul Mackerras <paulus@ozlabs.org> - 2016-03-19 01:30 +0100
      Re: [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps  in a macro Shreyas B Prabhu <shreyas@linux.vnet.ibm.com> - 2016-03-21 14:30 +0100

csiph-web