From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: x86_64 and AMD with C1E
Date: Mon, 1 Oct 2007 16:32:25 +0200 [thread overview]
Message-ID: <20071001143225.GA19797@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LRH.0.999.0710011612001.7353@www.tglx.de>
> There is work in progress on a patch, which allows to utilize the hpet
> timers as per cpu timers. This should solve the problem. Be patient.
Given that e.g. ICH8 only has 3 HPET timers that seems doubtful
except for the special case of single-socket non hyper threaded dual core.
You'll probably do a lot of broadcasting and IPI'ing still.
Also you'll likely make user space unhappy which often requires
at least one free HPET timer for /dev/rtc. Ok I suppose that
could be replaced with a hrtimer.
-Andi
next prev parent reply other threads:[~2007-10-01 14:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 6:15 x86_64 and AMD with C1E Mikhail Kshevetskiy
2007-10-01 9:33 ` Andi Kleen
[not found] ` <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>
2007-10-01 12:50 ` Fwd: " Mikhail Kshevetskiy
2007-10-01 14:14 ` Thomas Gleixner
2007-10-01 14:32 ` Andi Kleen [this message]
2007-10-01 14:59 ` Thomas Gleixner
2007-10-01 15:21 ` Andi Kleen
2007-10-01 16:44 ` Thomas Gleixner
2007-10-01 17:56 ` Chuck Ebbert
2007-10-01 14:33 ` Mikhail Kshevetskiy
2007-10-01 13:09 ` Andi Kleen
2007-10-01 14:06 ` Arjan van de Ven
2007-10-01 14:40 ` Mikhail Kshevetskiy
2007-10-19 16:39 ` Chuck Ebbert
2007-10-24 21:26 ` Mikhail Kshevetskiy
2007-10-24 21:41 ` Chuck Ebbert
2007-10-24 22:12 ` Thomas Gleixner
2007-10-24 22:42 ` Mikhail Kshevetskiy
2007-12-15 11:06 ` 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=20071001143225.GA19797@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.kshevetskiy@gmail.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.