LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chris Wright <chrisw@sous-sol.org>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks
Date: Mon, 2 Apr 2007 15:17:42 -0700 [thread overview]
Message-ID: <20070402221742.GE10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <1175550764.28263.190.camel@localhost.localdomain>
* Thomas Gleixner (tglx@linutronix.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
next prev parent reply other threads:[~2007-04-02 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 8:31 Chris Wright
2007-03-31 8:31 ` [RFC PATCH 1/5] x86_64: untangle asm/hpet.h from asm/timex.h Chris Wright
2007-03-31 8:31 ` [RFC PATCH 2/5] x86_64: drive set_rtc_mss from standalone timer Chris Wright
2007-03-31 8:31 ` [RFC PATCH 3/5] x86_64: clockevents drivers Chris Wright
2007-03-31 8:31 ` [RFC PATCH 4/5] x86_64: prep idle loop for dynticks Chris Wright
2007-03-31 8:31 ` [RFC PATCH 5/5] x86_64: enable dynticks Chris Wright
2007-03-31 9:23 ` [RFC PATCH 0/5] x86_64: enable clockevents and dynticks Ingo Molnar
2007-03-31 16:36 ` Chris Wright
2007-03-31 16:46 ` Ingo Molnar
2007-04-01 9:22 ` Thomas Gleixner
2007-04-01 18:54 ` Chris Wright
2007-04-02 21:31 ` Thomas Gleixner
2007-04-02 21:39 ` Chris Wright
2007-04-02 21:52 ` Thomas Gleixner
2007-04-02 22:17 ` Chris Wright [this message]
2007-04-01 20:53 ` Andi Kleen
2007-04-02 7:27 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070402221742.GE10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--subject='Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).