linux-kernel - Re: [PATCH 1/9] coresight: change coresight_device lock type to raw_spinlock

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:
 <GV1PR08MB105213222FB18FF328443148BFB362@GV1PR08MB10521.eurprd08.prod.outlook.com>
Date: Tue, 3 Dec 2024 15:30:43 +0000
From: Yeo Reum Yun <YeoReum.Yun@....com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: Suzuki Poulose <Suzuki.Poulose@....com>, "mike.leach@...aro.org"
	<mike.leach@...aro.org>, "james.clark@...aro.org" <james.clark@...aro.org>,
	"alexander.shishkin@...ux.intel.com" <alexander.shishkin@...ux.intel.com>,
	"bigeasy@...utronix.de" <bigeasy@...utronix.de>, "clrkwllms@...nel.org"
	<clrkwllms@...nel.org>, "coresight@...ts.linaro.org"
	<coresight@...ts.linaro.org>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-rt-devel@...ts.linux.dev"
	<linux-rt-devel@...ts.linux.dev>, nd <nd@....com>
Subject: Re: [PATCH 1/9] coresight: change coresight_device lock type to
 raw_spinlock_t

 Hi Steve,

> > > Still should be documented somewhere. It should describe the maximum number
> > > of feats that will ever be loaded. If there's a max, it makes it back to
> > > O(1). With a 'k' of how long it takes to process the max number of feats.
> >
> > But with other patchset seems better
> > since not only this function, but also for other functions too.

> Which other patchset?

I mean I'll send with seperate patchset to documents this.
Because I'm not sure documents here or in other file...

>
> BTW, is there any example describing this I can refer?

> No, it's on our todo list for RT. To document the RT behavior of the
> kernel. This is just one location.

Thanks to let me know :)