linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: wyang <w90p710@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Linuxppc-dev@lists.ozlabs.org, Gavin Hu <gavin.hu.2010@gmail.com>
Subject: Re: [question] Can the execution of the atomtic operation instruction pair lwarx/stwcx be interrrupted by local HW interruptions?
Date: Tue, 07 Jan 2014 09:00:20 +0800	[thread overview]
Message-ID: <52CB51A4.7080303@gmail.com> (raw)
In-Reply-To: <1389045939.11795.104.camel@snotra.buserror.net>


On 01/07/2014 06:05 AM, Scott Wood wrote:
> On Mon, 2014-01-06 at 13:27 +0800, wyang wrote:
>> On 01/06/2014 11:41 AM, Gavin Hu wrote:
>>
>>> Thanks your response.  :)
>>> But that means that these optimitive operations like atomic_add()
>>> aren't optimitive actully in PPC architecture, right? Becuase they
>>> can be interrupted by loacl HW interrupts. Theoretically, the ISR
>>> also can access the atomic gloable variable.
>>>
>> Nope, my understand is that if you wanna sync kernel primitive code
>> with ISR, you have responsibility to disable local interrupts.
>> atomic_add does not guarantee to handle such case.
> atomic_add() and other atomics do handle that case.  Interrupts are not
> disabled, but there's a stwcx. in the interrupt return code to make sure
> the reservation gets cleared.

Yeah, Can you provide more detail info about why they can handle that 
case? The following is my understand:

Let us assume that there is a atomic global variable(var_a) and its 
initial value is 0.

The kernel attempts to execute atomic_add(1, var_a), after lwarx a async 
interrupt happens, and the ISR also accesses "var_a" variable and 
executes atomic_add.

static __inline__ void atomic_add(int a, atomic_t *v)
{
     int t;

     __asm__ __volatile__(
"1:    lwarx    %0,0,%3        # atomic_add\n\
----------------------------------  <----------- interrupt 
happens------->        ISR also operates this global variable "var_a" 
such as also executing atomic_add(1, var_a). so the
               var_a would is 1.
     add    %0,%2,%0\n"
     PPC405_ERR77(0,%3)
"    stwcx.    %0,0,%3 \n\ <----- After interrupt code returns, the 
reservation is cleared. so CR0 is not equal to 0, and then jump the 1 
label. the var_a will be 2.
     bne-    1b"
     : "=&r" (t), "+m" (v->counter)
     : "r" (a), "r" (&v->counter)
     : "cc");
}

So the value of var_a is 2 rather than 1. Thats why i said that 
atomic_add does not handle such case. If I miss something, please 
correct me.:-)

Wei
>
> -Scott
>
>
>

  reply	other threads:[~2014-01-07  1:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  5:41 [question] Can the execution of the atomtic operation instruction pair lwarx/stwcx be interrrupted by local HW interruptions? Gavin Hu
2013-12-30  1:54 ` wyang
2014-01-06  3:41   ` Gavin Hu
2014-01-06  5:27     ` wyang
2014-01-06  5:51       ` Gavin Hu
2014-01-06  6:24       ` Gavin Hu
2014-01-06  6:42         ` wyang
2014-01-06 22:05       ` Scott Wood
2014-01-07  1:00         ` wyang [this message]
2014-01-07  6:35           ` Scott Wood
2014-01-07  7:22             ` wyang
2014-01-07  8:01               ` Scott Wood

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=52CB51A4.7080303@gmail.com \
    --to=w90p710@gmail.com \
    --cc=Linuxppc-dev@lists.ozlabs.org \
    --cc=gavin.hu.2010@gmail.com \
    --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).