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]
Date:	Sat, 5 Jan 2013 17:50:54 -0800
From:	Sadasivan Shaiju <sshaiju@...sta.com>
To:	Shaun Ruffell <sruffell@...ium.com>
Cc:	linux-kernel@...r.kernel.org, venki@...gle.com,
	a.p.zijlstra@...llo.nl
Subject: RE: Incorrect accounting of irq into the running task

Hi Shaun,

-----Original Message-----
From: Shaun Ruffell [mailto:sruffell@...ium.com]
Sent: Saturday, January 05, 2013 9:21 AM
To: Sadasivan Shaiju
Cc: linux-kernel@...r.kernel.org; venki@...gle.com; a.p.zijlstra@...llo.nl
Subject: Re: Incorrect accounting of irq into the running task

On Fri, Jan 04, 2013 at 10:22:12AM -0800, Sadasivan Shaiju wrote:
> Hi  Venkatesh,
>
> I have applied the following patches for the incorrect accounting of
> irq into the running task .
>
>
> [PATCH] x86: Add IRQ_TIME_ACCOUNTING
> [e82b8e4ea4f3dffe6e7939f90e78da675fcc450e]
> [PATCH] sched: Add IRQ_TIME_ACCOUNTING, finer accounting of irq time
> [b52bfee445d315549d41eacf2fa7c156e7d153d5]
>
> [PATCH] sched: Do not account irq time to current task
> [305e6835e05513406fa12820e40e4a8ecb63743c]
> [PATCH] sched: Export ns irqtimes through /proc/stat
> [abb74cefa9c682fb38ba86c17ca3c86fed6cc464]
>
>
>
> But still the stime and utime of the process in /proc/pid/stat is
> high. I think the above patches does not update The stime and utime
> values in /proc/pid/stat.
>
>
> Or am I missing anything?

Just checking that you do have CONFIG_IRQ_TIME_ACCOUNTING=y in your kernel
config?

  Yes  it  is  turned  on  .

Regards,
Shaiju.

Cheers,
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ