From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: having access to interrupt specifier in map() function
Date: Thu, 16 Jul 2009 08:33:17 +1000 [thread overview]
Message-ID: <1247697197.27937.2.camel@pasglop> (raw)
In-Reply-To: <761CE7B3-A7FD-41FD-A828-B9F17F73DF32@kernel.crashing.org>
On Wed, 2009-07-15 at 09:11 -0500, Kumar Gala wrote:
> Ben,
>
> Do you have any ideas on keeping access to the interrupt specifier
> around so when we call map() we have access to it. Our HV guys are
> looking at using additional bits in the interrupt specifier to encode
> information beyond just level/sense of the IRQ and want to make
> decisions based on it during map().
>
> Maybe we can keep it around in irq_map[].
Or we could translate those additional info into flags in the IRQ desc ?
Might be possible to request some arch specific flags in there.
Cheers,
Ben.
prev parent reply other threads:[~2009-07-15 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 14:11 having access to interrupt specifier in map() function Kumar Gala
2009-07-15 22:33 ` Benjamin Herrenschmidt [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=1247697197.27937.2.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).