From: Namhyung Kim <namhyung@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@lge.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] context_tracking: Add comments on interface and internals
Date: Wed, 16 Jan 2013 22:04:43 +0900 [thread overview]
Message-ID: <87wqvdl1n8.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1358339577-28766-1-git-send-email-fweisbec@gmail.com> (Frederic Weisbecker's message of "Wed, 16 Jan 2013 13:32:57 +0100")
Hi Frederic,
On Wed, 16 Jan 2013 13:32:57 +0100, Frederic Weisbecker wrote:
> This subsystem lacks many explanations on its purpose and
> design. Add these missing comments.
>
> v3: Fix the "hook" based naming as per Ingo's suggestion
[snip]
> +/**
> + * context_tracking_task_switch - context switch the syscall callbacks
To be more kernel-doc-friendly, it'd better adding descriptions for
arguments too:
@prev: the task that is being switched out
@next: the task we are going to switch to
Thanks,
Namhyung
> + *
> + * The context tracking uses the syscall slow path to implement its user-kernel
> + * boundaries probes on syscalls. This way it doesn't impact the syscall fast
> + * path on CPUs that don't do context tracking.
> + *
> + * But we need to clear the flag on the previous task because it may later
> + * migrate to some CPU that doesn't do the context tracking. As such the TIF
> + * flag may not be desired there.
> + */
> void context_tracking_task_switch(struct task_struct *prev,
> struct task_struct *next)
> {
next prev parent reply other threads:[~2013-01-16 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 12:32 Frederic Weisbecker
2013-01-16 13:04 ` Namhyung Kim [this message]
2013-01-16 14:58 ` Frederic Weisbecker
2013-01-16 16:16 ` [PATCH v4] " Frederic Weisbecker
2013-01-16 21:18 ` Andrew Morton
2013-01-16 21:49 ` Steven Rostedt
2013-01-16 22:06 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2012-12-13 20:57 [PATCH] " Frederic Weisbecker
2012-12-13 21:18 ` Andrew Morton
2012-12-13 22:50 ` Frederic Weisbecker
2012-12-13 23:00 ` Andrew Morton
2012-12-13 23:10 ` Frederic Weisbecker
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=87wqvdl1n8.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=fweisbec@gmail.com \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®