From: Vojtech Pavlik <vojtech@suse.cz>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, "Nakajima,
Jun" <jun.nakajima@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>
Subject: Re: [PATCH][2.6][5/5]Support for HPET based timer
Date: Wed, 20 Aug 2003 00:41:04 +0200 [thread overview]
Message-ID: <20030819224104.GB13346@ucw.cz> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1902C7D1C7@fmsmsx405.fm.intel.com>
On Tue, Aug 19, 2003 at 12:20:22PM -0700, Pallipadi, Venkatesh wrote:
> 5/5 - hpet5.patch - This can be a standalone patch. Without this
> patch we loose interrupt generation capability
> of RTC (/dev/rtc), due to HPET. With this patch
> we basically try to emulate RTC interrupt
> functions in software using HPET counter 1.
>
This is very wrong IMO. We shouldn't try to emulate the RTC interrupt
for the kernel, instead the HPET should use native APIC interrupt
routing. This way the RTC will keep working and the 'legacy mode' of
HPET doesn't need to be used. I must admit I was a bit lazy when I was
implementing the x86_64 variant and the native IRQ for HPET is still on
my to-do list.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-08-19 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 19:20 Pallipadi, Venkatesh
2003-08-19 22:41 ` Vojtech Pavlik [this message]
2003-08-20 0:08 ` Jamie Lokier
2003-08-20 8:03 ` Vojtech Pavlik
[not found] <mmGp.wp.3@gated-at.bofh.it>
[not found] ` <mnsM.1eL.13@gated-at.bofh.it>
[not found] ` <moRP.2r8.11@gated-at.bofh.it>
2003-08-20 0:31 ` Andi Kleen
2003-08-20 1:04 ` Jamie Lokier
2003-08-20 8:05 ` Vojtech Pavlik
2003-08-20 1:28 Pallipadi, Venkatesh
2003-08-20 8:10 ` Vojtech Pavlik
2003-08-20 17:51 Pallipadi, Venkatesh
2003-08-21 8:25 ` Vojtech Pavlik
2003-08-21 20:56 Pallipadi, Venkatesh
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=20030819224104.GB13346@ucw.cz \
--to=vojtech@suse.cz \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=venkatesh.pallipadi@intel.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
all inboxes | Powered by JetHome®