From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "David Mosberger-Tang" <David.Mosberger@acm.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [PATCHSET][2.6-test4][0/6]Support for HPET based timer - Take 2
Date: Fri, 29 Aug 2003 09:12:52 -0700 [thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1902C7D222@fmsmsx405.fm.intel.com> (raw)
The part of the patch that does the HPET initialization for timer
interrupt, and general HPET registers read/write/programming can be
common across architectures.
However, different archs diverge, when it comes to gettimeofday-timer
implementation (tsc, pit, itc, hpet, ) and we may still have to keep
that part architecture specific.
Thanks,
Venkatesh
> -----Original Message-----
> From: David Mosberger-Tang [mailto:David.Mosberger@acm.org]
> Sent: Thursday, August 28, 2003 8:41 PM
> To: Pallipadi, Venkatesh
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCHSET][2.6-test4][0/6]Support for HPET based
> timer - Take 2
>
>
> >>>>> On Fri, 29 Aug 2003 01:50:09 +0200, "Pallipadi,
> Venkatesh" <venkatesh.pallipadi@intel.com> said:
>
> Venkatesh> Resending the patch. A major change from previous version
> Venkatesh> is elimination of fixmap for HPET. Based on Andrew
> Venkatesh> Morton's suggestion, we have a new hook in init/main.c
> Venkatesh> for late_time_init(), at which time we can use ioremap,
> Venkatesh> in place of fixmap. Impact on other archs:
> Venkatesh> Calibrate_delay() (and hence loops_per_jiffy calculation)
> Venkatesh> has moved down in main.c, from after time_init() to after
> Venkatesh> kmem_cache_init().
>
> Venkatesh> All comments/feedbacks welcome.
>
> How much is really architecture-specific? HPET isn't x86-only so
> sooner or later, we'll have to move it out of arch/i386 anyhow.
>
> --david
>
next reply other threads:[~2003-08-29 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 16:12 Pallipadi, Venkatesh [this message]
2003-08-30 4:59 ` [PATCHSET][2.6-test4][0/6]Support for HPET based timer - Take 2 David Mosberger-Tang
-- strict thread matches above, loose matches on Subject: below --
2003-09-06 19:04 Pallipadi, Venkatesh
2003-09-07 17:57 ` George Anzinger
2003-08-30 16:26 Pallipadi, Venkatesh
2003-08-29 23:58 Pallipadi, Venkatesh
2003-09-05 22:26 ` George Anzinger
[not found] <pEGJ.73p.5@gated-at.bofh.it>
2003-08-29 3:40 ` David Mosberger-Tang
2003-08-28 23:41 Pallipadi, Venkatesh
2003-08-29 18:23 ` Andrew Morton
2003-08-29 21:03 ` Erik Andersen
2003-08-31 21:05 ` Linus Torvalds
2003-08-31 22:24 ` Erik Andersen
2003-08-31 22:48 ` Linus Torvalds
2003-09-05 22:19 ` George Anzinger
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=C8C38546F90ABF408A5961FC01FDBF1902C7D222@fmsmsx405.fm.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=David.Mosberger@acm.org \
--cc=linux-kernel@vger.kernel.org \
/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).