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]
Message-ID: <1269028326.8741.9.camel@c-dwalke-linux.qualcomm.com>
Date:	Fri, 19 Mar 2010 12:52:06 -0700
From:	Daniel Walker <dwalker@...eaurora.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	mgross@...ux.intel.com, Pavel Machek <pavel@....cz>,
	640E9920 <640e9920@...il.com>,
	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	tiwai@...e.de, bruce.w.allan@...el.com, aili@...eaurora.org,
	khilman@...prootsystems.com
Subject: Re: [PATCH] PM_QOS updates for 2.6.34-rc1

On Fri, 2010-03-19 at 20:49 +0100, Rafael J. Wysocki wrote:
> On Friday 19 March 2010, mark gross wrote:
> > On Sun, Mar 14, 2010 at 07:26:37AM +0100, Pavel Machek wrote:
> > > On Sat 2010-03-13 16:34:25, 640E9920 wrote:
> > > > The following patch series implements to following:
> > > > 1) pm_qos now uses a handle based implementation.  No more string
> > > > compares while walking lists.
> > > > 2) renames the exports to using more accurate names.
> > > > 3) updates kernel clients of pm_qos per this change
> > > > 4) added ascii interface to pmqos recognizing strings formatted in 10
> > > > charactor format "0x12345678"
> > > > 5) added new pm_qos class, "system_bus_throughput"
> > > > 
> > > > I would like to see this series make it into 2.6.34 if its not too late. 
> > > 
> > > I believe it is... -rc1 is past us.
> > 
> > crap.  I'll guess I'll redo them for next then.
> > 
> > 
> >  
> > > Also... the way the patches are structured... that will break bisect,
> > > no?
> > 
> > Um not sure, how would you recomend I structure them?
> 
> Generally speaking, the kernel should build and should work correctly after
> applying each consecutive patch in the series.

I think you would need to have the handle based method along side the
old method until all the kernel clients are converted.. Then remove the
old method ..

Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ