From: andrea@cpushare.com
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Chuck Ebbert <76306.1226@compuserve.com>,
"bruce@andrew.cmu.edu" <bruce@andrew.cmu.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arjan van de Ven <arjan@infradead.org>,
Adrian Bunk <bunk@stusta.de>, Lee Revell <rlrevell@joe-job.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] TIF_NOTSC and SECCOMP prctl
Date: Wed, 26 Jul 2006 13:45:34 +0200 [thread overview]
Message-ID: <20060726114534.GG32243@opteron.random> (raw)
In-Reply-To: <20060726080739.GA10574@elte.hu>
On Wed, Jul 26, 2006 at 10:07:39AM +0200, Ingo Molnar wrote:
>
> * andrea@cpushare.com <andrea@cpushare.com> wrote:
>
> > Here a repost of the last seccomp patch against current mainline
> > including the preempt fix. This changes the seccomp API from
> > /proc/<pid>/seccomp to a prctl (this will produce a smaller kernel)
> > and it adds a TIF_NOTSC that seccomp sets. Only the current task can
> > call disable_TSC (obviously because it hasn't a task_t param). This
> > includes Chuck's patch to give zero runtime cost to the notsc feature.
>
> please send a patch-queue that is properly split-up: the bugfix, the API
> change and the TIF_NOTSC improvement.
Which bugfix do you mean? If you mean the preempt fix for the NOTSC
improvement it makes no sense to split it up from the NOTSC
part. There are no other bugfixes (the reduction of the notsc window
isn't strictly a bugfix, since the feature already helped).
I can split the API change from the NOTSC feature, I'll wait some more
days in the hope this one goes in. If it doesn't go in I'll follow
your suggestion and I'll try again later with the split up in the hope
to increase my chances.
>From my point of view it's not urgent to merge it, it's just the
anti-seccomp advocates that should want this patch being merged
urgently.
next prev parent reply other threads:[~2006-07-26 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 10:20 [PATCH] TIF_NOTSC and SECCOMP prctl Chuck Ebbert
2006-07-18 13:29 ` andrea
2006-07-25 21:44 ` andrea
2006-07-26 8:07 ` Ingo Molnar
2006-07-26 11:45 ` andrea [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 14:17 [patch] let CONFIG_SECCOMP default to n andrea
2006-07-11 14:32 ` Arjan van de Ven
2006-07-11 15:31 ` andrea
2006-07-11 16:24 ` Alan Cox
2006-07-12 15:43 ` Andi Kleen
2006-07-12 21:07 ` Ingo Molnar
2006-07-13 1:51 ` Andrew Morton
2006-07-13 7:44 ` James Bruce
2006-07-13 8:34 ` andrea
2006-07-13 9:18 ` Andrew Morton
2006-07-14 6:09 ` [PATCH] TIF_NOTSC and SECCOMP prctl andrea
2006-07-14 6:27 ` Andrew Morton
2006-07-14 6:33 ` andrea
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=20060726114534.GG32243@opteron.random \
--to=andrea@cpushare.com \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bruce@andrew.cmu.edu \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.org \
/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