linux-kernel - Re: [patch 2/2] sched: allow cpuacct stats to be reset

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Feb 2008 11:38:54 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Paul Menage <menage@...gle.com>
Cc:	Dhaval Giani <dhaval@...ux.vnet.ibm.com>, vatsa@...ux.vnet.ibm.com,
	balbir@...ux.vnet.ibm.com, mingo@...e.hu,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	skumar@...ux.vnet.ibm.com
Subject: Re: [patch 2/2] sched: allow cpuacct stats to be reset


On Fri, 2008-02-29 at 02:08 -0800, Paul Menage wrote:
> On Thu, Feb 28, 2008 at 10:04 PM, Dhaval Giani
> <dhaval@...ux.vnet.ibm.com> wrote:
> > On Thu, Feb 28, 2008 at 09:48:51PM -0800, Paul Menage wrote:
> >
> > > On Thu, Feb 28, 2008 at 8:32 PM, Dhaval Giani <dhaval@...ux.vnet.ibm.com> wrote:
> >  >
> >
> > > Can I suggest, in order to be more generic, that this patch instead
> >  > set each CPU's counter to the written value divided by the number of
> >  > CPUs? (Either forgetting the remainder, or spreading it among the
> >  > first few CPUs).
> >  >
> >
> >  This patch is only allowing a reset of the stats. In what sort of a
> >  situation would one be looking for changing the usage value?
> 
> How about Checkpoint/Restart?

Shouldn't that be a kernel side thing? And from the kernel you can put
back any value you fancy.

--
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/