From: Deepak Saxena <dsaxena@plexity.net>
To: mingo@elte.hu
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
Manish Lachwani <mlachwani@mvista.com>
Subject: Re: [PATCH] Make MIPS udelay() preempt safe
Date: Mon, 19 Mar 2007 17:03:00 -0700 [thread overview]
Message-ID: <20070320000300.GA12123@plexity.net> (raw)
In-Reply-To: <20070319234945.GA11944@plexity.net>
Nevermind on this one. I just noticed that the original patch is not
needed.
~Deepak
On Mar 19 2007, at 16:49, Deepak Saxena was caught saying:
> Fix MIPS udelay to make is preempt safe under DEBUG_PREEMPT
>
> Signed-off-by: Manish Lachwani <mlachwani@mvista.com>
> Signed-off-by: Deepak Saxena <dsaxena@mvista.com>
>
> ---
>
> This needs to go into -rt patch set or directly into the MIPS tree.
> Applies cleanly to 2.6.21-rc4 and 2.6.21-rc3-rt0.
>
> include/asm-mips/delay.h | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6.18/include/asm-mips/delay.h
> ===================================================================
> --- linux-2.6.18.orig/include/asm-mips/delay.h
> +++ linux-2.6.18/include/asm-mips/delay.h
> @@ -79,7 +79,7 @@ static inline void __udelay(unsigned lon
> __delay(usecs);
> }
>
> -#define __udelay_val cpu_data[smp_processor_id()].udelay_val
> +#define __udelay_val cpu_data[raw_smp_processor_id()].udelay_val
>
> #define udelay(usecs) __udelay((usecs),__udelay_val)
>
>
> --
> Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
>
> In the end, they will not say, "those were dark times," they will ask
> "why were their poets silent?" - Bertolt Brecht
--
Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
In the end, they will not say, "those were dark times," they will ask
"why were their poets silent?" - Bertolt Brecht
next prev parent reply other threads:[~2007-03-20 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:49 [PATCH] Make MIPS udelay() preempt safe Deepak Saxena
2007-03-20 0:03 ` Deepak Saxena [this message]
2007-03-20 1:43 ` Atsushi Nemoto
2007-03-20 10:58 ` Ralf Baechle
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=20070320000300.GA12123@plexity.net \
--to=dsaxena@plexity.net \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=mlachwani@mvista.com \
--cc=ralf@linux-mips.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