All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: eranian@hpl.hp.com
Cc: perfmon@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.18 perfmon new code base + libpfm + pfmon
Date: Thu, 28 Sep 2006 07:32:39 +0000	[thread overview]
Message-ID: <p7364f8jvjc.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060927224832.GA17883@frankl.hpl.hp.com>

Stephane Eranian <eranian@hpl.hp.com> writes:
> 
> [ak] : separate patch for _TIF_WORK_CTXSW
> 	- I think I submitted a TIF patch for x86-64, but unlike i386 it is not yet in mainline

If it's not in mainline yet I lost it somehow and you should resubmit.

> [ak] : may have to add __kprobes to some functions
> 	- started doing this on some functions. Need better understanding on when to use this

Basically when you could recurse in kprobes. 

> [ak] : cleaner integration with NMI watchdog
> 	- integration done on AMD K8. Issues on P4, P6, due to PMU design

What are the issues?

> [akpm]: documentation for syscall? Is there an API specification?
> 	- answered. In short, there exists a specification but it needs to be updated

Probably you should have man pages ready for submission to the manpage maintainer.
That might also the second review pass on l-k easier if you supply
them in the description.

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: eranian@hpl.hp.com
Cc: perfmon@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.18 perfmon new code base + libpfm + pfmon
Date: 28 Sep 2006 09:32:39 +0200	[thread overview]
Message-ID: <p7364f8jvjc.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060927224832.GA17883@frankl.hpl.hp.com>

Stephane Eranian <eranian@hpl.hp.com> writes:
> 
> [ak] : separate patch for _TIF_WORK_CTXSW
> 	- I think I submitted a TIF patch for x86-64, but unlike i386 it is not yet in mainline

If it's not in mainline yet I lost it somehow and you should resubmit.

> [ak] : may have to add __kprobes to some functions
> 	- started doing this on some functions. Need better understanding on when to use this

Basically when you could recurse in kprobes. 

> [ak] : cleaner integration with NMI watchdog
> 	- integration done on AMD K8. Issues on P4, P6, due to PMU design

What are the issues?

> [akpm]: documentation for syscall? Is there an API specification?
> 	- answered. In short, there exists a specification but it needs to be updated

Probably you should have man pages ready for submission to the manpage maintainer.
That might also the second review pass on l-k easier if you supply
them in the description.

-Andi

  parent reply	other threads:[~2006-09-28  7:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 14:34 2.6.18 perfmon new code base + libpfm + pfmon Stephane Eranian
2006-09-26 14:34 ` Stephane Eranian
2006-09-27  5:09 ` Andrew Morton
2006-09-27  5:09   ` Andrew Morton
2006-09-27 22:48   ` Stephane Eranian
2006-09-27 22:48     ` Stephane Eranian
2006-09-27 23:31     ` Andrew Morton
2006-09-27 23:31       ` Andrew Morton
2006-09-28  6:49       ` Stephane Eranian
2006-09-28  6:49         ` Stephane Eranian
2006-09-28  7:05         ` Andrew Morton
2006-09-28  7:05           ` Andrew Morton
2006-09-28  7:32     ` Andi Kleen [this message]
2006-09-28  7:32       ` Andi Kleen
2006-09-28  7:56       ` Stephane Eranian
2006-09-28  7:56         ` Stephane Eranian
2006-09-28  8:05         ` Andi Kleen
2006-09-28  8:05           ` Andi Kleen
2006-09-29  9:30           ` Stephane Eranian
2006-09-29  9:30             ` Stephane Eranian
2006-09-28 13:41     ` Christoph Hellwig
2006-09-28 13:41       ` Christoph Hellwig
2006-09-28 14:04       ` Stephane Eranian
2006-09-28 14:04         ` Stephane Eranian

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=p7364f8jvjc.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfmon@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.