From: Scott Wood <scottwood@freescale.com>
To: "Arshad, Farrukh" <Farrukh_Arshad@mentor.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Problem in getting shared memory access on P1022RDK
Date: Tue, 3 Jan 2012 11:10:29 -0600 [thread overview]
Message-ID: <4F033685.6000509@freescale.com> (raw)
In-Reply-To: <93CD5F41FDBC6042A6B449764F3B35CC050CCA80@EU-MBX-03.mgc.mentorg.com>
On 01/03/2012 03:42 AM, Arshad, Farrukh wrote:
> Adding more to it,
>
>
>
> When I write from Core 1 on the shared memory region it is visible at
> Core 0 and it can read what I have written from Core 1 but when I write
> from Core 0 on this shared memory it is not visible on Core 1.
Is the memory mapped coherent on both cores?
-Scott
next prev parent reply other threads:[~2012-01-03 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 19:10 Problem in getting shared memory access on P1022RDK Arshad, Farrukh
2012-01-03 9:42 ` Arshad, Farrukh
2012-01-03 17:10 ` Scott Wood [this message]
2012-01-04 6:49 ` Arshad, Farrukh
2012-01-05 2:09 ` tiejun.chen
2012-01-05 5:46 ` Arshad, Farrukh
2012-01-11 15:52 ` Arshad, Farrukh
2012-01-12 8:09 ` tiejun.chen
2012-01-25 11:04 ` Arshad, Farrukh
2012-01-29 3:15 ` tiejun.chen
2012-01-04 9:56 ` Arshad, Farrukh
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=4F033685.6000509@freescale.com \
--to=scottwood@freescale.com \
--cc=Farrukh_Arshad@mentor.com \
--cc=linuxppc-dev@lists.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).