From: Mike Frysinger <vapier.adi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] scripts/checksyscalls.sh: only whine perf_counter_open when supported
Date: Fri, 12 Jun 2009 09:34:15 -0400 [thread overview]
Message-ID: <8bd0f97a0906120634o1f25d713v61e01de6ed47f936@mail.gmail.com> (raw)
In-Reply-To: <20090612123152.GE31845@elte.hu>
On Fri, Jun 12, 2009 at 08:31, Ingo Molnar wrote:
> That way say build breakages or runtime failures due to perfcounters
> only become possible on an architecture if the architecture
> maintainer has hooked up the syscall
also, this syscall approach is not how any other syscall is handled.
a runtime error along the lines of ENOSYS is trivial to diagnosis and
explain. you get the exact same behavior on supported architectures
running an older kernel or any kernel with the profiling code
disabled, so any userland code should already be sanely handling this.
-mike
next prev parent reply other threads:[~2009-06-12 13:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 11:29 Mike Frysinger
2009-06-12 12:05 ` Ingo Molnar
2009-06-12 12:13 ` Mike Frysinger
2009-06-12 12:17 ` Ingo Molnar
2009-06-12 12:22 ` Mike Frysinger
2009-06-12 12:31 ` Ingo Molnar
2009-06-12 12:41 ` Mike Frysinger
2009-06-12 12:59 ` Ingo Molnar
2009-06-12 13:04 ` Mike Frysinger
2009-06-12 13:09 ` Ingo Molnar
2009-06-12 13:21 ` Mike Frysinger
2009-06-12 13:56 ` Ingo Molnar
2009-06-12 15:25 ` Alan Cox
2009-06-12 15:56 ` Ingo Molnar
2009-06-12 16:57 ` Ingo Molnar
2009-06-12 17:11 ` Mike Frysinger
2009-06-12 13:34 ` Mike Frysinger [this message]
2009-06-12 15:16 ` Mike Frysinger
2009-06-12 15:21 ` Ingo Molnar
2009-06-12 15:29 ` Mike Frysinger
2009-06-12 15:50 ` Ingo Molnar
2009-06-13 21:00 ` Ingo Molnar
2009-06-13 4:37 ` Paul Mackerras
2009-06-13 10:48 ` Mike Frysinger
2009-06-14 9:37 ` Paul Mundt
2009-06-14 9:55 ` Mike Frysinger
2009-06-14 10:11 ` Paul Mundt
2009-06-14 10:55 ` Mike Frysinger
2009-06-14 11:20 ` Paul Mundt
2009-06-14 11:47 ` Mike Frysinger
2009-06-14 11:20 ` Sam Ravnborg
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=8bd0f97a0906120634o1f25d713v61e01de6ed47f936@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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®