From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Andi Kleen" <ak@muc.de>, "Muli Ben-Yehuda" <muli@il.ibm.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86-64: using cpu_online_map instead of APIC_ALL_CPUS
Date: Sun, 22 Oct 2006 12:58:57 -0700 [thread overview]
Message-ID: <86802c440610221258q29b19839i7290b628424f7dba@mail.gmail.com> (raw)
In-Reply-To: <m1k62sz150.fsf@ebiederm.dsl.xmission.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Muli,
Can you test this one?
YH
On 10/22/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> "Yinghai Lu" <yinghai.lu@amd.com> writes:
>
> > Using cpu_online_map instead of APIC_ALL_CPUS for flat apic mode, So
> > __assign_irq_vector can refer correct per_cpu data.
> >
> > Cc: Muli Ben-Yehuda <muli@il.ibm.com>
> > Signed-off-by: Yinghai Lu <yinghai.lu@amd.com>
>
> Nack. This fixes the symptom not the bug.
> More comprehensive patches follow.
>
> Eric
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
[-- Attachment #2: io_apic.diff --]
[-- Type: text/x-patch, Size: 446 bytes --]
diff --git a/arch/x86_64/kernel/io_apic.c b/arch/x86_64/kernel/io_apic.c
index b000017..29cae92 100644
--- a/arch/x86_64/kernel/io_apic.c
+++ b/arch/x86_64/kernel/io_apic.c
@@ -634,7 +634,7 @@ static int __assign_irq_vector(int irq,
int first, new_cpu;
int vector, offset;
- domain = vector_allocation_domain(cpu);
+ cpus_and(domain, vector_allocation_domain(cpu), mask);
first = first_cpu(domain);
vector = pos[first].vector;
next prev parent reply other threads:[~2006-10-22 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 16:42 Yinghai Lu
2006-10-22 16:50 ` Muli Ben-Yehuda
2006-10-22 17:55 ` Eric W. Biederman
2006-10-22 19:58 ` Yinghai Lu [this message]
2006-10-23 7:43 ` Muli Ben-Yehuda
2006-10-23 8:05 ` yhlu
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=86802c440610221258q29b19839i7290b628424f7dba@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=ak@muc.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
/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®