public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH -rt] irqd starvation on SMP by a single process?
Date: Fri, 12 May 2006 09:19:26 -0400	[thread overview]
Message-ID: <44648B5E.80105@compro.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0605120902460.30264@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Fri, 12 May 2006, Mark Hounschell wrote:
> 
>>> Mark, does this fix the problem?
>>>
>>> 	Ingo
>>>
>>> Index: linux-rt.q/drivers/net/3c59x.c
>>> ===================================================================
>>> --- linux-rt.q.orig/drivers/net/3c59x.c
>>> +++ linux-rt.q/drivers/net/3c59x.c
>>> @@ -1897,7 +1897,8 @@ vortex_timer(unsigned long data)
>>>
>>>  	if (vp->medialock)
>>>  		goto leave_media_alone;
>>> -	disable_irq(dev->irq);
>>> +	/* hack! */
>>> +	disable_irq_nosync(dev->irq);
>>>  	old_window = ioread16(ioaddr + EL3_CMD) >> 13;
>>>  	EL3WINDOW(4);
>>>  	media_status = ioread16(ioaddr + Wn4_Media);
>>>
>> Yes it does.
>>
> 
> 
> It fixes it for both "complete preemption" and "normal preemption"?
> 
> -- Steve
> 
> 

Nope, I still have the complete preemption problem. My box locked up
right away. Had to reboot it.

You guys know best but I think the problem the above patch fixes is
probably not related to my 'complete preemption' problem or the problem
reported by John. But my 'complete preemption' problem may certainly be
the same as Johns.

Mark

  parent reply	other threads:[~2006-05-12 13:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  2:43 [RFC][PATCH -rt] irqd starvation on SMP by a single process? john stultz
2006-05-12  5:50 ` Ingo Molnar
2006-05-12  7:59   ` Steven Rostedt
2006-05-12  8:10     ` Ingo Molnar
2006-05-12 11:39     ` Mark Hounschell
2006-05-12 11:56       ` Ingo Molnar
2006-05-12 11:59         ` Mark Hounschell
2006-05-12 12:53         ` Mark Hounschell
2006-05-12 13:03           ` Steven Rostedt
2006-05-12 13:06             ` Mark Hounschell
2006-05-12 13:19             ` Mark Hounschell [this message]
2006-05-12 17:47   ` john stultz
2006-05-12 18:04   ` john stultz
2006-05-12 19:16     ` Mark Hounschell
2006-05-12 20:04     ` Mark Hounschell
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12  4:22 Edward Killips

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=44648B5E.80105@compro.net \
    --to=markh@compro.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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