public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: paulus@samba.org, jk@blackdown.de, akpm@osdl.org,
	oleg@tv-sign.ru, linux-kernel@vger.kernel.org,
	maneesh@in.ibm.com
Subject: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
Date: Wed, 04 May 2005 10:05:08 +1000	[thread overview]
Message-ID: <1115165108.7567.76.camel@gaston> (raw)
In-Reply-To: <20050503163916.30d64630.davem@davemloft.net>

On Tue, 2005-05-03 at 16:39 -0700, David S. Miller wrote:
> On Wed, 04 May 2005 09:44:53 +1000
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > Nothing prevents it ? well, I wouldn't be that optimistic :) The USB
> > stuff is a bit complex, it inlcudes doing DMAs, so manipulating the
> > iommu, dealing with URB queues (and thus allocating/releasing them)
> > etc... and especially in the context of xmon, that mean letting the
> > driver do a lot of these at any time whatever state the system is...
> 
> I think doing calls to the USB interrupt handler would work.
> I'm not being crazy :)

Maybe, but it will trigger all other USB drivers around and really
weird things might happen.. Oh well, I may give it a try one of
these days anyway. I could probably even do some hack to force the
OHCI to only service incoming interrupt URBs for input devices or
such things...

> But yeah we could do a micro-stack as well, but as you noted the
> transfer to/from the real USB HCI driver would be non-trivial.
> 
> I truly believe just calling the real USB HCI driver interrupt
> handler in a polling fashion is the way to go.

But it feels very fragile... Oh well, I will experiment with that one of
these days (no time right now though).

Ben.



  reply	other threads:[~2005-05-04  0:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01  7:55 [PATCH] fix __mod_timer vs __run_timers deadlock Oleg Nesterov
2005-05-01  9:31 ` Andrew Morton
2005-05-02 22:50   ` Juergen Kreileder
2005-05-03  0:13     ` Benjamin Herrenschmidt
2005-05-03  1:24       ` Lee Revell
2005-05-03  1:28         ` Benjamin Herrenschmidt
2005-05-03  1:33         ` Zwane Mwaikambo
2005-05-03  1:35       ` Juergen Kreileder
2005-05-03  2:48         ` Paul Mackerras
2005-05-03 18:51           ` David S. Miller
2005-05-03 23:44             ` Benjamin Herrenschmidt
2005-05-03 23:39               ` David S. Miller
2005-05-04  0:05                 ` Benjamin Herrenschmidt [this message]
2005-05-02  4:08 ` Maneesh Soni

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=1115165108.7567.76.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=jk@blackdown.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=oleg@tv-sign.ru \
    --cc=paulus@samba.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