linux-kernel - Re: [PATCH v2 14/14] Change CPUACCT to default n

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]

Message-ID: <4ECEF7DD.6010403@cn.fujitsu.com>
Date:	Fri, 25 Nov 2011 10:05:17 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Paul Turner <pjt@...gle.com>
CC:	Glauber Costa <glommer@...allels.com>,
	linux-kernel@...r.kernel.org, paul@...lmenage.org,
	daniel.lezcano@...e.fr, a.p.zijlstra@...llo.nl,
	jbottomley@...allels.com, fweisbec@...il.com,
	Balbir Singh <bsingharora@...il.com>
Subject: Re: [PATCH v2 14/14] Change CPUACCT to default n

> despite it being a not entirely natural fit.  Something I proposed at
> Prague and that we could explore here is the idea of a co-mounted
> controller.  In this example it would only be mountable with cpu so
> you could always depend on the cpu hierarchy being there; likewise we
> can put (jump-labeled) touchpoints within the cpu-subsystem to call
> out for updates as appropriate when the co-mount exists.
> 

IIUC, this co-mounting idea is something I implemented years ago:

https://lkml.org/lkml/2008/6/18/389

The use case and the reason it was rejected:

https://lkml.org/lkml/2008/7/1/97

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