From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, patches@x86-64.org
Subject: Re: [PATCH] x86: optionally show last exception from/to register contents (v2)
Date: Sat, 1 Sep 2007 13:18:31 +0200 [thread overview]
Message-ID: <200709011318.31520.ak@suse.de> (raw)
In-Reply-To: <46D418AF.76E4.0078.0@novell.com>
On Tuesday 28 August 2007 12:44:31 Jan Beulich wrote:
> .. when dumping register state. This is particularly useful when gcc
> managed to tail-call optimize an indirect call which happens to hit a
> NULL (or otherwise invalid) pointer.
I added it, with a warning in the documentation and changelog
Also all the other patches except for the #DF one. Thanks.
BTW I think there is a reasonable cheap way to avoid the interrupt race:
If pda->irqcount was split into two 16bit words and irq entry code increases the upper
16bit word (that should be nearly free because because both are in L1 cache;
with some luck the CPU can even dual-issue). Then the traps code could save
the irq count early and then in the no_context case disable interrupts,
compare and only print LER if there were no interrupts inbetween.
-Andi
prev parent reply other threads:[~2007-09-01 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 10:44 [PATCH] x86: optionally show last exception from/to register contents (v2) Jan Beulich
2007-09-01 11:18 ` Andi Kleen [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=200709011318.31520.ak@suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.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