mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	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: Mon, 4 Nov 2002 21:31:25 +0100	[thread overview]
Message-ID: <15814.55581.459295.2217@kim.it.uu.se> (raw)
In-Reply-To: <1036440740.18668.5.camel@dell_ss3.pdx.osdl.net>

Stephen Hemminger writes:
 > 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.
...
 > 
 > Rather than adding yet another system call, shouldn't this be done by
 > extending the cpu part of sysfs (or /proc)?

Why?
ptrace() is a system call
fork() is a system call
write() is a system call
other arch's performance counter interfaces are system calls
...

 > 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.

There are about half a dozen operations, not 65. I could use 6 system calls,
no problem, but as long as Linus is silent about this I have no reason to
change it speculatively in random directions.

/Mikael

  reply	other threads:[~2002-11-04 20:24 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
2002-11-04 20:31   ` Mikael Pettersson [this message]
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=15814.55581.459295.2217@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --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®