linux-kernel - Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)

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:	Fri, 10 Sep 2010 09:47:22 +0200
From:	Damien Wyart <damien.wyart@...e.fr>
To:	Nix <nix@...eri.org.uk>
Cc:	Artur Skawina <art.08.09@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Venkatesh Pallipadi <venki@...gle.com>,
	John Drescher <drescherjm@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown
 to unusability (HPET)

> (hm, odd.
> 
> spindle:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
> 
> spindle:~# grep -i tsc /proc/timer_list
> spindle:~# grep -i hpet /proc/timer_list
> Clock Event Device: hpet
>  set_next_event: hpet_legacy_next_event
>  set_mode:       hpet_legacy_set_mode
> 
> I suspect current_clocksource doesn't do what we think it does, or the
> clocksource and 'clock event device' are not the same.)

Yes, same here. When saying I was using tsc in my previous mail, I had
run the first command only, but when running the other two, I get the
same results than you, so HPET seems to be used too.

-- 
Damien Wyart
--
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/