LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Ingo Molnar" <mingo@redhat.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: RE: [PATCH 1/5] RT kernel: force detect HPET from PCI space
Date: Fri, 30 Mar 2007 06:36:46 -0700	[thread overview]
Message-ID: <653FFBB4508B9042B5D43DC9E18836F52DF55E@scsmsx415.amr.corp.intel.com> (raw)
In-Reply-To: <1175248003.6157.43.camel@earth4>

 

>-----Original Message-----
>From: Ingo Molnar [mailto:mingo@redhat.com] 
>Sent: Friday, March 30, 2007 2:47 AM
>To: Pallipadi, Venkatesh
>Cc: linux-kernel; Thomas Gleixner
>Subject: Re: [PATCH 1/5] RT kernel: force detect HPET from PCI space
>
>On Thu, 2007-02-22 at 17:06 -0800, Venkatesh Pallipadi wrote:
>> Patchset enables force detection of HPET, when it is not listed by
>> BIOS.
>> and enables use of HPET as a event source. HPET timers
>> configures in stamdard interrupt mode can be used as dependable per
>> CPU timer
>> on laptops that are known to have LAPIC stoppage with ACPI C3 state.
>
>(sorry about the belated reply)
>
>cool patchset! I suspect the most logical place to start this would be
>on upstream 32-bit, which has the hpet clockevents changes already.
>Plus the i386 and x86_64 hpet code should be unified.
>

Yes. I restarted the work recently with i386 and upstream. I should
have the some patches in couple of weeks time.

Thanks,
Venki

  reply	other threads:[~2007-03-30 13:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23  1:06 [PATCH 1/5] RT kernel: force detect HPET from PCI space Venkatesh Pallipadi
2007-03-30  9:46 ` Ingo Molnar
2007-03-30 13:36   ` Pallipadi, Venkatesh [this message]
2007-03-30 16:50 Nicolas Mailhot
2007-03-30 16:59 ` Venki Pallipadi
2007-03-30 17:22   ` Nicolas Mailhot
2007-03-30 22:09 Mikko Tiihonen
2007-03-30 22:38 ` Nicolas Mailhot
2007-03-31  8:00   ` Mikko Tiihonen
2007-03-31 10:37   ` Krzysztof Halasa
2007-03-31 11:36     ` Nicolas Mailhot
2007-03-31 15:00       ` Mikko Tiihonen

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=653FFBB4508B9042B5D43DC9E18836F52DF55E@scsmsx415.amr.corp.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).