From: Manfred Spraul <manfred@colorfullife.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sched] [patch] migration-fixes-2.5.3-pre2-A1
Date: Sun, 20 Jan 2002 15:26:23 +0100 [thread overview]
Message-ID: <3C4AD38F.7754CCC4@colorfullife.com> (raw)
> */
> #define SPURIOUS_APIC_VECTOR 0xff
> #define ERROR_APIC_VECTOR 0xfe
> #define INVALIDATE_TLB_VECTOR 0xfd
> #define RESCHEDULE_VECTOR 0xfc
> -#define CALL_FUNCTION_VECTOR 0xfb
> +#define TASK_MIGRATION_VECTOR 0xfb
> +#define CALL_FUNCTION_VECTOR 0xfa
>
Are you sure it's a good idea to have 6 interrupts at priority 15?
The local apic of the P6 has only one in-service entry and one holding
entry for each priority.
I'm not sure what happens if the entries overflow - either an interrupt
is lost or the message is resent.
<<<< Newest ia32 docu, vol3, chap. 7.6.4.3:
The P6 family and Pentium processor\x19's local APIC includes an in-service
entryy and a holding entry for each priority level. Optimally, software
should allocate no more than 2 interrupts per priority.
<<<<<
<<< Original PPro, Vol 3, chap 7.4.2:
The processor's local APIC includes an in-service entry and a holding
entry for each proirity level. To avoid losing interrupts, software
should allocate no more than 2 interrupts per priority.
<<<<<
--
Manfred
next reply other threads:[~2002-01-20 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 14:26 Manfred Spraul [this message]
2002-01-20 21:59 ` [sched] [patch] migration-fixes-2.5.3-pre2-A1 Ingo Molnar
2002-01-21 15:40 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-01-20 13:36 Ingo Molnar
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=3C4AD38F.7754CCC4@colorfullife.com \
--to=manfred@colorfullife.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox