[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080703134300.GA499@elte.hu>
Date: Thu, 3 Jul 2008 15:43:00 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Alexander Beregalov <a.beregalov@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: next-0703: build failure in x86/entry_64.S
* Ingo Molnar <mingo@...e.hu> wrote:
> hm, cannot reproduce it here with linux-next-0702.
>
> but ... this looks quite similar to an issue triggered by the
> tip/x86/xen-64bit topic (and fixed by the patch below) - but that's
> not in linux-next yet.
ok, i can see the same problem in linux-next-0703 and git-cherry-picking
the commit below fixes it. I have also pushed out a new version of
auto-generic-ipi-next which caused this problem.
> commit 6d2a6e57be1582b017a39f52385adf49d7cc4b0f
> Author: Jeremy Fitzhardinge <jeremy@...p.org>
> Date: Fri Jun 27 12:04:03 2008 -0700
>
> x86_64: fix non-paravirt compilation
>
> Make sure SWAPGS and PARAVIRT_ADJUST_EXCEPTION_FRAME are properly
> defined when CONFIG_PARAVIRT is off.
>
> Fixes Ingo's build failure:
> arch/x86/kernel/entry_64.S: Assembler messages:
> arch/x86/kernel/entry_64.S:1201: Error: invalid character '_' in mnemonic
> arch/x86/kernel/entry_64.S:1205: Error: invalid character '_' in mnemonic
> arch/x86/kernel/entry_64.S:1209: Error: invalid character '_' in mnemonic
> arch/x86/kernel/entry_64.S:1213: Error: invalid character '_' in mnemonic
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