public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Peter Keilty <peter.keilty@hp.com>
Cc: Daniel Walker <dwalker@mvista.com>,
	linux-ia64@vger.kernel.org, Eric Whitney <eric.whitney@hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ia64: convert to use clocksource code
Date: Wed, 02 May 2007 10:58:27 -0700	[thread overview]
Message-ID: <1178128707.6183.6.camel@localhost.localdomain> (raw)
In-Reply-To: <463220C8.5060408@hp.com>

On Fri, 2007-04-27 at 12:11 -0400, Peter Keilty wrote:
> Daniel Walker wrote:
> >On Fri, 2007-04-27 at 11:42 -0400, Peter Keilty wrote:
> >>>There is a read(), and a vread() did you modify the slow syscall path to
> >>>use the vread()?
> >>> 
> >John mentioned that he thought fsys_mmio_ptr could be held in the vread
> >pointer. vread() is used in x86 for vsyscalls. It looks like you've used
> >the update_vsyscall() which is also used for vsyscalls. So vread could
> >also be used .. Have you considered that at all?
> >  
> >
> No, but yes it can be done, overloading the meaning.

Yea. I'm not really psyched about overloading the vread pointer's use. I
mentioned it could be done if the #ifdef was objected to, but it seems a
bit abusive. The #ifdef isn't great, but I think its something I can
live with for now. At least its explicit.

> It would need to change in the future if vread was needed.
> I have no strong argument against  using it.

Yea. I'd hold off on that for now.

thanks
-john



  parent reply	other threads:[~2007-05-02 17:58 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
2007-05-02 17:58             ` john stultz [this message]
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=1178128707.6183.6.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=dwalker@mvista.com \
    --cc=eric.whitney@hp.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