From: Alexandr Andreev <andreev@niisi.msk.ru>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: 3 questions about linux-2.4.18 and R3000
Date: Mon, 27 May 2002 17:13:33 -0400 [thread overview]
Message-ID: <3CF2A17D.6050207@niisi.msk.ru> (raw)
In-Reply-To: 3CEEAC5F.6010802@mvista.com
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Jun Sun wrote:
> I took a look of the arch_get_unmapped_area(), and it looks fine to me.
>
> Can you try the following changes and let me know what happens?
>
> 1) change COLOUR_ALIGN
> #define COLOUR_ALIGN(addr,pgoff) addr
OK, It works for me.
>
> We have been using gcc 2.9.5 and binutils 2.10.x for R3000 CPUs for
> quite a while with no problems. It seems newer gcc and binutiles are
> fine too.
>
I understand, but is there any __official__ recommended versions of these
utils? http://oss.sgi.com/mips/mips-howto.html is out-of-date :(
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 990 bytes --]
diff -pru linux_2_4_18_orig/arch/mips/mm/tlb-r3k.c linux_2_4_18/arch/mips/mm/tlb-r3k.c
--- linux_2_4_18_orig/arch/mips/mm/tlb-r3k.c Fri Apr 26 07:50:07 2002
+++ linux_2_4_18/arch/mips/mm/tlb-r3k.c Mon May 27 16:36:14 2002
@@ -118,7 +118,7 @@ void local_flush_tlb_range(struct mm_str
void local_flush_tlb_page(struct vm_area_struct *vma, unsigned long page)
{
- if (!vma || vma->vm_mm->context != 0) {
+ if (vma && vma->vm_mm->context) {
unsigned long flags;
int oldpid, newpid, idx;
diff -pru linux_2_4_18_orig/arch/mips/mm/tlb-r4k.c linux_2_4_18/arch/mips/mm/tlb-r4k.c
--- linux_2_4_18_orig/arch/mips/mm/tlb-r4k.c Fri Apr 26 07:50:07 2002
+++ linux_2_4_18/arch/mips/mm/tlb-r4k.c Mon May 27 16:31:45 2002
@@ -140,7 +140,7 @@ void local_flush_tlb_range(struct mm_str
void local_flush_tlb_page(struct vm_area_struct *vma, unsigned long page)
{
- if (!vma || vma->vm_mm->context != 0) {
+ if (vma && vma->vm_mm->context) {
unsigned long flags;
int oldpid, newpid, idx;
next prev parent reply other threads:[~2002-05-27 13:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 22:16 3 questions about linux-2.4.18 and R3000 Alexandr Andreev
2002-05-24 21:10 ` Jun Sun
2002-05-27 21:13 ` Alexandr Andreev [this message]
2002-05-28 17:15 ` Jun Sun
2002-05-30 0:18 ` Alexandr Andreev
2002-05-31 9:43 ` Gleb O. Raiko
2002-06-03 8:55 ` Ralf Baechle
2002-06-03 18:30 ` Maciej W. Rozycki
2002-06-03 22:40 ` Ralf Baechle
2002-06-03 23:01 ` Thiemo Seufer
2002-06-03 23:04 ` Ralf Baechle
2002-06-03 23:11 ` Thiemo Seufer
2002-06-03 23:15 ` Ralf Baechle
2002-06-03 23:53 ` Thiemo Seufer
2002-06-04 17:41 ` nick
2002-06-05 22:37 ` Thiemo Seufer
2002-06-05 23:50 ` Ilya Volynets
2002-06-06 23:54 ` Thiemo Seufer
2002-06-04 14:39 ` Maciej W. Rozycki
2002-06-04 14:37 ` Maciej W. Rozycki
2002-06-05 22:38 ` Thiemo Seufer
2002-06-04 14:34 ` Maciej W. Rozycki
2002-06-04 11:31 ` Gleb O. Raiko
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=3CF2A17D.6050207@niisi.msk.ru \
--to=andreev@niisi.msk.ru \
--cc=jsun@mvista.com \
--cc=linux-mips@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