From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] x86-64: adjust ia32entry.S
Date: Fri, 11 Nov 2005 16:34:44 +0100 [thread overview]
Message-ID: <200511111634.44871.ak@suse.de> (raw)
In-Reply-To: <43722D73.76F0.0078.0@novell.com>
On Wednesday 09 November 2005 17:10, Jan Beulich wrote:
> IA32 compatibility entry points needlessly played with extended
> registers. Additionally, frame unwind information was still incorrect
> for ia32_ptregs_common (sorry, my fault).
What do you mean with needlessly played? That it didn't initialize
all on the stack frame? That was more a feature than a bug.
Did it cause you problems?
In general I'm weary of making the asm macros more complex
(adding more arguments etc.) Please keep it simple.
-Andi
next prev parent reply other threads:[~2005-11-11 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 13:02 [PATCH] x86-64: separate unwind info generation from CONFIG_DEBUG_INFO Jan Beulich
2005-11-08 14:21 ` [PATCH] x86-64: fix bound check IDT gate Jan Beulich
2005-11-08 14:22 ` [PATCH] x86-64: remove dead die_if_kernel() Jan Beulich
2005-11-08 14:23 ` [PATCH] x86-64: make trap information available to die notification handlers Jan Beulich
2005-11-08 14:23 ` [PATCH] x86-64: adjust double fault handling Jan Beulich
2005-11-08 14:24 ` [PATCH] x86-64: remove unprotected iret Jan Beulich
2005-11-10 3:38 ` [discuss] " Andi Kleen
2005-11-08 14:25 ` [PATCH] x86-64: adjust page fault handling Jan Beulich
2005-11-09 16:10 ` [PATCH] x86-64: adjust ia32entry.S Jan Beulich
2005-11-11 15:34 ` Andi Kleen [this message]
2005-11-11 15:50 ` Jan Beulich
2005-11-11 15:53 ` [discuss] " Andi Kleen
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=200511111634.44871.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/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