Hi!
> > I believe probability someone uses that with more than 4 CPUs is <
> > 5%.
>
> So you even didn't bother to check:
>
> $ git grep "default-trigger = \"cpu[4-9]"
> arch/arm/boot/dts/vexpress-v2m-rs1.dtsi: linux,default-trigger = "cpu4";
> arch/arm/boot/dts/vexpress-v2m-rs1.dtsi:
On 9/25/20 11:40 AM, Pavel Machek wrote:
Hi!
So.. no, it is not causing kernel crashes or something. But it is
example of bad interface, and _that_ is causing problems. (And yes, if
I realized it is simply possible to limit it, maybe the BIN_ATTR
conversion would not be neccessary...)
The
Hi!
> >>So.. no, it is not causing kernel crashes or something. But it is
> >>example of bad interface, and _that_ is causing problems. (And yes, if
> >>I realized it is simply possible to limit it, maybe the BIN_ATTR
> >>conversion would not be neccessary...)
> >
> >The limitation you proposed
On 9/22/20 10:41 PM, Jacek Anaszewski wrote:
Hi Pavel,
On 9/22/20 12:42 AM, Pavel Machek wrote:
Hi!
Can I get details of your setup?
I don't use this trigger, but I can imagine that someone does.
Well, if someone exists, we can increase the limit, or convince them
to change their setup.
Hi Pavel,
On 9/22/20 12:42 AM, Pavel Machek wrote:
Hi!
Can I get details of your setup?
I don't use this trigger, but I can imagine that someone does.
Well, if someone exists, we can increase the limit, or convince them
to change their setup.
Linux is used in many commercial projects
Hi!
> >Can I get details of your setup?
>
> I don't use this trigger, but I can imagine that someone does.
Well, if someone exists, we can increase the limit, or convince them
to change their setup.
> >What CPU type that is, and how are you mapping CPU activity to LEDs?
>
> The type of CPU is
On 9/20/20 8:34 PM, Pavel Machek wrote:
Hi!
*
* It can be bound to any LED just like other triggers using either a
* board file or via sysfs interface.
*
* An API named ledtrig_cpu is exported for any user, who want to add CPU
- * activity indication in their code
+ *
Hi!
> >*
> >* It can be bound to any LED just like other triggers using either a
> >* board file or via sysfs interface.
> >*
> >* An API named ledtrig_cpu is exported for any user, who want to add CPU
> > - * activity indication in their code
> > + * activity indication in
318681d3e019e39354cc6c2155a7fd1bb8e8084d
Author: Pavel Machek
Date: Sat Sep 19 11:34:58 2020 +0200
ledtrig-cpu: Limit to 4 CPUs
Some machines have thousands of CPUs... and trigger mechanisms was not
really meant for thousands of triggers. I doubt anyone uses this
trigger on many-CPU
>>> commit 318681d3e019e39354cc6c2155a7fd1bb8e8084d
> >>> Author: Pavel Machek
> >>> Date: Sat Sep 19 11:34:58 2020 +0200
> >>>
> >>> ledtrig-cpu: Limit to 4 CPUs
> >>>
> >>> Some machines hav
On 9/20/20 5:39 PM, Marek Behun wrote:
On Sun, 20 Sep 2020 16:15:09 +0200
Jacek Anaszewski wrote:
Hi Pavel,
On 9/19/20 11:38 AM, Pavel Machek wrote:
commit 318681d3e019e39354cc6c2155a7fd1bb8e8084d
Author: Pavel Machek
Date: Sat Sep 19 11:34:58 2020 +0200
ledtrig-cpu: Limit to 4
On Sun, 20 Sep 2020 16:15:09 +0200
Jacek Anaszewski wrote:
> Hi Pavel,
>
> On 9/19/20 11:38 AM, Pavel Machek wrote:
> > commit 318681d3e019e39354cc6c2155a7fd1bb8e8084d
> > Author: Pavel Machek
> > Date: Sat Sep 19 11:34:58 2020 +0200
> >
>
Hi Pavel,
On 9/19/20 11:38 AM, Pavel Machek wrote:
commit 318681d3e019e39354cc6c2155a7fd1bb8e8084d
Author: Pavel Machek
Date: Sat Sep 19 11:34:58 2020 +0200
ledtrig-cpu: Limit to 4 CPUs
Some machines have thousands of CPUs... and trigger mechanisms was not
really meant
13 matches
Mail list logo
