public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: 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 11:49:36 +1000	[thread overview]
Message-ID: <42704130.9050005@yahoo.com.au> (raw)
In-Reply-To: <1114652039.7112.213.camel@gaston>

Benjamin Herrenschmidt wrote:
> Hi !
> 
> This patch converts ppc64 to use the generic pgtable-nopud.h instead of
> the "fixup" header.
> 

Great! Nice work Ben.

> -
> -static void unmap_im_area_pmd(pgd_t *dir, unsigned long address,
> -				  unsigned long size)
> -{
> -	unsigned long base, end;
> -	pmd_t *pmd;
> -
> -	if (pgd_none(*dir))
> -		return;
> -	if (pgd_bad(*dir)) {
> -		pgd_ERROR(*dir);
> -		pgd_clear(dir);
> -		return;
> -	}
> -
> -	pmd = pmd_offset(dir, address);
> -	base = address & PGDIR_MASK;
> -	address &= ~PGDIR_MASK;
> -	end = address + size;
> -	if (end > PGDIR_SIZE)
> -		end = PGDIR_SIZE;
> -
> -	do {
> -		unmap_im_area_pte(pmd, base + address, end - address);
> -		address = (address + PMD_SIZE) & PMD_MASK;
> -		pmd++;
> -	} while (address < end);
> -}

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 guess they don't matter much? They will probably get
converted when arches convert to the 4L headers.

-- 
SUSE Labs, Novell Inc.


  reply	other threads:[~2005-04-28  1:49 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 [this message]
2005-04-28  2:04   ` Chris Friesen
2005-04-28  2:15     ` Nick Piggin
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=42704130.9050005@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --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