linux-kernel - Re: [ANNOUNCE] System Inactivity Monitor v1.0

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: <20070130000341.GA17483@elf.ucw.cz>
Date:	Tue, 30 Jan 2007 01:03:41 +0100
From:	Pavel Machek <pavel@....cz>
To:	Alessandro Di Marco <dmr@....it>
Cc:	Vojtech Pavlik <vojtech@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] System Inactivity Monitor v1.0

Hi!
>    >    The /proc/bus/input/devices has an extensible structure. You can just
>    >    add an "A:" line (for Activity) instead of adding a new proc file.
>    > 
>    > I know, but IMO there is too much stuff to parse in there. Activity counters
>    > are frequently accessed by daemons, and four or five concurrent daemons are the
>    > norm in a typical X11 linux box...
> 
>    Syscalls are fast enough, and the file is _very_ easy (=> fast) to parse.
> 
>    >    Also, the activity counters should IMO coincide with the event times
>    >    passed through /dev/input/event, and should not be jiffies based.
>    >    Ideally, both should be based on clock_gettime(CLOCK_MONOTONIC).
>    > 
>    > In evdev.c do_gettimeofday() is used. Anyway I just need of a monotonic
>    > counter, so get_jiffies_64() wouldn't be better? It isn't affected by wrapping
>    > issues and it is probably faster than do_gtod().
> 
>    Just use same time source rest of inputs already do...
> 
> OK, but what about the time-warp problem?. To fix it I need to know when the
> system goes to sleep/resumes. In SIN I've solved via the platform driver,
> introducing suspend() resume() callbacks...

input drivers will already have suspend() resume() callbacks... could
you reuse those?

...hmm, I see no easy place where to hook these. You could reuse your
platform device trick, I guess... but maybe there's a better way?

Vojtech, do we have some "global" hooks for input suspend/resume? This
code is global to all the devices, but still needs to know about
suspend/resume...

Or we could create notifier list, where interested parties would be
informed of suspend/resume...
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/