From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TARGET_CPUS in assign_irq_vector
Date: Tue, 09 Sep 2008 23:45:23 -0700 [thread overview]
Message-ID: <m1zlmglcsc.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <48C719C0.6060201@goop.org> (Jeremy Fitzhardinge's message of "Tue, 09 Sep 2008 17:50:08 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> 3) give up because the idea is fundamentally ill-conceived, or 4)
> something else?
Yes.
When working with event channels you should not have any
truck with vectors and you should not call the architecture
specific do_IRQ().
Eric
next prev parent reply other threads:[~2008-09-10 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 22:30 TARGET_CPUS in assign_irq_vector Jeremy Fitzhardinge
2008-09-09 22:54 ` Yinghai Lu
2008-09-09 23:46 ` Jeremy Fitzhardinge
2008-09-10 0:26 ` Yinghai Lu
2008-09-10 0:50 ` Jeremy Fitzhardinge
2008-09-10 1:24 ` Yinghai Lu
2008-09-10 6:45 ` Eric W. Biederman [this message]
2008-09-10 19:44 ` Jeremy Fitzhardinge
2008-09-10 20:07 ` Eric W. Biederman
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=m1zlmglcsc.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.com \
/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