From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: Adam Kiepul <Adam_Kiepul@pmc-sierra.com>,
MAKE FUN PRANK CALLS <linux-mips@linux-mips.org>
Subject: Re: RM7k cache_flush_sigtramp
Date: Fri, 01 Aug 2003 08:40:14 +0800 [thread overview]
Message-ID: <3F29B6EE.5070207@ict.ac.cn> (raw)
In-Reply-To: <9DFF23E1E33391449FDC324526D1F259017DF087@SJC1EXM02>
Adam Kiepul wrote:
>Hi,
>
>If this is just to ensure the I Cache coherency for modified code then the following should be sufficient:
>
>cache Hit_Writeback_D, offset(base_register)
>cache Hit_Invalidate_I, offset(base_register)
>
>
Current linux code does exactly this. But I was seeing all kinds of
faults occuring around the
sigreturn point on the stack without a sync? And a sync does greatly
improve the stablity.
>The ordering does matter however since the Hit_Invalidate_I makes sure the write buffer is flushed.
>
>Kind Regards,
>
>_______________________________
>
>Adam Kiepul
>Sr. Applications Engineer
>
>PMC-Sierra, Microprocessor Division
>Mission Towers One
>3975 Freedom Circle
>Santa Clara, CA 95054, USA
>Direct: 408 239 8124
>Fax: 408 492 9462
>
>
>
>-----Original Message-----
>From: Ralf Baechle [mailto:ralf@linux-mips.org]
>Sent: Thursday, July 31, 2003 4:47 AM
>To: Fuxin Zhang
>Cc: MAKE FUN PRANK CALLS
>Subject: Re: RM7k cache_flush_sigtramp
>
>
>On Thu, Jul 31, 2003 at 09:56:08AM +0800, Fuxin Zhang wrote:
>
>
>>Date: Thu, 31 Jul 2003 09:56:08 +0800
>>From: Fuxin Zhang <fxzhang@ict.ac.cn>
>>To: MAKE FUN PRANK CALLS <linux-mips@linux-mips.org>
>>
>>
> ^^^^^^^^^^^^^^^^^^^^
>
>Funny name for the list :-)
>
>
>
>>r4k_cache_flush_sigtrap seems not enough for RM7000 cpus because
>>there is a writebuffer between L1 dcache & L2 cache,so the written back
>>block may not be seen by icache. This small patch fixes crashes of my
>>Xserver on ev64240.
>>
>>
>
>It would seem a similar fix is also needed in other places then?
>
> Ralf
>
>
>
>
next prev parent reply other threads:[~2003-08-01 0:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 16:50 RM7k cache_flush_sigtramp Adam Kiepul
2003-08-01 0:40 ` Fuxin Zhang [this message]
2003-08-01 3:01 ` Ralf Baechle
2003-08-01 4:59 ` Fuxin Zhang
2003-08-01 7:51 ` Dominic Sweetman
2003-08-01 7:51 ` Dominic Sweetman
2003-08-01 9:26 ` Ralf Baechle
2003-08-01 14:18 ` Fuxin Zhang
2003-08-02 17:02 ` Ralf Baechle
2003-08-04 8:45 ` Dominic Sweetman
2003-08-04 11:51 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2003-08-01 15:42 Adam Kiepul
2003-08-04 3:38 ` Fuxin Zhang
2003-08-06 11:00 ` Fuxin Zhang
2003-08-06 11:55 ` Ralf Baechle
2003-08-06 12:52 ` Fuxin Zhang
2003-08-06 14:45 ` Ralf Baechle
2003-08-06 15:04 ` Fuxin Zhang
2003-08-06 22:30 ` Ralf Baechle
2003-07-31 1:56 Fuxin Zhang
2003-07-31 11:46 ` Ralf Baechle
2003-07-31 12:57 ` Fuxin Zhang
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=3F29B6EE.5070207@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=Adam_Kiepul@pmc-sierra.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 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.