From: Michael Schnell <mschnell@lumino.de>
To: monstr@monstr.eu
Cc: microblaze-uclinux@itee.uq.edu.au,
LKML <linux-kernel@vger.kernel.org>,
John Williams <john.williams@petalogix.com>,
John Linn <John.Linn@xilinx.com>,
Stefan Asserhall <stefan.asserhall@xilinx.com>,
Goran Bilski <goran@xilinx.com>,
"Steven J. Magnani" <steve@digidescorp.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
sam@ravnborg.org, stephenn@xilinx.com,
Karen Whelan <karen.whelan@petalogix.com>,
Wendy Liang <wendy.liang@petalogix.com>
Subject: Re: Microblaze - The fist year
Date: Wed, 14 Apr 2010 09:53:28 +0200 [thread overview]
Message-ID: <4BC57478.3080902@lumino.de> (raw)
In-Reply-To: <4BC4713F.6030702@monstr.eu>
On 04/13/2010 03:27 PM, Michal Simek wrote:
>
> yes, futex is there. You can check it in
> arch/microblaze/include/asm/futex.h
Great ! I'll check how this is done.
>
>> Does Microblaze MMU Linux support SMP ?
>
> It is possible to connect several MicroBlazes but the problem is
> missing cache coherency modul. I hope that Xilinx will release any
> version which will support it.
> We haven't done any significant work to support it but it is expected
> solution which will happen.
Besides cache coherency, another problem might be doing FUTEX. here (I
suppose) SMP safe atomic user space operations are necessary. many
simple RISK (load/store-) CPUs don't provide these (new ARMs provide
"load-locked / store-conditional" on that behalf as an extension to the
load/store paradigm. I suppose these can be done in an SMP-safe way,
supposedly using the hardware that provides cache coherency).
-Michael
next prev parent reply other threads:[~2010-04-14 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 12:21 Microblaze - The fist year Michal Simek
2010-04-13 13:12 ` Michael Schnell
2010-04-13 13:27 ` Michal Simek
2010-04-14 7:53 ` Michael Schnell [this message]
2010-05-09 16:49 ` Bill Davidsen
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=4BC57478.3080902@lumino.de \
--to=mschnell@lumino.de \
--cc=John.Linn@xilinx.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=edgar.iglesias@gmail.com \
--cc=goran@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=karen.whelan@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@elte.hu \
--cc=monstr@monstr.eu \
--cc=sam@ravnborg.org \
--cc=stefan.asserhall@xilinx.com \
--cc=stephenn@xilinx.com \
--cc=steve@digidescorp.com \
--cc=torvalds@linux-foundation.org \
--cc=wendy.liang@petalogix.com \
/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.