From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: tglx@linutronix.de, hpa@zytor.com,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
Cyrill Gorcunov <gorcunov@gmail.com>,
Alexander van Heukelum <heukelum@fastmail.fm>
Subject: Re: [PATCH] x86-64: add unwind annotations to early_idt_handler
Date: Thu, 12 Mar 2009 11:53:45 +0100 [thread overview]
Message-ID: <20090312105345.GB30204@elte.hu> (raw)
In-Reply-To: <49B8F3A2.76E4.0078.0@novell.com>
* Jan Beulich <jbeulich@novell.com> wrote:
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: Andi Kleen <andi@firstfloor.org>
>
> ---
> arch/x86/kernel/head_64.S | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> --- linux-2.6.29-rc7/arch/x86/kernel/head_64.S 2009-03-11 17:52:10.000000000 +0100
> +++ 2.6.29-rc7-x86_64-unwind-early_idt_handler/arch/x86/kernel/head_64.S 2009-02-18 13:38:09.000000000 +0100
> @@ -280,6 +280,8 @@ early_idt_handlers:
>
> ENTRY(early_idt_handler)
> #ifdef CONFIG_EARLY_PRINTK
> +#include <asm/calling.h>
> +#include <asm/dwarf2.h>
> cmpl $2,early_recursion_flag(%rip)
> jz 1f
> incl early_recursion_flag(%rip)
> @@ -295,6 +297,16 @@ ENTRY(early_idt_handler)
> testl $0x27d00,%eax
> je 0f
> popq %r8 # get error code
> +
> + CFI_STARTPROC simple
> + CFI_SIGNAL_FRAME
> + CFI_DEF_CFA rsp, SS+8-RIP
> +# CFI_REL_OFFSET ss, SS-RIP
> + CFI_REL_OFFSET rsp, RSP-RIP
> +# CFI_REL_OFFSET rflags, EFLAGS-RIP
> +# CFI_REL_OFFSET cs, CS-RIP
> + CFI_REL_OFFSET rip, RIP-RIP
> +
This too is too ugly - there should be a structured macro that
expresses this - instead of open-coded CFI details. This is a
regular x86 entry layout with a lot of commonalities with other
entry points.
Ingo
next prev parent reply other threads:[~2009-03-12 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 10:36 Jan Beulich
2009-03-12 10:53 ` Ingo Molnar [this message]
2009-03-12 11:36 ` Jan Beulich
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=20090312105345.GB30204@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=gorcunov@gmail.com \
--cc=heukelum@fastmail.fm \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--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®