Messages in this thread | | | Subject | Re: [PATCH] time: x86: report_lost_ticks doesn't exist any more | From | "H. Peter Anvin" <> | Date | Wed, 23 Jan 2013 08:43:45 -0600 |
| |
That works. You can add my Ack if you want. Thanks!
Jiri Kosina <jkosina@suse.cz> wrote:
>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@suse.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
-- Sent from my mobile phone. Please excuse brevity and lack of formatting.
| |