From: Andi Kleen <ak@suse.de>
To: tglx@linutronix.de
Cc: Chris Wright <chrisw@sous-sol.org>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks
Date: Sun, 1 Apr 2007 22:53:20 +0200 [thread overview]
Message-ID: <200704012253.20834.ak@suse.de> (raw)
In-Reply-To: <1175419332.28263.67.camel@localhost.localdomain>
> Have you checked, if we could share the code between i386 and x86_64 at
> least for PIT and HPET. I'm not sure about the local APIC, but I think
> it might be doable as well.
Not for PIT. I don't want all the broken ancient hardware workarounds on x86-64.
HPET might be doable, but would need quite some work.
-Andi
next prev parent reply other threads:[~2007-04-01 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 8:31 [RFC PATCH 0/5] x86_64: enable clockevents and dynticks 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
2007-04-01 20:53 ` Andi Kleen [this message]
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=200704012253.20834.ak@suse.de \
--to=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.