From: Hans Lambrechts <hans.lambrechts@skynet.be>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21pre3 smp_affinity, very strange
Date: Mon, 20 Jan 2003 17:41:02 +0100 [thread overview]
Message-ID: <200301201741.02782.hans.lambrechts@skynet.be> (raw)
In-Reply-To: <1043002445.1479.8.camel@laptop.fenrus.com>
Thanks Manfred and Arjan for responding, and for the solution :-)
My box works now as before.
pc:~ # cat /proc/interrupts
CPU0 CPU1
0: 5894 5418 IO-APIC-edge timer
1: 57 40 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 0 2 IO-APIC-edge rtc
9: 0 0 IO-APIC-edge acpi
12: 283 223 IO-APIC-edge PS/2 Mouse
14: 4 3 IO-APIC-edge ide0
16: 4044 3976 IO-APIC-level aic7xxx
18: 50 42 IO-APIC-level eth0
NMI: 11227 11227
LOC: 11204 11203
ERR: 0
MIS: 0
Patch attached at the bottom of the page. If any comments, please cc me.
On Sunday 19 January 2003 19:54, you wrote:
> > Did the APIC or mpparse changes cause this?
>
> +#ifdef CONFIG_X86_CLUSTERED_APIC
> +static inline int target_cpus(void)
> +{
> + static int cpu;
> + switch(clustered_apic_mode){
> + case CLUSTERED_APIC_NUMAQ:
> + /* Broadcast intrs to local quad only. */
> + return APIC_BROADCAST_ID_APIC;
> + case CLUSTERED_APIC_XAPIC:
> + /*round robin the interrupts*/
> + cpu = (cpu+1)%smp_num_cpus;
> + return cpu_to_physical_apicid(cpu);
> + default:
> + }
> + return cpu_online_map;
> +}
> +#else
> +#define target_cpus() (0x01)
> +#endif
> (2.4.21-pre3)
> that's wrong..... 0x01 -> 0xFF and it should be fixed
--- linux/include/asm-i386/smpboot.h 2003-01-20 16:45:13.000000000 +0100
+++ linux/include/asm-i386/smpboot.h.orig 2003-01-20 16:44:05.000000000 +0100
@@ -116,6 +116,6 @@
return cpu_online_map;
}
#else
-#define target_cpus() (0xFFFFFFFF)
+#define target_cpus() (0x01)
#endif
#endif
next prev parent reply other threads:[~2003-01-20 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 15:45 Hans Lambrechts
2003-01-19 18:54 ` Arjan van de Ven
2003-01-20 16:41 ` Hans Lambrechts [this message]
2003-01-19 20:41 Manfred Spraul
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=200301201741.02782.hans.lambrechts@skynet.be \
--to=hans.lambrechts@skynet.be \
--cc=linux-kernel@vger.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®