linux-kernel - Re: [context tracking subsystem] Re: [GIT PULL rcu/next] One more RCU commit for 3.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 10 Dec 2012 17:29:33 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	paulmck@...ux.vnet.ibm.com, Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org
Subject: Re: [context tracking subsystem] Re: [GIT PULL rcu/next] One more RCU
 commit for 3.8

2012/12/10 Paul E. McKenney <paulmck@...ux.vnet.ibm.com>:
> On Sat, Dec 08, 2012 at 03:37:57PM +0100, Ingo Molnar wrote:
>>
>> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
>>
>> > Hello, Ingo,
>> >
>> > Could you please pull one more commit?  This is an update to Frederic
>> > Weisbecker's context-tracking subsystem that is another stepping stone
>> > towards adaptive-idle and tickless userspace execution.  This has been
>> > subjected to -next testing.  It does give two checkpatch.pl errors,
>> > but these are on cpp macro definitions used within assembly code -- and
>> > following checkpatch.pl's suggestions would result in assembler errors.
>> > (I have reported this to Andy Whitcroft, checkpatch.pl's maintainer.)
>> >
>> > These changes are available in the git repository at:
>> >   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
>> >
>> >                                                     Thanx, Paul
>> >
>> > ---------------->
>> > Frederic Weisbecker (1):
>> >       context_tracking: New context tracking susbsystem
>> >
>> >  arch/Kconfig                                       |   15 ++--
>> >  arch/x86/Kconfig                                   |    2 +-
>> >  arch/x86/include/asm/{rcu.h => context_tracking.h} |   15 ++--
>> >  arch/x86/kernel/entry_64.S                         |    2 +-
>> >  arch/x86/kernel/ptrace.c                           |    8 +-
>> >  arch/x86/kernel/signal.c                           |    5 +-
>> >  arch/x86/kernel/traps.c                            |    2 +-
>> >  arch/x86/mm/fault.c                                |    2 +-
>> >  include/linux/context_tracking.h                   |   18 ++++
>> >  include/linux/rcupdate.h                           |    2 -
>> >  init/Kconfig                                       |   28 ++++----
>> >  kernel/Makefile                                    |    1 +
>> >  kernel/context_tracking.c                          |   83 ++++++++++++++++++++
>> >  kernel/rcutree.c                                   |   64 +---------------
>> >  kernel/sched/core.c                                |   11 ++-
>> >  15 files changed, 150 insertions(+), 108 deletions(-)
>> >  rename arch/x86/include/asm/{rcu.h => context_tracking.h} (63%)
>> >  create mode 100644 include/linux/context_tracking.h
>> >  create mode 100644 kernel/context_tracking.c
>>
>> Pulled it and pushed it out earlier this week.
>>
>> One issue I wanted to raise on a bit wider forum was the
>> introduction of the (small) kernel/context_tracking.c subsystem.
>>
>> It makes sense to me, but I've Cc:-ed Linus and Andrew, in case
>> they have a different opinion.
>
> And it does appear that Frederic and I have a bit more explaining to do.  ;-)

Right :-)

Andrew strongly suggested us to give some more description of that
thing and the role and semantics of the new APIs. I indeed overlooked
that part. I'll send a patch soon.
--
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/