[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ps7yphf7.fsf@ebiederm.dsl.xmission.com>
Date: Sun, 25 Feb 2007 05:09:48 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Mika Penttilä <mika.penttila@...umbus.fi>
Cc: Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
Zwane Mwaikambo <zwane@...radead.org>,
Ashok Raj <ashok.raj@...el.com>, Ingo Molnar <mingo@...e.hu>,
"Lu, Yinghai" <yinghai.lu@....com>,
Natalie Protasevich <protasnb@...il.com>,
Andi Kleen <ak@...e.de>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
Mika Penttilä <mika.penttila@...umbus.fi> writes:
> Eric W. Biederman wrote:
>> * Vectors 0x20-0x2f are used for ISA interrupts.
>> */
>> -#define IRQ0_VECTOR FIRST_EXTERNAL_VECTOR
>> +#define IRQ0_VECTOR FIRST_EXTERNAL_VECTOR + 0x10
>> #define IRQ1_VECTOR IRQ0_VECTOR + 1
>> #define IRQ2_VECTOR IRQ0_VECTOR + 2
>> #define IRQ3_VECTOR IRQ0_VECTOR + 3
>> @@ -82,7 +87,7 @@
>>
> I think we have a dependency in i8259.c that irq0 is mapped to vector 0x20.
We did, but I'm pretty certain I removed it when I introduced the
IRQ[0-15]_VECTOR defines.
One of my test machines seems to be delivering irq0 in EXTInt mode
with this patch applied (a bug of another flavor) so I don't think
there is a real issue here.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists