linux-kernel - Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks

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]

Message-ID: <20070402221742.GE10574@sequoia.sous-sol.org>
Date:	Mon, 2 Apr 2007 15:17:42 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Chris Wright <chrisw@...s-sol.org>, Ingo Molnar <mingo@...e.hu>,
	john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks

* Thomas Gleixner (tglx@...utronix.de) wrote:
> On Mon, 2007-04-02 at 14:39 -0700, Chris Wright wrote:
> > the part i know is broken is lapic broadcast, so i'd like to fix that
> > up too.  trouble is, it's broken on vanilla too, so i'm not 100% sure
> > what i'm debugging yet.
> 
> You need to remove switch_APIC_timer_to_ipi and counterpart so that the
> clockevents broadcast gets control over broadcasting. This requires a
> change in drivers/acpi/processor_idle.c as well
> 
> commit e9e2cdb412412326c4827fc78ba27f410d837e6e has the basic changes. 

Yeah, I saw that, and while I didn't remove it yet, it shouldn't be
getting called from anywhere because of CONFIG_GENERIC_CLOCKEVENTS
being set.  In fact, acpi_propagate_timer_broadcast() does get called,
and all that does it drop me back to hpet because of C3.  But, I didn't add
DUMMY yet, and I must've missed smth else.  Some of that got a little
tangled into the nice calibration cleanup, which I didn't want to suck
in until I understood what I had broken ;-)

thanks,
-chris
-
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/