From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jesse Brandeburg <jesse.brandeburg@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
NetDEV list <netdev@vger.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: Subject: [PATCH 1/2] x86: get back 15 vectors
Date: Mon, 04 Jan 2010 16:05:44 -0800 [thread overview]
Message-ID: <1262649945.2700.364.camel@sbs-t61.sc.intel.com> (raw)
In-Reply-To: <4B42467F.5040008@zytor.com>
On Mon, 2010-01-04 at 11:50 -0800, H. Peter Anvin wrote:
> On 01/04/2010 11:45 AM, Suresh Siddha wrote:
> > On Mon, 2010-01-04 at 11:35 -0800, Yinghai Lu wrote:
> >> sth like this?
> >>
> >> Subject: [PATCH 1/2] x86: get back 16 vectors
> >>
> >> -v2: according to hpa that we could start from 0x10
> >> according to Eric, we should hold 16 vectors for IRQ MOVE
> >>
> >> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> >>
> >
> > Yinghai we have to change IRQ_MOVE_CLEANUP_VECTOR to 0x1f or so. From
> > the cpu perspective this vector is documented as illegal, so we need to
> > check if this change will work on the cpu's we have today to get some
> > confidence.
> >
>
> It's documented as reserved, not illegal. The ability for the APIC to
> generate vectors starting at 0x10 is documented, as is the ability for
> the CPU to receive any vector number as an interrupt -- in fact, the
> legacy BIOS relies on being able to receive interrupts starting at
> vector 0x08. It causes problems galore, but only at the software level.
I have checked out couple of platforms (including 32-bit atom) and 0x1f
vector logic seems to be working.
Hopefully we won't have other hardware or software issues (vmm
restrictions etc) with this logic.
thanks,
suresh
next prev parent reply other threads:[~2010-01-05 0:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 8:42 [PATCH] x86: increase NR_IRQS and nr_irqs Yinghai Lu
2009-12-28 9:47 ` Ingo Molnar
2009-12-29 5:08 ` [PATCH -v2] " Yinghai Lu
2009-12-30 12:21 ` [tip:x86/apic] x86: Increase " tip-bot for Yinghai Lu
2010-01-04 3:06 ` [PATCH -v2] x86: increase " Jesse Brandeburg
2010-01-04 3:20 ` Yinghai Lu
2010-01-04 6:56 ` Subject: [PATCH 1/2] x86: get back 15 vectors Yinghai Lu
2010-01-04 16:18 ` Eric W. Biederman
2010-01-04 18:40 ` Yinghai Lu
2010-01-04 19:04 ` Eric W. Biederman
2010-01-04 19:14 ` H. Peter Anvin
2010-01-04 19:01 ` H. Peter Anvin
2010-01-04 19:09 ` Eric W. Biederman
2010-01-04 19:35 ` Yinghai Lu
2010-01-04 19:45 ` Suresh Siddha
2010-01-04 19:50 ` H. Peter Anvin
2010-01-05 0:05 ` Suresh Siddha [this message]
2010-01-05 0:16 ` Yinghai Lu
2010-01-05 5:30 ` [tip:x86/apic] x86, apic: Reclaim IDT vectors 0x20-0x2f tip-bot for H. Peter Anvin
2010-01-04 19:48 ` Subject: [PATCH 1/2] x86: get back 15 vectors H. Peter Anvin
2010-01-04 20:06 ` Yinghai Lu
2010-01-04 20:14 ` Eric W. Biederman
2010-01-04 20:33 ` Yinghai Lu
2010-01-04 21:10 ` H. Peter Anvin
2010-01-04 21:20 ` Yinghai Lu
2010-01-04 21:33 ` H. Peter Anvin
2010-01-04 22:01 ` Yinghai Lu
2010-01-04 23:03 ` H. Peter Anvin
2010-01-04 23:32 ` Yinghai Lu
2010-01-04 23:38 ` H. Peter Anvin
2010-01-04 23:42 ` Yinghai Lu
2010-01-04 23:49 ` Yinghai Lu
2010-01-04 23:59 ` H. Peter Anvin
2010-01-05 5:30 ` [tip:x86/apic] x86, apic: Don't waste a vector to improve vector spread tip-bot for H. Peter Anvin
2010-01-04 20:08 ` Subject: [PATCH 1/2] x86: get back 15 vectors Eric W. Biederman
2010-01-04 6:58 ` [PATCH 2/2] x86: get more exact nr_irqs Yinghai Lu
2010-01-04 16:55 ` Eric W. Biederman
2010-01-04 19:03 ` Yinghai Lu
2010-01-04 19:16 ` Eric W. Biederman
2010-01-04 19:30 ` H. Peter Anvin
2010-01-04 19:47 ` Yinghai Lu
2010-01-04 20:05 ` Eric W. Biederman
2010-01-04 21:50 ` H. Peter Anvin
2010-01-04 6:59 ` [PATCH 1/2] x86: get back 15 vectors Yinghai Lu
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=1262649945.2700.364.camel@sbs-t61.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®