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]
Date:	Tue, 1 Jul 2008 22:31:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Nick Piggin <npiggin@...e.de>, Mark McLoughlin <markmc@...hat.com>,
	xen-devel <xen-devel@...ts.xensource.com>,
	Eduardo Habkost <ehabkost@...hat.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Stephen Tweedie <sct@...hat.com>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for
	64-bit Xen support


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Ingo Molnar wrote:
>> Excluding the x86/xen-64bit topic solves the problem.
>>
>> It triggered on two 64-bit machines so it seems readily reproducible  
>> with that config.
>>
>> i've pushed the failing tree out to tip/tmp.xen-64bit.Tue_Jul__1_10_55
>>   
>
> The patch to fix this is on tip/x86/unify-setup: "x86: setup_arch() && 
> early_ioremap_init()".  Logically that patch should probably be in the 
> xen64 branch, since it's only meaningful with the early_ioremap 
> unification.

ah, indeed - it was missing from tip/master due to:

| commit ac998c259605741efcfbd215533b379970ba1d9f
| Author: Ingo Molnar <mingo@...e.hu>
| Date:   Mon Jun 30 12:01:31 2008 +0200
|
|    Revert "x86: setup_arch() && early_ioremap_init()"
|
|    This reverts commit 181b3601a1a7d2ac3ace6b23cb3204450a4f9a27.

because that change needed the other changes from xen-64bit.

will retry tomorrow.

	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