All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartvig Ekner <hartvig@ekner.info>
To: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Aliasing in pgtable-bits.h (CONFIG_64BIT_PHYS_ADDR)
Date: Tue, 08 Apr 2003 09:06:24 +0200	[thread overview]
Message-ID: <3E9274F0.227008F7@ekner.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

From pgtable-bits.h:

#if defined(CONFIG_CPU_MIPS32) && defined(CONFIG_64BIT_PHYS_ADDR)

#define _PAGE_PRESENT               (1<<6)  /* implemented in software */
#define _PAGE_READ                  (1<<7)  /* implemented in software */
#define _PAGE_WRITE                 (1<<8)  /* implemented in software */
#define _PAGE_ACCESSED              (1<<9)  /* implemented in software */
#define _PAGE_MODIFIED              (1<<10) /* implemented in software */

#define _PAGE_R4KBUG                (1<<0)  /* workaround for r4k bug  */
#define _PAGE_GLOBAL                (1<<0)

Is the aliasing between R4KBUG & GLOBAL intentional? This is the only CONFIG case where it
is done. Superficially, I can't see R4KBUG used anywhere, so maybe it doesn't matter. But
if R4KBUG truly isn't used, why not consider removing it entirely from all PTE layouts?

/Hartvig


[-- Attachment #2: Type: text/html, Size: 1807 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Hartvig Ekner <hartvig@ekner.info>
To: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Aliasing in pgtable-bits.h (CONFIG_64BIT_PHYS_ADDR)
Date: Tue, 08 Apr 2003 09:06:24 +0200	[thread overview]
Message-ID: <3E9274F0.227008F7@ekner.info> (raw)
Message-ID: <20030408070624.3G7BMVayYR4VbKh2IzmyVXT6khInMQIXGbzyFYXQ4Bw@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2003-04-08  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  7:06 Hartvig Ekner [this message]
2003-04-08  7:06 ` Aliasing in pgtable-bits.h (CONFIG_64BIT_PHYS_ADDR) Hartvig Ekner
2003-04-08 10:32 ` Juan Quintela
2003-04-08 21:48   ` Ralf Baechle
2003-04-08 21:47 ` Ralf Baechle
2003-04-09 10:12   ` Maciej W. Rozycki

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=3E9274F0.227008F7@ekner.info \
    --to=hartvig@ekner.info \
    --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 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.