From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933769AbcA0RcE (ORCPT ); Wed, 27 Jan 2016 12:32:04 -0500 Received: from mail.efficios.com ([78.47.125.74]:45708 "EHLO mail.efficios.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932303AbcA0RcB (ORCPT ); Wed, 27 Jan 2016 12:32:01 -0500 Date: Wed, 27 Jan 2016 17:31:58 +0000 (UTC) From: Mathieu Desnoyers To: Thomas Gleixner Cc: Paul Turner , Andrew Hunter , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-api , Andy Lutomirski , Andi Kleen , Dave Watson , Chris Lameter , Ingo Molnar , Ben Maurer , rostedt , "Paul E. McKenney" , Josh Triplett , Linus Torvalds , Andrew Morton , Russell King , Catalin Marinas , Will Deacon , Michael Kerrisk Message-ID: <671969438.6129.1453915918933.JavaMail.zimbra@efficios.com> In-Reply-To: References: <1453913683-28915-1-git-send-email-mathieu.desnoyers@efficios.com> <1453913683-28915-2-git-send-email-mathieu.desnoyers@efficios.com> Subject: Re: [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [78.47.125.74] X-Mailer: Zimbra 8.6.0_GA_1178 (ZimbraWebClient - FF43 (Linux)/8.6.0_GA_1178) Thread-Topic: getcpu_cache system call: cache CPU number of running thread Thread-Index: Cu2LuWV4Lfl8DYUJvGCUHN6mGcGbkg== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- On Jan 27, 2016, at 12:22 PM, Thomas Gleixner tglx@linutronix.de wrote: > On Wed, 27 Jan 2016, Mathieu Desnoyers wrote: >> +/* >> + * sys_getcpu_cache - setup getcpu cache for caller thread >> + */ >> +SYSCALL_DEFINE2(getcpu_cache, int32_t __user **, cpu_cachep, int, flags) >> +{ >> + int32_t __user *cpu_cache; >> + >> + if (unlikely(flags)) >> + return -EINVAL; >> + /* Check if cpu_cache is already registered. */ >> + if (current->cpu_cache) { >> + if (put_user(current->cpu_cache, cpu_cachep)) >> + return -EFAULT; >> + return 0; >> + } > > This is really odd. How is the caller supposed to differentiate between: > > 1) Get the installed cpucache pointer > > 2) Set the cpucache pointer > > We really want clearly seperated functionality here. > > getcpu_cache(ptr, GET_CACHEP); > > and > > getcpu_cache(ptr, SET_CACHEP); > > Returns -EBUSY if current->cpu_cache is already set, except we allow > replacing the pointer. Sounds fair. What is the recommended typing for "ptr" then ? uint32_t ** or uint32_t * ? It would be expected to pass a "uint32_t *" for the set operation, but the "get" operation requires a "uint32_t **". Also, I'd be tempted to put the GET/SET operation selector as a first parameter. Thanks, Mathieu > > Thanks, > > tglx -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com