Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH] fix parisc runtime hangs wrt pa_tlb_lock
Date: Wed, 17 Jun 2009 09:26:05 +0200	[thread overview]
Message-ID: <4A389A8D.2010806@gmx.de> (raw)
In-Reply-To: <20090617025529.GA19032@bombadil.infradead.org>

On 06/17/2009 04:55 AM, Kyle McMartin wrote:
> On Tue, Jun 16, 2009 at 10:51:48PM +0200, Helge Deller wrote:
>> On 06/15/2009 01:20 AM, John David Anglin wrote:
>>> I am convinced that interrupts need to be disabled on SMP kernels to
>>> prevent deadlock.  On UP kernels, I am not convinced that anything bad
>>> happens if we do a tlb purge while handling an interrupt since we don't
>>> have to worry about preventing bus conflicts.  The UP code can't
>>> deadlock.  I'm thinking that we can stay with disabling preemption.
>> Dave is right and it took me long to understand his point...
>> I continued testing and we can simply just disable preemption for UP
>> kernels and use an irq-safe spinlock for SMP kernels.
>>
>> Below is the latest and greatest patch which fixes this bug.
>> Run-tested onUP kernels and compile-tested on SMP kernels.
>>
>
> Ugh, I'd really prefer it if we just took the irq disable and enable hit
> on UP by making the codepaths the same... Is that ok with you or?

You mean to use the irq-safe spinlocking path for SMP _and_ UP?
Yes, that would be ok for me too. We just thought why we should try to save
some cycles on UP if possible, as the UP-kernel often is used on
slower machines where it would be beneficial for them...

If yes, do you want me to send an updated patch?

Helge

      reply	other threads:[~2009-06-17  7:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 20:13 [PATCH, RFC] fix parisc runtime hangs wrt pa_tlb_lock Helge Deller
2009-05-23 15:26 ` John David Anglin
2009-05-23 15:34   ` John David Anglin
2009-05-23 19:34     ` Helge Deller
2009-05-23 20:03       ` John David Anglin
2009-05-23 21:53 ` John David Anglin
2009-05-28  1:50 ` John David Anglin
2009-06-06 21:25   ` Helge Deller
2009-06-14 22:05     ` Helge Deller
2009-06-14 23:20       ` John David Anglin
2009-06-16 20:51         ` [PATCH] " Helge Deller
2009-06-17  2:55           ` Kyle McMartin
2009-06-17  7:26             ` Helge Deller [this message]

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=4A389A8D.2010806@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.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