linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: vinay hegde <thisismevinay@yahoo.co.in>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Differentiate between two e500 core (in mult-core e500)
Date: Wed, 31 Jan 2007 00:02:41 -0800 (PST)	[thread overview]
Message-ID: <90010.28006.qm@web8411.mail.in.yahoo.com> (raw)
In-Reply-To: <42D831B8-9452-48E1-B996-2E970EB9DC27@kernel.crashing.org>

Hi,

Actually, what I mean is, there are two independent L1
caches (one in first e500 core and other in second
e500 core) in mpc8572. Now, if I am running cache
test(POST) on mpc8572, I must somehow make sure that
it tests both the L1 caches. Generally, earlier there
used to be one e500 core, one L1 cache and hence cache
test does not need to query whether it is testing L1
of first core or L1 of second.

So, how to make sure that I am testing L1 caches on
_both_ the e500 cores?

Thanks,
Vinay.

--- Kumar Gala <galak@kernel.crashing.org> wrote:

> 
> On Jan 30, 2007, at 10:58 PM, vinay hegde wrote:
> 
> > Hi,
> >
> > Sorry for the repeat mail on this, I forgot to ask
> the
> > question;-)
> >
> > If anybody knows how to differentiate one e500
> core
> > from another (in multi-core proc's), please post a
> > message.
> 
> Do you mean some software ID to know which core you
> are running on?
> 
> If so the PIR should be used for this purpose.
> 
> - k
> 
> > --- vinay hegde <thisismevinay@yahoo.co.in> wrote:
> >
> >> Hi,
> >>
> >> I have a need to write a POST sort of a test to
> test
> >> L1 data/inst cache residing on each of the e500
> v2
> >> multi-core seperately (for a network hardware).
> This
> >> is because multicore e500 has seperate L1 caches
> and
> >> shared L2 cache.
> >>
> >> This is for mpc8572. I learnt from this list that
> >> mpc8572 isn't out yet, but thought that
> >> differentiating between e500 mult-cores has
> nothing
> >> to
> >> do with mpc8572.
> >>
> >> Please let me know if you have any inputs.
> >>
> >> Thanks,
> >> Vinay.
> >>
> >>
> >>
> >>
> >
>
______________________________________________________________________
> 
> > ______________
> >> Expecting? Get great news right away with email
> >> Auto-Check.
> >> Try the Yahoo! Mail Beta.
> >>
> >
>
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
> >>
> >> _______________________________________________
> >> Linuxppc-embedded mailing list
> >> Linuxppc-embedded@ozlabs.org
> >>
> >
>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >>
> >
> >
> >
> >
> >
>
______________________________________________________________________
> 
> > ______________
> > Don't get soaked.  Take a quick peak at the
> forecast
> > with the Yahoo! Search weather shortcut.
> >
> http://tools.search.yahoo.com/shortcuts/#loc_weather
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> >
>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 



 
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time 
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news

  reply	other threads:[~2007-01-31  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31  4:46 Differentiate between two e500 core (in mult-core e500) vinay hegde
2007-01-31  4:58 ` vinay hegde
2007-01-31  6:45   ` Kumar Gala
2007-01-31  8:02     ` vinay hegde [this message]
2007-01-31 14:37       ` Kumar Gala
2007-02-01  4:14         ` vinay hegde
2007-02-01 17:14           ` Wang Haiying-r54964

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=90010.28006.qm@web8411.mail.in.yahoo.com \
    --to=thisismevinay@yahoo.co.in \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).