From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
Dave Liu <r63238@freescale.com>,
Paul Mackerras <paulus@samba.org>,
Kumar Gala <galak@gate.crashing.org>
Subject: Re: fsl booke MM vs. SMP questions
Date: Tue, 22 May 2007 20:05:42 +1000 [thread overview]
Message-ID: <1179828342.32247.832.camel@localhost.localdomain> (raw)
In-Reply-To: <20070522100212.GA13225@iram.es>
On Tue, 2007-05-22 at 12:02 +0200, Gabriel Paubert wrote:
>
> Well, there should always be an stwcx. to clear reservation before
> any interrupt return. Otherwise you'll be able to cause hard to
> reproduce bugs in the interrupted code.
Well, that's the point. The BookE TLB refill exception is a very fast
path that doesn't use the normal interrupt return code path. It thus
needs to be careful about not leaving dangling reservations.
On some CPUs, there are also performance issues with leaving dangling
lwarx iirc but I don't have the details off the top of my mind.
Cheers,
Ben.
next prev parent reply other threads:[~2007-05-22 10:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 7:06 fsl booke MM vs. SMP questions Benjamin Herrenschmidt
[not found] ` <1179741447.3660.7.camel@localhost.localdomain>
[not found] ` <1179742083.32247.689.camel@localhost.localdomain>
2007-05-21 11:37 ` Dave Liu
2007-05-21 22:07 ` Benjamin Herrenschmidt
2007-05-22 3:09 ` Benjamin Herrenschmidt
2007-05-22 10:56 ` Dave Liu
2007-05-22 22:42 ` Benjamin Herrenschmidt
2007-05-23 2:38 ` Dave Liu
2007-05-23 3:08 ` Benjamin Herrenschmidt
2007-05-28 9:05 ` Liu Dave-r63238
2007-05-28 9:24 ` Benjamin Herrenschmidt
2007-05-28 9:37 ` Liu Dave-r63238
2007-05-28 10:00 ` Benjamin Herrenschmidt
2007-05-28 10:23 ` Gabriel Paubert
2007-05-28 10:28 ` Benjamin Herrenschmidt
2007-05-22 8:46 ` Gabriel Paubert
2007-05-22 9:14 ` Benjamin Herrenschmidt
2007-05-22 10:02 ` Gabriel Paubert
2007-05-22 10:05 ` Benjamin Herrenschmidt [this message]
2007-05-23 9:12 ` Gabriel Paubert
2007-05-22 3:03 ` Kumar Gala
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=1179828342.32247.832.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
--cc=paulus@samba.org \
--cc=r63238@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).