public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: Robin Holt <holt@sgi.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	Keith Owens <kaos@americas.sgi.com>,
	Dean Nelson <dcn@americas.sgi.com>
Subject: Re: Is notify_die being overloaded?
Date: Mon, 17 Apr 2006 09:45:32 -0700	[thread overview]
Message-ID: <20060417094531.A20168@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060413194643.GC25701@lnx-holt.americas.sgi.com>; from holt@sgi.com on Thu, Apr 13, 2006 at 02:46:44PM -0500

On Thu, Apr 13, 2006 at 02:46:44PM -0500, Robin Holt wrote:
> notify_die seems to be called to indicate the machine is going down as
> well as there are trapped events for the process.
> 
> Specifically, the following call notify_die when there are machine
> related events:
> ia64_mca_rendez_int_handler (DIE_MCA_RENDZVOUS_ENTER,
> 	DIE_MCA_RENDZVOUS_PROCESS, DIE_MCA_RENDZVOUS_LEAVE)
> ia64_mca_handler (DIE_MCA_MONARCH_ENTER, DIE_MCA_MONARCH_PROCESS,
> 	DIE_MCA_MONARCH_LEAVE)
> ia64_init_handler (DIE_INIT_ENTER,
> 	DIE_INIT_{SLAVE|MONARCH}_{ENTER|PROCESS|LEAVE})
> ia64_mca_init (DIE_MCA_NEW_TIMEOUT)
> machine_restart (DIE_MACHINE_RESTART)
> machine_halt (DIE_MACHINE_HALT)
> die (DIE_OOPS)
> 
> 
> The following seem to be process related:
> ia64_bad_break (DIE_BREAK, DIE_FAULT)
> ia64_do_page_fault (DIE_PAGE_FAULT)
> 
> 
> Shouldn't these really be seperated into two seperate notifier chains?
> One for OS level die() type activity and another for process faults
> which a debugger et. al. would want to know about?
> 
> The specific concern is some testing we have been doing with an upcoming
> OSD release.  We see notify_die being called from ia64_do_page_fault
> frequently in our performance samples.  On these machines, xpc has
> registers a die notifier and therefore callouts are occuring which have
> no relationship to a processes page faulting.  XPC is looking for events
> which indicate the OS is stopping.  Additionally, kdb is installed on
> this machine as well and it has registered a die notifier as well.

Since DIE_PAGE_FAULT is the one which come in performance path, I think
this should be optimised and I would suggest just making 
notify_die(DIE_PAGE_FAULT,..) into a seperate notifier chains (something like
notify_page_fault() which calls just the registered handlers).
In this way, in the performance critical path, we will be calling only the
required handlers(probally only the kprobes handlers) and not the whole world
registered on notify_die() call chain.

-thanks,
Anil

      parent reply	other threads:[~2006-04-17 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 19:46 Is notify_die being overloaded? Robin Holt
2006-04-15  6:19 ` Keith Owens
2006-04-15 10:43   ` Robin Holt
2006-04-17  7:52     ` Keith Owens
2006-04-17 10:51       ` Robin Holt
2006-04-17 11:25         ` Robin Holt
2006-04-18  0:23           ` Keith Owens
2006-04-18 22:16             ` ia64_do_page_fault shows 19.4% slowdown from notify_die Robin Holt
2006-04-18 23:03               ` Keshavamurthy Anil S
2006-04-19  0:30               ` Andi Kleen
2006-04-19 11:11                 ` Robin Holt
2006-04-17 16:50       ` Is notify_die being overloaded? Keshavamurthy Anil S
2006-04-17 16:45 ` Keshavamurthy Anil S [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=20060417094531.A20168@unix-os.sc.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=akpm@osdl.org \
    --cc=dcn@americas.sgi.com \
    --cc=holt@sgi.com \
    --cc=kaos@americas.sgi.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