From: ebiederm@xmission.com (Eric W. Biederman)
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Yinghai Lu <yinghai.lu@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] x86-64: typo in __assign_irq_vector when updating pos for vector and offset
Date: Sun, 22 Oct 2006 02:58:18 -0600 [thread overview]
Message-ID: <m1d58k20d1.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061022085036.GP5211@rhun.haifa.ibm.com> (Muli Ben-Yehuda's message of "Sun, 22 Oct 2006 10:50:36 +0200")
Muli Ben-Yehuda <muli@il.ibm.com> writes:
> Works!
Cool so we have a work around.
So it looks like we need to be a little more careful with vector_irq,
and it's initialization when cpus start up, or are not running.
Eric
next prev parent reply other threads:[~2006-10-22 9:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610212100.k9LL0GtC018787@hera.kernel.org>
2006-10-22 3:51 ` [PATCH] x86-64: typo in __assign_irq_vector when updating pos for vector and offset Muli Ben-Yehuda
2006-10-22 5:13 ` Yinghai Lu
2006-10-22 6:55 ` yhlu
2006-10-22 8:50 ` Muli Ben-Yehuda
2006-10-22 8:50 ` Eric W. Biederman
2006-10-22 8:28 ` Yinghai Lu
2006-10-22 8:50 ` Muli Ben-Yehuda
2006-10-22 8:58 ` Eric W. Biederman [this message]
2006-10-22 16:02 ` yhlu
2006-10-22 16:19 ` yhlu
2006-10-22 21:33 ` Andi Kleen
2006-10-22 16:20 ` Muli Ben-Yehuda
2006-10-22 16:28 ` yhlu
2006-10-22 8:35 ` Eric W. Biederman
2006-10-22 8:52 ` Muli Ben-Yehuda
2006-10-22 9:10 ` Eric W. Biederman
2006-10-23 4:32 ` [PATCH 1/2] x86_64 irq: Simplify the vector allocator Eric W. Biederman
2006-10-23 4:35 ` [PATCH 2/2] x86_64 irq: Only look at per_cpu data for online cpus Eric W. Biederman
2006-10-23 6:17 ` yhlu
2006-10-23 8:14 ` Muli Ben-Yehuda
2006-10-23 6:15 ` [PATCH 1/2] x86_64 irq: Simplify the vector allocator yhlu
2006-10-24 5:29 ` Andi Kleen
2006-10-22 13:29 ` [PATCH] x86-64: typo in __assign_irq_vector when updating pos for vector and offset Andi Kleen
2006-10-22 16:31 ` Muli Ben-Yehuda
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=m1d58k20d1.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=yinghai.lu@amd.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