From: john stultz <johnstul@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] linux-2.4.23-pre9_ia64-cyclone_A0
Date: Tue, 18 Nov 2003 18:44:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106918249303475@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106911773604958@msgid-missing>
On Tue, 2003-11-18 at 08:42, Bjorn Helgaas wrote:
> Apart from that correctness question, I have some concerns about
> how the code is structured. I don't think I've seen the actual
> SGI patch either, but based on John Hawkes' email (URL above),
> the hook looks something like:
>
> + if (ia64_platform_timer_interrupt)
> + (*ia64_platform_timer_interrupt)();
>
> That's far better than adding stuff like this:
>
> + if(use_cyclone)
> + return do_gettimeoffset_cyclone() + lost * (1000000 / HZ);
>
> because the former is much more generic.
Very much agreed.
> I also don't like adding asm-ia64/cyclone.c and ia64/kernel/cyclone.c.
> Those files are machine-specific and don't belong in the generic ia64
> area. (In fact, they look functionally identical to the i386 code;
> could this all be consolidated in something under drivers/ and shared?)
My plan is to do exactly that (and a bit more) for 2.7. As for 2.4 and
2.5, I'm a bit more hesitant about consolidating the code across arches.
Outside the constants and init function not much is really shared
(although they are structurally similar), and there are still some
subtle differences between those (casting changes and fixmap vs
ioremap). At this point I'd like to avoid the code churn in the i386
dir. However I'd be happy to more the ia64 bits into drivers/ as you
suggest.
thanks for the feedback!
-john
prev parent reply other threads:[~2003-11-18 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 1:01 [RFC][PATCH] linux-2.4.23-pre9_ia64-cyclone_A0 john stultz
2003-11-18 1:02 ` john stultz
2003-11-18 1:08 ` john stultz
2003-11-18 16:42 ` Bjorn Helgaas
2003-11-18 18:44 ` john stultz [this message]
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=marc-linux-ia64-106918249303475@msgid-missing \
--to=johnstul@us.ibm.com \
--cc=linux-ia64@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