From: "David S. Miller" <davem@davemloft.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Tue, 3 May 2005 16:39:16 -0700 [thread overview]
Message-ID: <20050503163916.30d64630.davem@davemloft.net> (raw)
In-Reply-To: <1115163893.7568.49.camel@gaston>
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 :)
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.
next prev parent reply other threads:[~2005-05-03 23:51 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 [this message]
2005-05-04 0:05 ` Benjamin Herrenschmidt
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=20050503163916.30d64630.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.