From: Joe George <joeg@clearcore.net>
To: Pete Popov <ppopov@mvista.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips <linux-mips@oss.sgi.com>
Subject: Re: PATCH
Date: Tue, 16 Jul 2002 11:43:33 -0600 [thread overview]
Message-ID: <3D345B45.50001@clearcore.net> (raw)
In-Reply-To: 1026832557.3552.3.camel@adsl.pacbell.net
I'll disagree with both of you so I may learn from the flames. :-)
First it's true the patch wasn't formatted for oss and should have
been rejected on that basis. At least my patches would be. :)
But Vivien Chappelier said it fixed his X server problem in mips64.
CONFIG_64BIT_PHYS_ADDR is applicable to both 36 and 64
bit code, I think.
So the crux of my question is, if an unsigned long long pte is
and'ed with an unsigned long PAGE_CHG_MASK what happens
to the upper 32 bits of pte. On a 64 bit processor is PAGE_CHG_MASK
sign extended so everything is fine, or does it zero the upper
32 bits?
Joe
Pete Popov wrote:
> On Tue, 2002-07-16 at 08:07, Ralf Baechle wrote:
>
>>On Mon, Jul 15, 2002 at 03:29:10PM -0700, Pete Popov wrote:
>>
>>
>>>--- include/asm-mips/pgtable.h.old Fri Jul 12 17:25:19 2002
>>>+++ include/asm-mips/pgtable.h Fri Jul 12 17:25:36 2002
>>>@@ -332,7 +332,9 @@
>>>
>>> static inline pte_t pte_modify(pte_t pte, pgprot_t newprot)
>>> {
>>>- return __pte(((pte).pte_low & _PAGE_CHG_MASK) | pgprot_val(newprot));
>>>+ pte.pte_low &= _PAGE_CHG_MASK;
>>>+ pte.pte_low |= pgprot_val(newprot);
>>>+ return pte;
>>> }
>>>
>>This patch certainly doesn't apply to oss. Seems somebody did copy all
>>the x86 pte_t and stuff into your tree without too much thinking ...
>>
>
> That's right, I forgot you don't have the 36 bit code that uses pte_low
> and pte_high.
>
> Pete
>
next prev parent reply other threads:[~2002-07-16 17:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 22:29 PATCH Pete Popov
2002-07-16 15:07 ` PATCH Ralf Baechle
2002-07-16 15:15 ` PATCH Pete Popov
2002-07-16 17:43 ` Joe George [this message]
2002-07-16 18:00 ` PATCH Pete Popov
2002-07-17 0:29 ` PATCH Vivien Chappelier
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 4:50 PATCH Pete Popov
2002-12-14 4:52 PATCH Pete Popov
2002-12-17 22:29 ` PATCH Greg Lindahl
2002-12-17 22:40 ` PATCH Pete Popov
2002-12-17 23:24 ` PATCH Alan Cox
2002-12-17 22:51 ` PATCH Pete Popov
2002-12-17 22:59 ` PATCH Greg Lindahl
2002-12-20 20:43 ` PATCH James Simmons
2002-12-20 20:59 ` PATCH Pete Popov
2002-12-21 20:39 ` PATCH James Simmons
2004-10-10 5:31 PATCH Pete Popov
2004-10-10 7:17 PATCH Pete Popov
2004-10-10 17:17 PATCH Pete Popov
2004-10-10 18:01 ` PATCH Geert Uytterhoeven
2004-10-10 19:11 ` PATCH Maciej W. Rozycki
2004-10-10 22:50 ` PATCH Pete Popov
2004-10-11 0:25 ` PATCH Maciej W. Rozycki
2004-10-11 0:39 ` PATCH Pete Popov
2004-10-10 19:33 ` PATCH Matt Porter
2004-10-10 22:52 ` PATCH Pete Popov
2004-10-10 23:41 ` PATCH Pete Popov
2004-10-10 23:43 PATCH Pete Popov
2004-10-11 0:01 PATCH Pete Popov
2004-10-11 0:32 ` PATCH Maciej W. Rozycki
2004-10-11 0:47 ` PATCH Pete Popov
2004-10-11 7:55 ` PATCH Pete Popov
2004-10-11 10:32 ` PATCH Christoph Hellwig
2004-10-11 17:07 ` PATCH Pete Popov
2004-10-11 13:53 ` PATCH Atsushi Nemoto
2004-10-11 16:33 ` PATCH Pete Popov
2004-10-11 18:04 ` PATCH Pete Popov
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=3D345B45.50001@clearcore.net \
--to=joeg@clearcore.net \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.com \
--cc=ralf@oss.sgi.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