From: Ingo Molnar <mingo@elte.hu>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: next-0703: build failure in x86/entry_64.S
Date: Thu, 3 Jul 2008 15:43:00 +0200 [thread overview]
Message-ID: <20080703134300.GA499@elte.hu> (raw)
In-Reply-To: <20080703133132.GC12102@elte.hu>
* Ingo Molnar <mingo@elte.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@goop.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
prev parent reply other threads:[~2008-07-03 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 13:00 next-0703: build failure in x86/entry_64.S Alexander Beregalov
2008-07-03 13:31 ` Ingo Molnar
2008-07-03 13:43 ` Ingo Molnar [this message]
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=20080703134300.GA499@elte.hu \
--to=mingo@elte.hu \
--cc=a.beregalov@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).