From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Stefan Bader <stefan.bader@canonical.com>,
stable@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [stable] [PATCH] x86: Reserve FIRST_DEVICE_VECTOR in used_vectors bitmap
Date: Fri, 10 Oct 2008 14:12:25 -0700 [thread overview]
Message-ID: <20081010211225.GA17695@kroah.com> (raw)
In-Reply-To: <20081010215038.13be501e@lxorguk.ukuu.org.uk>
On Fri, Oct 10, 2008 at 09:50:38PM +0100, Alan Cox wrote:
> On Fri, 10 Oct 2008 13:41:33 -0700
> Greg KH <greg@kroah.com> wrote:
>
> > On Fri, Oct 10, 2008 at 01:35:48PM -0700, H. Peter Anvin wrote:
> > > Greg KH wrote:
> > >> Is there a problem with being assigned to IRQ0 in situations like this?
> > >
> > > On PCs, IRQ 0 is dedicated to use for the PIT.
> >
> > Ah, I didn't realize it couldn't be shared.
>
> And more importantly dev->irq == 0 or IRQ == 0 to anything but arch
> internal code means "no interrupt line".
I thought we had changed that a while ago, as some arches had 0 as a
valid irq line.
Anyway, thanks all for the information, I appreciate it.
greg k-h
next prev parent reply other threads:[~2008-10-10 21:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 20:01 [PATCH] x86: Reserve FIRST_DEVICE_VECTOR in used_vectors bitmap Stefan Bader
2008-10-10 20:16 ` [stable] " Greg KH
2008-10-10 20:23 ` Ingo Molnar
2008-10-10 20:29 ` Greg KH
2008-10-10 20:36 ` Stefan Bader
2008-10-10 20:41 ` Greg KH
2008-10-10 20:16 ` Greg KH
2008-10-10 20:22 ` Stefan Bader
2008-10-10 20:18 ` Greg KH
2008-10-10 20:24 ` Stefan Bader
2008-10-10 20:35 ` H. Peter Anvin
2008-10-10 20:41 ` Greg KH
2008-10-10 20:50 ` Alan Cox
2008-10-10 21:12 ` Greg KH [this message]
2008-10-10 21:49 ` Alan Cox
2008-10-10 22:09 ` Greg KH
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=20081010211225.GA17695@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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