linux-kernel - Re: Proper kernel irq time accounting -v4

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: <4CB72BF3.4030601@digium.com>
Date:	Thu, 14 Oct 2010 11:12:35 -0500
From:	Shaun Ruffell <sruffell@...ium.com>
To:	Venkatesh Pallipadi <venki@...gle.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Proper kernel irq time accounting -v4

On 10/04/2010 07:03 PM, Venkatesh Pallipadi wrote:
> Solution to (1) involves adding extra timing on irq entry/exit to
> get the fine granularity info and then exporting it to user.
> The following patchset addresses this problem in a way similar to [2][3].
> Keeps most of the code that does the timing generic
> (CONFIG_IRQ_TIME_ACCOUNTING), based off of sched_clock(). And adds support for
> this in x86. This time is not yet exported to userspace yet. Patch for that
> coming soon.
> 

Would you be willing to share your thoughts on how you plan to export
this information to userspace?

I applied this set to one of my machines in hopes of seeing more
accurate hi time before I noticed that in the quoted paragraph you said
this is still forthcoming.

Thanks,
Shaun
--
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/