mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: <heukelum@fastmail.fm>, <tglx@linutronix.de>, <mingo@redhat.com>,
	<linux-kernel@vger.kernel.org>, <hpa@zytor.com>
Subject: Re: [tip:x86/asm] x86-64: Add CFI annotations to lib/rwsem_64.S
Date: Tue, 01 Mar 2011 08:26:45 +0000	[thread overview]
Message-ID: <4D6CBBD502000078000343DF@vpn.id2.novell.com> (raw)
In-Reply-To: <20110228182642.GA7041@elte.hu>

>>> On 28.02.11 at 19:26, Ingo Molnar <mingo@elte.hu> wrote:

> * tip-bot for Jan Beulich <JBeulich@novell.com> wrote:
> 
>> Commit-ID:  39f2205e1abd1b6fffdaf45e1f1c3049a5f8999c
>> Gitweb:     
> http://git.kernel.org/tip/39f2205e1abd1b6fffdaf45e1f1c3049a5f8999c 
>> Author:     Jan Beulich <JBeulich@novell.com>
>> AuthorDate: Mon, 28 Feb 2011 15:31:59 +0000
>> Committer:  Ingo Molnar <mingo@elte.hu>
>> CommitDate: Mon, 28 Feb 2011 18:06:21 +0100
>> 
>> x86-64: Add CFI annotations to lib/rwsem_64.S
>> 
>> These weren't part of the initial commit of this code.
>> 
>> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>> Cc: Alexander van Heukelum <heukelum@fastmail.fm>
>> LKML-Reference: <4D6BCDFF02000078000341B0@vpn.id2.novell.com>
>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>> ---
>>  arch/x86/lib/rwsem_64.S |   56 ++++++++++++++++++++++++++++------------------
>>  1 files changed, 34 insertions(+), 22 deletions(-)
> 
> this change breaks the UML build:
> 
>  tip/arch/um/sys-x86_64/../../x86/lib/rwsem_64.S:46: Error: no such 
> instruction: `pushq_cfi %rdi'

Any reason why arch/um/Kconfig.x86 has X86_32 but not
X86_64? That's resulting in asm/dwarf2.h producing the 32-bit
(pushl_cfi & Co) macros instead of the 64-bit ones. And I
wonder what other inconsistencies this may cause...

If this is on purpose (i.e. simply adding X86_64 as a new config
option there isn't the right solution), what would be the preferred
way of fixing this in asm/dwarf2.h:
- #ifndef CONFIG_X86_32,
- #ifdef CONFIG_64BIT,
- yet something else?

Thanks, Jan


  reply	other threads:[~2011-03-01  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 15:31 [PATCH] x86-64: add " Jan Beulich
2011-02-28 17:28 ` [tip:x86/asm] x86-64: Add " tip-bot for Jan Beulich
2011-02-28 18:26   ` Ingo Molnar
2011-03-01  8:26     ` Jan Beulich [this message]
2011-03-01  8:56       ` Ingo Molnar
2011-03-01  9:38         ` Jan Beulich
2011-03-01 10:37           ` Ingo Molnar

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=4D6CBBD502000078000343DF@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=heukelum@fastmail.fm \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®