public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Jamie Lokier <jamie@shareable.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	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 10:03:41 +0200	[thread overview]
Message-ID: <20030820080341.GA17793@ucw.cz> (raw)
In-Reply-To: <20030820000856.GE18035@mail.jlokier.co.uk>

On Wed, Aug 20, 2003 at 01:08:56AM +0100, Jamie Lokier wrote:
> Vojtech Pavlik wrote:
> > 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.
> 
> Even on those machines where APIC interrupts are not usable?
> (E.g. due to interactions with the SMM BIOS).

Well, I suspect the machines with HPET should better have usable APIC
interrupts, because you won't be able to use all the HPET timers then -
only two can be routed via the timer and RTC interrupts, the other need
to use APIC or direct FSB delivery.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-08-20  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 19:20 [PATCH][2.6][5/5]Support for HPET based timer Pallipadi, Venkatesh
2003-08-19 22:41 ` Vojtech Pavlik
2003-08-20  0:08   ` Jamie Lokier
2003-08-20  8:03     ` Vojtech Pavlik [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
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=20030820080341.GA17793@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=asit.k.mallick@intel.com \
    --cc=jamie@shareable.org \
    --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