lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 15 Jul 2016 15:38:40 +0800
From:	Jisheng Zhang <jszhang@...vell.com>
To:	Russell King - ARM Linux <linux@...linux.org.uk>
CC:	<arm@...nel.org>, Daniel Lezcano <daniel.lezcano@...aro.org>,
	"Arnd Bergmann" <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	<lorenzo.pieralisi@....com>, <lina.iyer@...aro.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 2/2] ARM: cpuidle: make arm_cpuidle_suspend() a bit
 more efficient

On Thu, 14 Jul 2016 16:31:13 +0100 Russell King - ARM Linux wrote:

> On Fri, Jul 08, 2016 at 06:58:54PM +0800, Jisheng Zhang wrote:
> > On Fri, 8 Jul 2016 12:50:12 +0200 Daniel Lezcano  wrote:
> >   
> > > On Fri, Jul 08, 2016 at 02:17:29PM +0800, Jisheng Zhang wrote:  
> > > > Dear Daniel,
> > > > 
> > > > On Thu, 7 Jul 2016 15:46:28 +0200 Daniel Lezcano wrote:
> > > >     
> > > > > On Wed, Jul 06, 2016 at 02:15:55PM +0800, Jisheng Zhang wrote:    
> > > > > > Currently, we check cpuidle_ops.suspend every time when entering a
> > > > > > low-power idle state. But this check could be avoided in this hot path
> > > > > > by moving it into arm_cpuidle_read_ops() to reduce arm_cpuidle_suspend
> > > > > > overhead a bit.
> > > > > > 
> > > > > > Signed-off-by: Jisheng Zhang <jszhang@...vell.com>
> > > > > > ---      
> > > > > 
> > > > > Acked-by: Daniel Lezcano <daniel.lezcano@...aro.org>    
> > > > 
> > > > I'm not sure the upstream merging path this patch should follow, Per my
> > > > understanding, I need to put it into Russell's PATCH system.    
> > > 
> > > Or alternatively through arm-soc
> > >   
> > 
> > Got it. thanks.
> > 
> > Dear Arnd, Olof,
> > 
> > I have no pull request permission. what's your preference? Could you please
> > advise?  
> 
> ... and because arm-soc people haven't responded, they've now ended up
> in the patch system... So I've applied them to my tree in a separate
> branch.
> 

Thank you so much!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ