From: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
To: Anderw Morton <akpm@osdl.org>
Cc: 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>, Andi Kleen <ak@suse.de>,
Robin Holt <holt@sgi.com>
Subject: [(resend)patch 0/7] Notify page fault call chain
Date: Wed, 19 Apr 2006 15:14:19 -0700 [thread overview]
Message-ID: <20060419221419.382297865@csdlinux-2.jf.intel.com> (raw)
Hi Andrew,
Currently in the do_page_fault() code path, we call
notify_die(DIE_PAGE_FAULT, ...) to notify the page fault.
The only interested components for this page fault
notifications are Kprobes and/or kdb. Since
notify_die() is highly overloaded, this page fault
notification is currently being sent to other
components registered with register_die_notifier()
which uses the same die_chain to loop for all
the registered components.
In order to optimize the do_page_fault() code path,
this critical page fault notification is now moved
to different call chain and the test results conducted
by Robin Holt showed great improvements.
Patches for i386, x86_64, ia64, powerpc and sparc64 follows this mail.
Please apply.
Thanks,
Anil Keshavamurthy
--
next reply other threads:[~2006-04-19 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 22:14 Anil S Keshavamurthy [this message]
2006-04-19 22:14 ` [(resend)patch 1/7] Notify page fault call chain for i386 Anil S Keshavamurthy
2006-04-19 22:14 ` [(resend)patch 2/7] Notify page fault call chain for x86_64 Anil S Keshavamurthy
2006-04-19 22:14 ` [(resend)patch 3/7] Notify page fault call chain for ia64 Anil S Keshavamurthy
2006-04-20 2:18 ` Keith Owens
2006-04-20 4:47 ` Keshavamurthy Anil S
2006-04-19 22:14 ` [(resend)patch 4/7] Notify page fault call chain for powerpc Anil S Keshavamurthy
2006-04-19 22:14 ` [(resend)patch 5/7] Notify page fault call chain for sparc64 Anil S Keshavamurthy
2006-04-19 22:14 ` [(resend)patch 6/7] Kprobes registers for notify page fault Anil S Keshavamurthy
2006-04-19 22:14 ` [(resend)patch 7/7] Kprobes - Register for page fault notify on active probes Anil S Keshavamurthy
2006-04-20 3:57 ` Ananth N Mavinakayanahalli
2006-04-20 4:53 ` Keshavamurthy Anil S
2006-04-20 0:27 ` [(resend)patch 0/7] Notify page fault call chain Keith Owens
2006-04-20 4:37 ` Keshavamurthy Anil S
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=20060419221419.382297865@csdlinux-2.jf.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=dnc@americas.sgi.com \
--cc=holt@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