public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
Cc: Anderw Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Keith Owens <kaos@americas.sgi.com>,
	Dean Nelson <dnc@americas.sgi.com>,
	Tony Luck <tony.luck@intel.com>,
	Ananth Mavinakayanahalli <ananth@in.ibm.com>,
	Prasanna Panchamukhi <prasanna@in.ibm.com>,
	Dave M <davem@davemloft.net>
Subject: Re: [patch 2/6] Notify page fault call chain for x86_64
Date: Wed, 19 Apr 2006 23:07:03 +0200	[thread overview]
Message-ID: <200604192307.03772.ak@suse.de> (raw)
In-Reply-To: <20060419190134.862282078@csdlinux-2.jf.intel.com>

On Wednesday 19 April 2006 21:01, Anil S Keshavamurthy wrote:

You seem to be missing a description/rationale here.



-Andi

> ---
> arch/x86_64/kernel/traps.c  |   12 ++++++++++++
> arch/x86_64/mm/fault.c      |    4 ++--
> include/asm-x86_64/kdebug.h |   16 ++++++++++++++++
> 3 files changed, 30 insertions(+), 2 deletions(-)

  reply	other threads:[~2006-04-19 21:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 19:00 [patch 0/6] Notify page fault call chain Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 1/6] Notify page fault call chain for i386 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 2/6] Notify page fault call chain for x86_64 Anil S Keshavamurthy
2006-04-19 21:07   ` Andi Kleen [this message]
2006-04-19 21:25     ` Keshavamurthy Anil S
2006-04-19 19:01 ` [patch 3/6] Notify page fault call chain for ia64 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 4/6] Notify page fault call chain for powerpc Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 5/6] Notify page fault call chain for sparc64 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 6/6] Kprobes registers for notify page fault Anil S Keshavamurthy

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=200604192307.03772.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=dnc@americas.sgi.com \
    --cc=kaos@americas.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasanna@in.ibm.com \
    --cc=tony.luck@intel.com \
    /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