All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Keilty <peter.keilty@hp.com>
To: Daniel Walker <dwalker@mvista.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:11:52 +0000	[thread overview]
Message-ID: <463220C8.5060408@hp.com> (raw)
In-Reply-To: <1177688931.12796.130.camel@imap.mvista.com>

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()?
>>> 
>>>
>>>      
>>>
>>I miss type, read().
>>    
>>
>
>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.
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.

>Daniel
>
>  
>

WARNING: multiple messages have this Message-ID (diff)
From: Peter Keilty <peter.keilty@hp.com>
To: Daniel Walker <dwalker@mvista.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 12:11:52 -0400	[thread overview]
Message-ID: <463220C8.5060408@hp.com> (raw)
In-Reply-To: <1177688931.12796.130.camel@imap.mvista.com>

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()?
>>> 
>>>
>>>      
>>>
>>I miss type, read().
>>    
>>
>
>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.
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.

>Daniel
>
>  
>

  reply	other threads:[~2007-04-27 16:11 UTC|newest]

Thread overview: 42+ 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:26 ` Peter Keilty
2007-04-26 20:27 ` [PATCH 2/3] ia64: remove interpolater code Peter Keilty
2007-04-26 20:27   ` Peter Keilty
2007-04-26 20:52   ` john stultz
2007-04-26 20:52     ` john stultz
2007-04-26 21:47     ` David Miller
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:27   ` Peter Keilty
2007-04-26 20:41 ` [PATCH 1/3] ia64: convert to use clocksource code Sam Ravnborg
2007-04-26 20:41   ` Sam Ravnborg
2007-04-26 20:48   ` john stultz
2007-04-26 20:48     ` john stultz
2007-04-26 21:07 ` Daniel Walker
2007-04-26 21:07   ` Daniel Walker
2007-04-27 14:38   ` Peter Keilty
2007-04-27 14:38     ` Peter Keilty
2007-04-27 15:35     ` Daniel Walker
2007-04-27 15:35       ` Daniel Walker
2007-04-27 15:42       ` Peter Keilty
2007-04-27 15:42         ` Peter Keilty
2007-04-27 15:48         ` Daniel Walker
2007-04-27 15:48           ` Daniel Walker
2007-04-27 16:11           ` Peter Keilty [this message]
2007-04-27 16:11             ` Peter Keilty
2007-04-27 16:32             ` Daniel Walker
2007-04-27 16:32               ` Daniel Walker
2007-05-02 17:58             ` john stultz
2007-05-02 17:58               ` john stultz
2007-05-02 19:08               ` Daniel Walker
2007-05-02 19:08                 ` Daniel Walker
2007-04-26 21:18 ` john stultz
2007-04-26 21:18   ` john stultz
2007-04-27 12:54   ` Peter Keilty
2007-04-27 12:54     ` Peter Keilty
2007-05-02 17:50     ` john stultz
2007-05-02 17:50       ` john stultz
2007-04-27  1:02 ` Chris Wright
2007-04-27  1:02   ` Chris Wright
2007-04-27 13:35   ` Peter Keilty
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=463220C8.5060408@hp.com \
    --to=peter.keilty@hp.com \
    --cc=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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.