From: Andi Kleen <ak@suse.de>
To: "bibo,mao" <bibo_mao@linux.intel.com>
Cc: Jan Beulich <jbeulich@novell.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
mao bibo <bibo.mao@intel.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]x86_64 debug_stack nested patch
Date: Wed, 10 May 2006 12:12:06 +0200 [thread overview]
Message-ID: <200605101212.06854.ak@suse.de> (raw)
In-Reply-To: <4461A3B2.8000601@linux.intel.com>
On Wednesday 10 May 2006 10:26, bibo,mao wrote:
> yes, I am wrong. And I will modify this. And then only need define
> DEBUG_STACK_ORDER as (EXCEPTION_STACK_ORDER + 1)
If the kprobes code really wants to nest (in my opinion it's a kprobes
bug) you should reduce its stack to 2K or so. Don't want to waste
space for stupid code like this.
-Andi
prev parent reply other threads:[~2006-05-10 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 6:45 [PATCH]x86_64 debug_stack nested patch bibo,mao
2006-05-10 7:08 ` Jan Beulich
2006-05-10 7:44 ` bibo,mao
2006-05-10 7:56 ` Jan Beulich
2006-05-10 8:26 ` bibo,mao
2006-05-10 10:12 ` 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=200605101212.06854.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bibo.mao@intel.com \
--cc=bibo_mao@linux.intel.com \
--cc=jbeulich@novell.com \
--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