public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pte-highmem-5
Date: Wed, 16 Jan 2002 19:35:21 +0100	[thread overview]
Message-ID: <20020116193521.C835@athlon.random> (raw)
In-Reply-To: <20020116185814.I22791@athlon.random> <Pine.LNX.4.33.0201161002390.2112-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0201161002390.2112-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, Jan 16, 2002 at 10:04:37AM -0800

On Wed, Jan 16, 2002 at 10:04:37AM -0800, Linus Torvalds wrote:
> 
> On Wed, 16 Jan 2002, Andrea Arcangeli wrote:
> >
> > This patch in short will move pagetables into highmem, obviously it
> > breaks all the archs out there.
> 
> Hmm.. Looks ok, although I miss the "obviously". Archs have their own page
> table allocator functions, so by allocating lowmem (and most non-x86 won't
> care) the change _should_ have zero impact on them simply because they
> don't need to unmap. No?

the problem is as usual we need to work with pages or pfn somewhere (see
pte_alloc), we cannot work with virtual addresses or we'll overflow...
the pte_t * virtual address is always the result of the kmap, so the
changes required are the minimal as possible in most places, and I made
a pte_kunmap smart enough to be able to unmap any kind of kmap so the
common code changes are as simple as possible, but still pmd_populate
needs to know the whole thing (struct page * actually) and probably some
other bit of the same kind with the pmd breaks too.

Andrea

  reply	other threads:[~2002-01-16 18:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 17:58 pte-highmem-5 Andrea Arcangeli
2002-01-16 18:04 ` pte-highmem-5 Linus Torvalds
2002-01-16 18:35   ` Andrea Arcangeli [this message]
2002-01-16 18:19 ` pte-highmem-5 Linus Torvalds
2002-01-16 18:48   ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:11     ` pte-highmem-5 Linus Torvalds
2002-01-16 19:30       ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:30   ` pte-highmem-5 Benjamin LaHaise
2002-01-16 19:50     ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:34   ` pte-highmem-5 Rik van Riel
2002-01-17  8:31 ` pte-highmem-5 Christoph Rohland
2002-01-17 12:14   ` pte-highmem-5 Hugh Dickins
2002-01-17 15:45     ` pte-highmem-5 Andrea Arcangeli
2002-01-17 16:08       ` pte-highmem-5 Hugh Dickins
2002-01-17 15:30   ` pte-highmem-5 Andrea Arcangeli
2002-01-17 16:11     ` pte-highmem-5 Christoph Rohland
2002-01-17 16:37       ` pte-highmem-5 Andrea Arcangeli
2002-01-17 17:31       ` pte-highmem-5 Rik van Riel
2002-01-17 17:57 ` pte-highmem-5 Hugh Dickins
2002-01-17 18:09   ` pte-highmem-5 Andrea Arcangeli
2002-01-17 19:02     ` pte-highmem-5 Hugh Dickins
2002-01-18  2:38       ` pte-highmem-5 Andrea Arcangeli
2002-01-19 20:56         ` pte-highmem-5 Hugh Dickins
2002-01-21 18:15           ` pte-highmem-5 Andrea Arcangeli
2002-01-22 18:01             ` pte-highmem-5 Hugh Dickins
2002-01-22 19:10               ` pte-highmem-5 Andrea Arcangeli
2002-01-22 21:41                 ` pte-highmem-5 Hugh Dickins
2002-01-22 23:34                   ` pte-highmem-5 Andrea Arcangeli
2002-01-23  0:56                     ` pte-highmem-5 Paul Mackerras
2002-01-23  1:27                       ` pte-highmem-5 Andrea Arcangeli
2002-01-23  5:38                     ` pte-highmem-5 Hugh Dickins
2002-01-23 16:29                       ` pte-highmem-5 Daniel Phillips
2002-01-23 20:23                         ` pte-highmem-5 Hugh Dickins
2002-01-24  3:09                       ` pte-highmem-5 Andrea Arcangeli
2002-01-24 15:35                         ` pte-highmem-5 Hugh Dickins
2002-01-22 19:29             ` pre4aa1 contig kmaps patch Hugh Dickins
2002-01-23 13:31               ` rwhron

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=20020116193521.C835@athlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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