linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michel Danzer <michdaen@iiic.ethz.ch>, linuxppc-dev@lists.linuxppc.org
Subject: Re: patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128
Date: Wed, 8 Mar 2000 22:11:31 -0500	[thread overview]
Message-ID: <00030822191300.00546@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0003060013070.30614-100000@idd-01.imbc.gr>


Hi Kostas,

I took one more look at the cache flush code for what the loader loads and
would like to make one small change.  The reason is as follows:  if the object
is loaded at an address whose last 5 bits are not 0 (say they are 30 decimal for
the sake of argument and the size is 8 bytes really two cache lines should be
flushed and not just one.  The way it was previously (after your change to
ppc_flush_icache) only 1 cache line was being flushed in this case.

    if(read(fd,ptr,size)!=size)
	FatalError("\n_LoaderFileToMem() read() failed: %s\n",strerror(errno));

#if defined(linux) && defined(__powerpc__)
 {
 int i;
 for (i = 0; i < size; i += 32)
    ppc_flush_icache(ptr+i);

 /* add this line to make sure any partial ending cache line gets flushed too */
 ppc_flush_icache(ptr+size-1)
 }
#endif

#ifdef DEBUGMEM
    ErrorF("=%lx\n",ptr);
#endif


Thanks,

Kevin


--
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario  N6A-3K7  CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-03-09  3:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0003041753480.1870-100000@idd-01.imbc.gr>
2000-03-04 18:55 ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-05 13:42   ` Michel Dänzer
2000-03-05 16:43     ` Kostas Gewrgiou
2000-03-05 16:58       ` Kevin B. Hendricks
2000-03-05 21:04         ` Kostas Gewrgiou
2000-03-05 21:20           ` Geert Uytterhoeven
2000-03-05 22:25             ` Kostas Gewrgiou
2000-03-06  6:54               ` Geert Uytterhoeven
2000-03-09  3:11               ` Kevin Hendricks [this message]
     [not found]                 ` <38C7A016.8C2ED4C8@iiic.ethz.ch>
     [not found]                   ` <v03110701b562ab7246aa@[129.100.29.243]>
2000-03-10 15:33                     ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 Kevin B. Hendricks
2000-03-10 17:25                       ` Kostas Gewrgiou
2000-03-10 18:17                         ` Kevin B. Hendricks
2000-03-10 19:21                           ` Michael Schmitz
2000-03-10 23:54                             ` patch to get latest XFree 4.0 snapshot (xf3918) to work on ppcwithr128 Michel Dänzer
2000-03-11 14:50                               ` Michael Schmitz
2000-03-12 14:52                                 ` patch to get latest XFree 4.0 snapshot (xf3918) to work onppcwithr128 Michel Dänzer
2000-03-10 19:43                       ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwithr128 David A. Gatwood
2000-03-11 14:38               ` Help! Getting aty128fb.c to work with newest sawtooth machines Kevin Hendricks
2000-03-13  9:19                 ` Kostas Gewrgiou
2000-03-14  1:12               ` patch to get latest XFree 4.0 snapshot (xf3918) to work on pp cwith r128 Kevin Hendricks
2000-03-09  2:41           ` Kevin Hendricks
2000-03-09 11:04             ` Gabriel Paubert
     [not found] <v03110700b562a526cc14@[129.100.29.243]>
2000-03-09 16:31 ` David A. Gatwood
2000-03-10 12:48   ` Gabriel Paubert
2000-03-10 13:14     ` Benjamin Herrenschmidt
2000-03-10 19:39     ` David A. Gatwood
2000-03-11 15:39       ` Gabriel Paubert

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=00030822191300.00546@localhost.localdomain \
    --to=khendricks@ivey.uwo.ca \
    --cc=geert@linux-m68k.org \
    --cc=gewrgiou@imbc.gr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=michdaen@iiic.ethz.ch \
    /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;
as well as URLs for NNTP newsgroup(s).