From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Jim Hull" <jim.hull@hp.com>, parisc-linux@lists.parisc-linux.org
Cc: "Grant Grundler" <grundler@parisc-linux.org>
Subject: RE: [parisc-linux] Re: [parisc-linux-cvs] linux carlos
Date: Fri, 29 Aug 2003 17:59:53 +0200 [thread overview]
Message-ID: <3F4D78B0000005EE@ocpmta3.freegates.net> (raw)
>If you use fdc, fic, or pdc then they are broadcast to other
>processors, but fdce and fice are not.
Hi Jim and al,
I just noticed the two following loops:
flush_data_cache_local:
[...]
fdmanyloop: /* Loop if LOOP >= 2 */
ADDIB> -1,%r31,fdmanyloop /* Adjusted inner loop decr
*/
fdce 0(%sr1,%arg0)
fdce,m %arg1(%sr1,%arg0) /* Last fdce and addr adjust
*/
movb,tr %arg3,%r31,fdmanyloop /* Re-init inner loop count
*/
ADDIB<=,n -1,%arg2,fdsync /* Outer loop decr */
fdoneloop: /* Loop if LOOP = 1 */
ADDIB> -1,%arg2,fdoneloop /* Outer loop count decr
*/
fdce,m %arg1(%sr1,%arg0) /* Fdce for one loop */
fdsync:
syncdma
sync
mtsm %r22
bv %r0(%r2)
nop
.exit
.procend
[...]
flush_instruction_cache_local:
[...]
fimanyloop: /* Loop if LOOP >= 2 */
ADDIB> -1,%r31,fimanyloop /* Adjusted inner loop decr
*/
fice 0(%sr1,%arg0)
fice,m %arg1(%sr1,%arg0) /* Last fice and addr adjust
*/
movb,tr %arg3,%r31,fimanyloop /* Re-init inner loop count
*/
ADDIB<=,n -1,%arg2,fisync /* Outer loop decr */
fioneloop: /* Loop if LOOP = 1 */
ADDIB> -1,%arg2,fioneloop /* Outer loop count decr
*/
fice,m %arg1(%sr1,%arg0) /* Fice for one loop */
fisync:
sync
bv %r0(%r2)
nop
.exit
.procend
Do you think that could be there where the pb occurs?
Thanks for advise,
Joel
-------------------------------------------------------------------------
Tiscali ADSL, seulement 35 eur/mois et le modem est inclus...abonnez-vous!
http://reg.tiscali.be/default.asp?lg=fr
next reply other threads:[~2003-08-29 16:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 15:59 Joel Soete [this message]
2003-08-29 16:13 ` [parisc-linux] Re: [parisc-linux-cvs] linux carlos Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 16:08 Joel Soete
2003-08-28 16:34 ` Jim Hull
2003-08-29 7:27 ` Joel Soete
2003-08-28 7:04 Joel Soete
2003-08-28 15:12 ` Grant Grundler
2003-08-25 10:03 Joel Soete
2003-08-25 16:45 ` Grant Grundler
2003-08-25 16:50 ` James Bottomley
2003-08-25 19:19 ` Grant Grundler
2003-08-25 19:48 ` James Bottomley
2003-08-26 17:17 ` Carlos O'Donell
2003-08-26 17:54 ` Joel Soete
2003-08-23 15:54 Joel Soete
2003-08-23 19:28 ` Grant Grundler
2003-08-24 12:51 ` Joel Soete
2003-08-24 17:19 ` Grant Grundler
2003-08-25 17:26 ` Joel Soete
2003-08-28 6:08 ` Joel Soete
[not found] <20030820192919.0C20349401C@palinux.hppa>
2003-08-20 19:41 ` Carlos O'Donell
2003-08-21 6:21 ` Joel Soete
[not found] <20021104004626.651BC4829@dsl2.external.hp.com>
2002-11-04 0:58 ` Carlos O'Donell
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=3F4D78B0000005EE@ocpmta3.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=grundler@parisc-linux.org \
--cc=jim.hull@hp.com \
--cc=parisc-linux@lists.parisc-linux.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