From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-mips@linux-mips.org
Cc: Bob Breuer <bbreuer@righthandtech.com>,
Jordan Crouse <jordan.crouse@amd.com>,
Konstantin Baidarov <kbaidarov@ru.mvista.com>
Subject: Re: [PATCH] Fix swap entry for MIPS32 36-bit physical address
Date: Sat, 08 Apr 2006 02:04:49 +0400 [thread overview]
Message-ID: <4436E201.4090409@ru.mvista.com> (raw)
In-Reply-To: <4436D793.6080701@ru.mvista.com>
Hello.
Sergei Shtylyov wrote:
> With 64-bit physical address enabled, 'swapon' was causing kernel oops
> on Alchemy CPUs (MIPS32) 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 harware 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.
Hm, just noticed that this fix renders set_pte()/pte_clear() erroneous by
reusing _PAGE_GLOBAL (bit 0) in pte_low field of pte_t -- pte_high should have
been used instead or those macros fixed. So, refrain from committing as yet...
WBR, Sergei
> Signed-off-by: Konstantin Baydarov <kbaidarov@ru.mvista.com>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> ------------------------------------------------------------------------
>
> diff --git a/include/asm-mips/pgtable-32.h b/include/asm-mips/pgtable-32.h
> index 4d6bc45..b0ad112 100644
> --- a/include/asm-mips/pgtable-32.h
> +++ b/include/asm-mips/pgtable-32.h
> @@ -190,11 +190,27 @@ pfn_pte(unsigned long pfn, pgprot_t prot
>
> #else
>
> +#if defined(CONFIG_64BIT_PHYS_ADDR) && defined(CONFIG_CPU_MIPS32)
> +/*
> + * For 36-bit physical address we store swap entry in pte_low and 0 in pte_high,
> + * which gives us 25 bits available for the offset...
> + */
> +#define __swp_type(x) ((x).val & 0x1f)
> +#define __swp_offset(x) ((((x).val >> 5) & 0x1) | \
> + (((x).val >> 6) & 0xe) | \
> + (((x).val >> 11) << 4))
> +#define __swp_entry(type,offset) \
> + ((swp_entry_t) { ((type) & 0x1f) | \
> + (((offset) & 0x1) << 5) | \
> + (((offset) & 0xe) << 6) | \
> + (((offset) >> 4 ) << 11) })
> +#else
> /* Swap entries must have VALID and GLOBAL bits cleared. */
> #define __swp_type(x) (((x).val >> 8) & 0x1f)
> #define __swp_offset(x) ((x).val >> 13)
> #define __swp_entry(type,offset) \
> ((swp_entry_t) { ((type) << 8) | ((offset) << 13) })
> +#endif /* defined(CONFIG_64BIT_PHYS_ADDR) && defined(CONFIG_CPU_MIPS32) */
>
> /*
> * Bits 0, 1, 2, 7 and 8 are taken, split up the 27 bits of offset
>
>
next prev parent reply other threads:[~2006-04-07 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:20 swapon failure with au1550 Bob Breuer
2005-02-22 22:20 ` Bob Breuer
2006-04-05 13:45 ` [PATCH] Fix swap entry for MIPS32 36-bit physical address Sergei Shtylyov
2006-04-07 19:52 ` Sergei Shtylyov
2006-04-07 21:19 ` Sergei Shtylyov
2006-04-07 21:19 ` Sergei Shtylyov
2006-04-07 21:20 ` Sergei Shtylyov
2006-04-07 22:04 ` Sergei Shtylyov [this message]
2006-04-08 9:51 ` [PATCH] Fix swap entry for MIPS32 with " Sergei Shtylyov
2006-04-08 3:56 ` [PATCH] Enable 36-bit physical address on MIPS32R2 also Sergei Shtylyov
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=4436E201.4090409@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bbreuer@righthandtech.com \
--cc=jordan.crouse@amd.com \
--cc=kbaidarov@ru.mvista.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox