[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0906140255h295b393dl3165fff4c0a6baf6@mail.gmail.com>
Date: Sun, 14 Jun 2009 05:55:44 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: Paul Mundt <lethal@...ux-sh.org>, akpm <akpm@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts/checksyscalls.sh: only whine perf_counter_open
when supported
On Sun, Jun 14, 2009 at 05:37, Paul Mundt wrote:
> On Sat, Jun 13, 2009 at 06:48:52AM -0400, Mike Frysinger wrote:
>> On Fri, Jun 12, 2009 at 07:29, Mike Frysinger wrote:
>> > If the port does not support HAVE_PERF_COUNTERS, then they can't support
>> > the perf_counter_open syscall either. ??Rather than forcing everyone to add
>> > an ignore (or suffer the warning until they get around to implementing
>> > support), only whine about the syscall when applicable.
>> >
>> > Signed-off-by: Mike Frysinger <vapier@...too.org>
>>
>> Andrew: could you pick this up since Ingo acked it now ?
btw, Sam said he would pick it up via the kbuild tree
> I fail to see why this is necessary? cond_syscall() takes care of this in
> the not implemented case, the same as every other syscall backing some
> feature that has yet to be implemented.
i dont think we should go hassling every arch maintainer when a new
syscall is added that requires arch-specific support for optional
features (especially when said features are debug in nature). if
wiring up the syscall is the only work because the code is all common
(like the pread/pwrite functions), then np of course.
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists