From: Daniel Walker <dwalker@mvista.com>
To: Peter Keilty <peter.keilty@hp.com>
Cc: linux-ia64@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
Eric Whitney <eric.whitney@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ia64: convert to use clocksource code
Date: Fri, 27 Apr 2007 16:32:55 +0000 [thread overview]
Message-ID: <1177691575.12796.142.camel@imap.mvista.com> (raw)
In-Reply-To: <463220C8.5060408@hp.com>
On Fri, 2007-04-27 at 12:11 -0400, Peter Keilty wrote:
> >
> No, but yes it can be done, overloading the meaning.
> It would need to change in the future if vread was needed.
> I have no strong argument against using it.
> Although we may still need the IA64 define, I removed 32bit read mmio and
> if that is brought back the fast syscall patch call will need to have a
> field in the
> clocksource struct that would indicated that. Waiting on comments about
> that...
> John and discuss this awhile back felt it was not needed, may prove wrong.
The vread field is just a pointer, which should be 64bits on ia64. Why
do you mention 32bits above? The two variables similar enough ..
Daniel
next prev parent reply other threads:[~2007-04-27 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:26 [PATCH 1/3] ia64: convert to use clocksource code Peter Keilty
2007-04-26 20:27 ` [PATCH 2/3] ia64: remove interpolater code Peter Keilty
2007-04-26 20:52 ` john stultz
2007-04-26 21:47 ` David Miller
2007-04-26 20:27 ` [PATCH 3/3] ia64: update fsyscall for performance, enable build/run on 2.6.21-rc1 Peter Keilty
2007-04-26 20:41 ` [PATCH 1/3] ia64: convert to use clocksource code Sam Ravnborg
2007-04-26 20:48 ` john stultz
2007-04-26 21:07 ` Daniel Walker
2007-04-27 14:38 ` Peter Keilty
2007-04-27 15:35 ` Daniel Walker
2007-04-27 15:42 ` Peter Keilty
2007-04-27 15:48 ` Daniel Walker
2007-04-27 16:11 ` Peter Keilty
2007-04-27 16:32 ` Daniel Walker [this message]
2007-05-02 17:58 ` john stultz
2007-05-02 19:08 ` Daniel Walker
2007-04-26 21:18 ` john stultz
2007-04-27 12:54 ` Peter Keilty
2007-05-02 17:50 ` john stultz
2007-04-27 1:02 ` Chris Wright
2007-04-27 13:35 ` Peter Keilty
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=1177691575.12796.142.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=eric.whitney@hp.com \
--cc=johnstul@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.keilty@hp.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