linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] [RFC] Emulate "lwsync" to run standard user land on e500 cores
Date: Sun, 27 Oct 2013 11:25:53 +0100	[thread overview]
Message-ID: <20131027102554.06B313811DD@gemini.denx.de> (raw)
In-Reply-To: <6BFC8EB0-1A75-41C3-985A-E3ED14846710@kernel.crashing.org>

Dear Kumar,

In message <6BFC8EB0-1A75-41C3-985A-E3ED14846710@kernel.crashing.org> you wrote:
> 
> Fair enough
> > 
> > I'm not too worried as long as we warn and account them.
>
> Than, I'd ask this be under a Kconfig option that is disabled by
> default.  Users should have to explicitly enable this so they know what
> they are doing.

Is this really worth the effort?  Under normal situations (users are
using a user space environment that has been properly buiult for the
processor variant they are using) nobody should ever run into this
situation.  It happens only if you are already doing something wrong -
like using user space that has not been built for an E500 core on such
a machine.

In this situation, it seems more useful to me if a "standard" kernel
just works with a "standard" user space environment, even if this
includes some performance penalty - which actually should be
neglibale.  In my tests (when running standard Debian for PPC on a
E500 only very few programs actually triggered this situation, and
none of them in a time-critical way.  I doubt I would even be able to
measure the performance impact.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"...all the  good  computer  designs  are  bootlegged;  the  formally
planned  products,  if  they  are built at all, are dogs!" - David E.
Lundstrom, "A Few Good Men From Univac", MIT Press, 1987

  parent reply	other threads:[~2013-10-27 10:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  7:38 [PATCH] [RFC] Emulate "lwsync" to run standard user land on e500 cores Wolfgang Denk
2013-10-18 16:38 ` Scott Wood
2013-10-18 18:50   ` Wolfgang Denk
2013-10-23  5:07 ` Kumar Gala
2013-10-23 10:15   ` Scott Wood
2013-10-24  4:06     ` Kumar Gala
2013-10-24  9:45       ` Benjamin Herrenschmidt
2013-10-24  9:55         ` Kumar Gala
2013-10-24 21:05           ` James Yang
2013-10-25  4:12             ` Kumar Gala
2013-10-25  4:49               ` Yang James-RA8135
2013-10-25  9:58                 ` David Laight
2013-10-25 13:02                   ` Benjamin Herrenschmidt
2013-10-26  7:26                     ` Kumar Gala
2013-10-25 15:13                   ` James Yang
2013-10-25 10:36           ` Scott Wood
2013-10-25 15:25             ` James Yang
2013-10-28 17:52               ` Scott Wood
2013-10-27 10:29             ` Wolfgang Denk
2013-10-27 10:25           ` Wolfgang Denk [this message]
2013-10-24 10:18       ` David Laight

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=20131027102554.06B313811DD@gemini.denx.de \
    --to=wd@denx.de \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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 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).