From: Thomas Gleixner <tglx@linutronix.de>
To: Pierre Tardy <pierre.tardy@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
Roman Zippel <zippel@linux-m68k.org>, Andi Kleen <ak@suse.de>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH] lapic-timer: increase the max_delta to 31 bits
Date: Mon, 10 Jan 2011 09:36:31 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1101100932400.12146@localhost6.localdomain6> (raw)
In-Reply-To: <1294327409-19426-1-git-send-email-pierre.tardy@intel.com>
On Thu, 6 Jan 2011, Pierre Tardy wrote:
> Latest atom socs(penwell) does not have hpet timer.
>
> As their local APIC timer is clocked at 400KHZ, and the current code
> limit their Initial Counter register to 23 bits, they cannot sleep
> more than 1.34 seconds which leads to ~2 spurious wakeup per second (1 per thread)
>
> These SOCs support 32bit timer so we change the max_delta to at least 31bits.
> So we can at least sleep for 300 seconds.
>
> We could not find any previous chip errata where lapic would only have 23 bit precision
> As powertop is suggesting to activate HPET to "sleep longer", this could mean this problem is
> already known.
I have no idea why I put this limit there back then. If there is no
erratum then there is no reason to keep it.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
> Problem is here since very first implementation of lapic timer as a clock event
> e9e2cdb [PATCH] clockevents: i386 drivers
> cc contributors of the first patch and x86 maintainers
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
> index 7821813..c031f1d 100644
> --- a/arch/x86/kernel/apic/apic.c
> +++ b/arch/x86/kernel/apic/apic.c
> @@ -684,7 +684,7 @@ static int __init calibrate_APIC_clock(void)
> lapic_clockevent.mult = div_sc(delta, TICK_NSEC * LAPIC_CAL_LOOPS,
> lapic_clockevent.shift);
> lapic_clockevent.max_delta_ns =
> - clockevent_delta2ns(0x7FFFFF, &lapic_clockevent);
> + clockevent_delta2ns(0x7FFFFFFF, &lapic_clockevent);
> lapic_clockevent.min_delta_ns =
> clockevent_delta2ns(0xF, &lapic_clockevent);
>
> --
> 1.7.0.4
>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number: 302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
next prev parent reply other threads:[~2011-01-10 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 15:23 Pierre Tardy
2011-01-10 8:36 ` Thomas Gleixner [this message]
2011-01-10 8:39 ` [tip:x86/urgent] x86, lapic-timer: Increase " tip-bot for Pierre Tardy
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=alpine.LFD.2.00.1101100932400.12146@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=hpa@linux.intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pierre.tardy@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=x86@kernel.org \
--cc=zippel@linux-m68k.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®