linux-kernel - Re: [PATCH 1/3] clockevents: Use an atomic RCU notifier for clockevents

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:	Wed, 7 Sep 2011 01:19:06 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andi Kleen <ak@...ux.intel.com>
cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] clockevents: Use an atomic RCU notifier for
 clockevents

On Tue, 6 Sep 2011, Andi Kleen wrote:

> > The idle code, at least the one in drivers/idle/intel_idle.c, does
> > _NOT_ call into that code at all when a reliable lapic timer is
> > available:
> 
> But the ACPI idle doesn't check that, so it still has a scalability problem.
> 
> Hmm ok so could add that check into acpi idle too I guess, but then ACPI
> idle doesn't normally know anything about CPUs.
> 
> > Either you are using different code or your machine does not have that
> > ARAT flag set.
> 
> The second test was using ACPI idle.

And as I said in that very same mail:

> > Same applies for drivers/acpi/processor_idle.c

lapic_timer_check_state()
{
       if (cpu_has(&cpu_data(pr->id), X86_FEATURE_ARAT))
                return;
....

WTF are you talking about? 

Thanks,

	tglx
--
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/