From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-mips@linux-mips.org
Cc: Ralf Baechle <ralf@linux-mips.org>,
Jordan Crouse <jordan.crouse@amd.com>
Subject: Re: [MIPS] Fix swap entry for MIPS32 36-bit physical address
Date: Sat, 27 May 2006 19:58:03 +0400 [thread overview]
Message-ID: <4478770B.9080301@ru.mvista.com> (raw)
In-Reply-To: <S8133863AbWEZXEn/20060526230443Z+689@ftp.linux-mips.org>
Hello.
linux-mips@linux-mips.org wrote:
> Author: Sergei Shtylyov <sshtylyov@ru.mvista.com> Wed Apr 5 00:24:40 2006 +0400
> Comitter: Ralf Baechle <ralf@linux-mips.org> Sat May 27 00:01:23 2006 +0100
> Commit: f826429f5ad38f40b96ff587cd44def138f99f3a
> Gitweb: http://www.linux-mips.org/g/linux/f826429f
> Branch: master
>
> With 64-bit physical address enabled, 'swapon' was causing kernel oops
> on Alchemy CPUs (MIPS32R1) because of the swap entry type field
> corrupting the _PAGE_FILE bit in pte_low. So, change layout of the
> swap entry to use all bits except _PAGE_PRESENT and _PAGE_FILE (the
> hardware protection bits are loaded from pte_high which should be
> cleared by __swp_entry_to_pte() macro) -- which gives 25 bits for the
> swap entry offset. Additionally, PTEs in MIPS32R2 should have the same
> layout for 64-bit physical address case as in MIPS32R1, according to
> the architecture manuals -- so, fix the #ifdef's.
>
> Signed-off-by: Konstantin Baydarov <kbaidarov@ru.mvista.com>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
>
> ---
>
> include/asm-mips/pgtable-32.h | 22 +++++++++++++++++++---
> include/asm-mips/pgtable-bits.h | 2 +-
> 2 files changed, 20 insertions(+), 4 deletions(-)
Alas, Ralf have finally managed to commit the wrong patch -- both outdated
and error-prone because it reuses _PAGE_GLOBAL which is bad for set_pte() and
pte_clear() and probably for the CPU itself since it ANDs G-bit of both the
even and odd PTEs to decide whether to compare ASID or not when doing TLB
lookups. I wonder whether this commit can be undone (it's still the most
recent one) or should I compose an incremental patch?
WBR, Sergei
parent reply other threads:[~2006-05-27 15:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <S8133863AbWEZXEn/20060526230443Z+689@ftp.linux-mips.org>]
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=4478770B.9080301@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=jordan.crouse@amd.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.