lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090130185411.GA9984@elte.hu>
Date:	Fri, 30 Jan 2009 19:54:11 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] voyager: fix up for moving the generic smp call func
	to pointers


James,

* James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> commit e7986739a76cde5079da08809d8bbc6878387ae0
> Author: Mike Travis <travis@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ