mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: eranian@googlemail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 00/19] perfmon2 minimal v3:  introduction
Date: Tue, 29 Jul 2008 01:47:30 +1000	[thread overview]
Message-ID: <20080729014730.76b879a4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4868dbf6.0af5660a.1972.52f4@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

Hi Stephane,

On Mon, 30 Jun 2008 06:13:26 -0700 (PDT) eranian@googlemail.com wrote:
>
> The following patches implement a minimal perfmon2 subsystem which provides
> access to the hardware performance counters of modern processors.

First up, I cannot speak to the actual function of the patches, but just
to the mechanics of getting them into the kernel.  One good thing is that
with CONFIG_PERFMON turned off, it looks like the impact is very close to
zero. Two obvious things that would help these being accepted are:

	ordering - in the current incarnation, the patches produce places
where the kernel will not build.  We like things to be ordered so that
git bisection does not fail if at all possible - that means that an
allmod/yesconfig should build after the application of each patch.
Currently this is not so.  It could be mode to do so trivially by
delaying the "global" Kconfig/Makefile updates until later in the
sequence.  And you really should introduce the system calls *before*
wiring them up.

	quite a few of the macros (especially for the dummy (non
CONFIG_PERFMON) versions of functions) should be "static inline"
functions unless they absolutely must be macros.  Andrew Morton said it
best - "write in C not C preprocessor".

I can see that this infrastructure could be very useful and I appreciate
that it has been cut down for this initial merge.  These patches (even as
they are) compare favourably to some other new infrastructure that has
been introduced.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-28 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 13:13 eranian
2008-07-28 15:47 ` Stephen Rothwell [this message]
2008-07-29  6:20   ` stephane eranian
2008-07-30 23:59     ` stephane eranian
2008-07-31  0:21       ` Stephen Rothwell
2008-07-31  0:26         ` stephane eranian
2008-07-31  0:43           ` Stephen Rothwell

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=20080729014730.76b879a4.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=eranian@googlemail.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

all inboxes | Powered by JetHome®