From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: jacob pan <jacob.jun.pan@linux.intel.com>,
Alan Cox <alan@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Feng Tang <feng.tang@intel.com>, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] x86/sfi: fix ioapic gsi range
Date: Tue, 08 Jun 2010 14:08:56 -0700 [thread overview]
Message-ID: <4C0EB168.5080801@zytor.com> (raw)
In-Reply-To: <m1iq5tckb1.fsf@fess.ebiederm.org>
On 06/08/2010 01:59 PM, Eric W. Biederman wrote:
>
> No. There is no reason to loose 16 IDT entries indefinitely. We may
> need a boot time allocation when we see we have isa irqs, to replace
> the static allocation that we have. But for the most part we dynamically
> idt entries aka vector numbers today, and there is no reason we can't
> generalize that in the future.
>
Well, that boot time allocation is one of the things
legacy_pic->nr_legacy_irq is used for, and it really makes sense, I
think. I would really like to move away from a compile-time allocation,
and I still find it hard to believe it has a reason to exist.
-hpa
next prev parent reply other threads:[~2010-06-08 21:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 23:07 [PATCH] x86/sfi: fix ioapic gsi range Jacob Pan
2010-06-08 0:01 ` jacob pan
2010-06-08 0:24 ` Eric W. Biederman
2010-06-08 0:30 ` H. Peter Anvin
2010-06-08 1:10 ` Eric W. Biederman
2010-06-08 8:10 ` Alan Cox
2010-06-08 18:11 ` H. Peter Anvin
2010-06-08 20:04 ` Eric W. Biederman
2010-06-08 18:44 ` [PATCH] x86/irq: Rename gsi_end gsi_top, and fix off by one errors Eric W. Biederman
2010-06-09 22:06 ` [tip:x86/urgent] x86, irq: " tip-bot for Eric W. Biederman
2010-06-08 5:50 ` [PATCH] x86/sfi: fix ioapic gsi range jacob pan
2010-06-08 19:41 ` Eric W. Biederman
2010-06-08 19:12 ` Alan Cox
2010-06-08 20:56 ` Yuhong Bao
2010-06-08 22:16 ` Eric W. Biederman
2010-06-08 22:29 ` Alan Cox
2010-06-08 20:36 ` H. Peter Anvin
2010-06-08 20:59 ` Eric W. Biederman
2010-06-08 21:08 ` H. Peter Anvin [this message]
2010-06-08 21:51 ` Eric W. Biederman
2010-06-08 20:41 ` jacob pan
2010-06-08 21:22 ` Eric W. Biederman
2010-06-08 22:17 ` jacob pan
2010-06-09 23:44 ` Eric W. Biederman
2010-06-10 8:40 ` jacob pan
2010-06-10 14:39 ` 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=4C0EB168.5080801@zytor.com \
--to=hpa@zytor.com \
--cc=alan@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=feng.tang@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.