mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] performance counters 3.1 for 2.5.45 [4/4]: kernel changes
Date: 04 Nov 2002 12:12:19 -0800	[thread overview]
Message-ID: <1036440740.18668.5.camel@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <200210312310.AAA07615@kim.it.uu.se>

On Thu, 2002-10-31 at 15:10, Mikael Pettersson wrote:
> This is part 4 of 4 of perfctr-3.1 for the 2.5.45 kernel:
> kernel changes to integrate the low and high-level drivers.
> 
> /Mikael
> 
>  CREDITS                              |    1 +
>  MAINTAINERS                          |    6 ++++++
>  arch/i386/Kconfig                    |    1 +
>  arch/i386/kernel/entry.S             |   11 +++++++++++
>  arch/i386/kernel/i8259.c             |    3 +++
>  arch/i386/kernel/process.c           |    9 +++++++++
>  arch/i386/mach-generic/irq_vectors.h |    5 +++--
>  drivers/Makefile                     |    1 +
>  include/asm-i386/apic.h              |    3 +++
>  include/asm-i386/processor.h         |    2 ++
>  include/asm-i386/unistd.h            |    1 +
>  kernel/timer.c                       |    2 ++
>  12 files changed, 43 insertions(+), 2 deletions(-)

Rather than adding yet another system call, shouldn't this be done by
extending the cpu part of sysfs (or /proc)?

It looks like the operations in sys_vperfctr could be easily mapped to a
RAM based file system.  As it stands it reminds me of one of the old DEC
graphic libraries with one API entry for all the operations, and 65
different flag values.




  reply	other threads:[~2002-11-04 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 23:10 Mikael Pettersson
2002-11-04 20:12 ` Stephen Hemminger [this message]
2002-11-04 20:31   ` Mikael Pettersson
2002-11-04 20:56     ` Stephen Hemminger

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=1036440740.18668.5.camel@dell_ss3.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®