From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] voyager: fix up for moving the generic smp call func to pointers
Date: Fri, 30 Jan 2009 19:54:11 +0100 [thread overview]
Message-ID: <20090130185411.GA9984@elte.hu> (raw)
In-Reply-To: <1233340524.3248.45.camel@localhost.localdomain>
James,
* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> commit e7986739a76cde5079da08809d8bbc6878387ae0
> Author: Mike Travis <travis@sgi.com>
> Date: Tue Dec 16 17:33:52 2008 -0800
>
> x86 smp: modify send_IPI_mask interface to accept cpumask_t pointers
>
> Changed all the IPI ops to take pointers, but didn't update voyager,
> which is now broken. Make the changes in voyager as well.
Note: earlier this week i've rearchitectured the x86 subarchitecture and
APIC code - so there's a whole lot more to be done on the Voyager side
than just the cpumask conversion.
The x86/Voyager subarch is not fully ported yet (i cleaned up its Kconfig
impact already) and hence it is disabled for the time being. It ought to
be relatively straightforward to port it to the new code - if you are
interested in doing that.
You can find the latest code in tip/master at:
http://people.redhat.com/mingo/tip.git/README
it's tentatively aimed for v2.6.30.
If you have any questions/suggestions about this code, feel free ...
Ingo
next prev parent reply other threads:[~2009-01-30 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 18:35 [PATCH] voyager: fix up for moving the generic smp call func to pointers James Bottomley
2009-01-30 18:54 ` Ingo Molnar [this message]
2009-01-30 18:59 ` James Bottomley
2009-01-30 19:38 ` Ingo Molnar
2009-01-30 19:41 ` James Bottomley
2009-01-31 19:05 ` [PATCH] x86/Voyager: make it build and boot Ingo Molnar
2009-02-01 15:16 ` James Bottomley
2009-02-01 17:04 ` 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=20090130185411.GA9984@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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