[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080625152212.GA3442@elte.hu>
Date:	Wed, 25 Jun 2008 17:22:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
	xen-devel <xen-devel@...ts.xensource.com>,
	Stephen Tweedie <sct@...hat.com>,
	Eduardo Habkost <ehabkost@...hat.com>,
	Mark McLoughlin <markmc@...hat.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Nick Piggin <npiggin@...e.de>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen
	support
* Ingo Molnar <mingo@...e.hu> wrote:
> Anyway, that's all theory - i'll try out your patchset in -tip to see 
> what breaks in practice ;-)
i've put the commits (and a good number of dependent commits) into the 
new tip/x86/xen-64bit topic branch.
It quickly broke the build in testing:
 include/asm/pgalloc.h: In function ‘paravirt_pgd_free':
 include/asm/pgalloc.h:14: error: parameter name omitted
 arch/x86/kernel/entry_64.S: In file included from 
 arch/x86/kernel/traps_64.c:51:include/asm/pgalloc.h: In function ‘paravirt_pgd_free':
 include/asm/pgalloc.h:14: error: parameter name omitted
 [...]
with this config:
  http://redhat.com/~mingo/misc/config-Wed_Jun_25_16_37_51_CEST_2008.bad
this could easily be some integration mistake on my part, so please 
double-check the end result.
Merging it into tip/master is a bit tricky, due to various interactions. 
This should work fine if you check out the latest tip/master:
  git-merge tip/x86/xen-64bit
  [ ... fix up the trivial merge conflict ... ]
i've already merged tip/x86/xen-64bit-base topic into master, to make it 
easier. (there were a few preconditions for the 64-bit Xen patches which 
arent carried in linux-next - such as the nmi-safe changes.)
	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
 
