[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YQwZGjjugfJTV2s6@hirez.programming.kicks-ass.net>
Date: Thu, 5 Aug 2021 19:00:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Eugene Syromiatnikov <esyr@...hat.com>
Cc: joel@...lfernandes.org, chris.hyser@...cle.com, joshdon@...gle.com,
mingo@...nel.org, vincent.guittot@...aro.org,
valentin.schneider@....com, mgorman@...e.de,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
linux-api@...r.kernel.org, ldv@...ace.io
Subject: Re: [PATCH 18/19] sched: prctl() core-scheduling interface
On Thu, Aug 05, 2021 at 06:53:19PM +0200, Eugene Syromiatnikov wrote:
> On Thu, Apr 22, 2021 at 02:05:17PM +0200, Peter Zijlstra wrote:
> > API:
> >
> > prctl(PR_SCHED_CORE, PR_SCHED_CORE_GET, tgtpid, pidtype, &cookie)
> > prctl(PR_SCHED_CORE, PR_SCHED_CORE_CREATE, tgtpid, pidtype, NULL)
> > prctl(PR_SCHED_CORE, PR_SCHED_CORE_SHARE_TO, tgtpid, pidtype, NULL)
> > prctl(PR_SCHED_CORE, PR_SCHED_CORE_SHARE_FROM, srcpid, pidtype, NULL)
> >
> > where 'tgtpid/srcpid == 0' implies the current process and pidtype is
> > kernel enum pid_type {PIDTYPE_PID, PIDTYPE_TGID, PIDTYPE_PGID, ...}.
>
> It means that enum pid_tipe has to be a part of UAPI now. Would you
> like to address it, or rather I'd send a patch?
Please send a patch; I'm more sparse than usual atm.
Powered by blists - more mailing lists