From: Ingo Molnar <mingo@elte.hu>
To: venkatesh.pallipadi@intel.com
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
shaohua.li@intel.com, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [RFC 0/4] Using HPET in MSI mode and setting up per CPU HPET timers
Date: Sat, 6 Sep 2008 14:42:34 +0200 [thread overview]
Message-ID: <20080906124234.GG30964@elte.hu> (raw)
In-Reply-To: <20080906010214.229910000@intel.com>
* venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com> wrote:
> Patchset that uses HPET timers in MSI mode (when supported) and sets
> up per CPU HPET timers. This removes the dependency on IRQ0 timer
> broadcast with LAPIC stopping in deep C-state, on platforms that
> support HPET MSI mode.
>
> On my test system with dual core CPU, the number of timer related
> interrupts (HPET_MSI + IRQ0 + LAPIC) comes down from 180 to 95 over a
> period of 10s, with these patches. This is on an idle system with
> tickless enabled and when system is idle.
>
> Patches against tip.
cool stuff!
this is _really_ how a modern dynticks system should look like on x86 -
proper per CPU hardware timers that are southbridge based.
There's a few routine checks this new has to pass: we've got to see how
widely this works and whether there are any bugs/quirks to take care of,
so i created a separate feature topic for it: tip/timers/hpet-percpu.
This tip/timers/hpet-percpu feature topic tree is based on irq/sparseirq
+ timers/hpet + timers/urgent - which had some changes in the hpet area.
I merged up the conflicts - please double check the result. I also did
cleanups for a few style problems that were present in hpet.c.
I've merged it into tip/master as well and will run a few tests before
pushing it out.
Ingo
next prev parent reply other threads:[~2008-09-06 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 1:02 [RFC 0/4] Using HPET in MSI mode and setting up per CPU HPET timers venkatesh.pallipadi
2008-09-06 1:02 ` [RFC 1/4] x86: HPET_MSI change IRQ affinity in process context when it is disabled venkatesh.pallipadi
2008-09-06 1:02 ` [RFC 2/4] x86: HPET_MSI Refactor code in preparation for HPET_MSI venkatesh.pallipadi
2008-09-06 1:02 ` [RFC 3/4] x86: HPET_MSI Basic HPET_MSI setup code venkatesh.pallipadi
2008-09-06 1:02 ` [RFC 4/4] x86: HPET_MSI Initialise per-cpu HPET timers venkatesh.pallipadi
2008-09-06 12:42 ` Ingo Molnar [this message]
2008-09-06 13:03 ` [RFC 0/4] Using HPET in MSI mode and setting up per CPU " Ingo Molnar
2008-09-08 17:18 ` Venki Pallipadi
2008-09-08 17:55 ` Ingo Molnar
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=20080906124234.GG30964@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yhlu.kernel@gmail.com \
/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