From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Peter Zijlstra <peterz@infradead.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Oleg Nesterov" <oleg@redhat.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
darren@dvhart.com, johan.eker@ericsson.com, p.faure@akatech.ch,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Claudio Scordino" <claudio@evidence.eu.com>,
"Michael Trimarchi" <michael@amarulasolutions.com>,
"Fabio Checconi" <fchecconi@gmail.com>,
"Tommaso Cucinotta" <tommaso.cucinotta@sssup.it>,
"Juri Lelli" <juri.lelli@gmail.com>,
nicola.manica@disi.unitn.it, luca.abeni@unitn.it,
"Dhaval Giani" <dhaval.giani@gmail.com>,
hgu1972@gmail.com, "Paul McKenney" <paulmck@linux.vnet.ibm.com>,
"Dario Faggioli" <raistlin@linux.it>,
insop.song@gmail.com, liming.wang@windriver.com,
"John Kacur" <jkacur@redhat.com>
Subject: Re: [PATCH 01/13] sched: Add 3 new scheduler syscalls to support an extended scheduling parameters ABI
Date: Sun, 26 Jan 2014 10:48:48 +0100 [thread overview]
Message-ID: <CAMuHMdU574ojqZ2wK4bAM_c8_1GCHRDPpco+iF-rHaF8Kdbaxg@mail.gmail.com> (raw)
In-Reply-To: <20131217123352.692059839@infradead.org>
On Tue, Dec 17, 2013 at 1:27 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> From: Dario Faggioli <raistlin@linux.it>
>
> Add the syscalls needed for supporting scheduling algorithms
> with extended scheduling parameters (e.g., SCHED_DEADLINE).
> - defines and implements the new scheduling related syscalls that
> manipulate it, i.e., sched_setscheduler2(), sched_setattr()
> and sched_getattr().
> Syscalls are introduced for x86 (32 and 64 bits) and ARM only, as a
> proof of concept and for developing and testing purposes. Making them
> available on other architectures is straightforward.
Please cc linux-arch on new syscalls.
They're now in mainline, and in the end there are only 2 (sched_setattr() and
sched_getattr()).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2014-01-26 9:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20131217123352.692059839@infradead.org>]
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=CAMuHMdU574ojqZ2wK4bAM_c8_1GCHRDPpco+iF-rHaF8Kdbaxg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=claudio@evidence.eu.com \
--cc=darren@dvhart.com \
--cc=dhaval.giani@gmail.com \
--cc=fchecconi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hgu1972@gmail.com \
--cc=insop.song@gmail.com \
--cc=jkacur@redhat.com \
--cc=johan.eker@ericsson.com \
--cc=juri.lelli@gmail.com \
--cc=liming.wang@windriver.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=michael@amarulasolutions.com \
--cc=mingo@redhat.com \
--cc=nicola.manica@disi.unitn.it \
--cc=oleg@redhat.com \
--cc=p.faure@akatech.ch \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@sssup.it \
/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;
as well as URLs for NNTP newsgroup(s).