public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: update to use the new 4L headers
Date: Thu, 28 Apr 2005 12:15:10 +1000	[thread overview]
Message-ID: <4270472E.9050708@yahoo.com.au> (raw)
In-Reply-To: <427044AA.5030402@nortel.com>

Chris Friesen wrote:
> Nick Piggin wrote:
> 
>> Just a bit off-topic: I wonder how many more of these open
>> coded pt walks exist in arch code (yes I see you've cleaned
>> yours up - good).
> 
> 
> I know there's open coded walks outside the tree (I maintain one) due to 
> there being no suitable function available from with in it...
> 

Oh - I meant hand calculating the addresses rather than using
the pmd_addr_end and friends... but:

> I needed something like:
> 
> pte_t *va_to_ptep_map(struct mm_struct *mm, unsigned int addr)
> 
> There was code in follow_page() that did basically what I needed, but it 
> was all contained within that function so I had to re-implement it.
> 

If you can break out exactly what you need, and make that inline
or otherwise available via the correct header, I'm sure it would
have a good chance of being merged.

Keep in mind that you shouldn't introduce an inefficiency to
follow_page, however if that is not possible you could simply
duplicate what you need in a seperate function in mm/memory.c and
use that - better to do it once there than a lot of times in
random places.

-- 
SUSE Labs, Novell Inc.


  reply	other threads:[~2005-04-28  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  1:33 [PATCH] ppc64: update to use the new 4L headers Benjamin Herrenschmidt
2005-04-28  1:49 ` Nick Piggin
2005-04-28  2:04   ` Chris Friesen
2005-04-28  2:15     ` Nick Piggin [this message]
2005-05-02  0:17       ` Peter Chubb

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=4270472E.9050708@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.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