linux-kernel - Re: [PATCH] time: x86: report_lost

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]

Date:	Wed, 23 Jan 2013 12:12:59 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	x86@...nel.org, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] time: x86: report_lost_ticks doesn't exist any more

On Thu, 17 Jan 2013, Jiri Kosina wrote:

> 'report_lost_ticks' parameter has been removed back in 2007 through 
> 1489939f0ab ("time: x86_64: convert x86_64 to use GENERIC_TIME").
> 
> Signed-off-by: Jiri Kosina <jkosina@...e.cz>
> ---
>  Documentation/x86/x86_64/boot-options.txt |    4 ----
>  1 files changed, 0 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/x86/x86_64/boot-options.txt b/Documentation/x86/x86_64/boot-options.txt
> index de38429..e015a83 100644
> --- a/Documentation/x86/x86_64/boot-options.txt
> +++ b/Documentation/x86/x86_64/boot-options.txt
> @@ -112,10 +112,6 @@ Timing
>    This can be used to work around timing problems on multiprocessor systems
>    with not properly synchronized CPUs.
>  
> -  report_lost_ticks
> -  Report when timer interrupts are lost because some code turned off
> -  interrupts for too long.
> -
>    nohpet
>    Don't use the HPET timer.

Noone seems to have picked this up, I am taking it through trivial.git

-- 
Jiri Kosina
SUSE Labs
--
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/