[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20060726114534.GG32243@opteron.random>
Date: Wed, 26 Jul 2006 13:45:34 +0200
From: andrea@...share.com
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Chuck Ebbert <76306.1226@...puserve.com>,
"bruce@...rew.cmu.edu" <bruce@...rew.cmu.edu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Arjan van de Ven <arjan@...radead.org>,
Adrian Bunk <bunk@...sta.de>,
Lee Revell <rlrevell@...-job.com>,
Linus Torvalds <torvalds@...l.org>
Subject: Re: [PATCH] TIF_NOTSC and SECCOMP prctl
On Wed, Jul 26, 2006 at 10:07:39AM +0200, Ingo Molnar wrote:
>
> * andrea@...share.com <andrea@...share.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.
-
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