[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<GV1PR08MB105212FEF9251CA2B3AAF7FFFFB362@GV1PR08MB10521.eurprd08.prod.outlook.com>
Date: Tue, 3 Dec 2024 08:31:54 +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.
BTW, is there any example describing this I can refer?
Thanks
Powered by blists - more mailing lists