From: Catalin Marinas <catalin.marinas@arm.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: Fix task tracing
Date: Mon, 15 Apr 2013 11:11:59 +0100 [thread overview]
Message-ID: <20130415101159.GA25095@localhost.cambridge.arm.com> (raw)
In-Reply-To: <1365510814-21343-1-git-send-email-cov@codeaurora.org>
On Tue, Apr 09, 2013 at 01:33:34PM +0100, Christopher Covington wrote:
> For accurate accounting pass contextidr_thread_switch the prev
> task pointer, since cpu_switch_to has at that point changed the
> the stack pointer.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> ---
> arch/arm64/kernel/process.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
> index 0337cdb..a49b25a 100644
> --- a/arch/arm64/kernel/process.c
> +++ b/arch/arm64/kernel/process.c
> @@ -315,7 +315,7 @@ struct task_struct *__switch_to(struct task_struct *prev,
> /* the actual thread switch */
> last = cpu_switch_to(prev, next);
>
> - contextidr_thread_switch(next);
> + contextidr_thread_switch(prev);
The original code was indeed wrong but using prev isn't any better. For
a newly created thread, prev is probably 0 (if it's in a register,
cpu_context has been zeroed by copy_thread()) or some random stack
value.
So we either use current or move the call before cpu_switch_to() (I
would go for the former).
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Fix task tracing
Date: Mon, 15 Apr 2013 11:11:59 +0100 [thread overview]
Message-ID: <20130415101159.GA25095@localhost.cambridge.arm.com> (raw)
In-Reply-To: <1365510814-21343-1-git-send-email-cov@codeaurora.org>
On Tue, Apr 09, 2013 at 01:33:34PM +0100, Christopher Covington wrote:
> For accurate accounting pass contextidr_thread_switch the prev
> task pointer, since cpu_switch_to has at that point changed the
> the stack pointer.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> ---
> arch/arm64/kernel/process.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
> index 0337cdb..a49b25a 100644
> --- a/arch/arm64/kernel/process.c
> +++ b/arch/arm64/kernel/process.c
> @@ -315,7 +315,7 @@ struct task_struct *__switch_to(struct task_struct *prev,
> /* the actual thread switch */
> last = cpu_switch_to(prev, next);
>
> - contextidr_thread_switch(next);
> + contextidr_thread_switch(prev);
The original code was indeed wrong but using prev isn't any better. For
a newly created thread, prev is probably 0 (if it's in a register,
cpu_context has been zeroed by copy_thread()) or some random stack
value.
So we either use current or move the call before cpu_switch_to() (I
would go for the former).
--
Catalin
next prev parent reply other threads:[~2013-04-15 10:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 18:01 [PATCH] arm64: Fix task tracing Christopher Covington
2013-04-03 18:01 ` Christopher Covington
2013-04-03 18:04 ` Will Deacon
2013-04-03 18:04 ` Will Deacon
2013-04-08 14:42 ` Christopher Covington
2013-04-08 14:42 ` Christopher Covington
2013-04-08 15:31 ` Will Deacon
2013-04-08 15:31 ` Will Deacon
2013-04-09 12:33 ` [PATCH v2] " Christopher Covington
2013-04-09 12:33 ` Christopher Covington
2013-04-10 11:41 ` Will Deacon
2013-04-10 11:41 ` Will Deacon
2013-04-10 13:12 ` Christopher Covington
2013-04-10 13:12 ` Christopher Covington
2013-04-15 10:11 ` Catalin Marinas [this message]
2013-04-15 10:11 ` Catalin Marinas
2013-04-15 10:45 ` Will Deacon
2013-04-15 10:45 ` Will Deacon
2013-04-15 10:58 ` Catalin Marinas
2013-04-15 10:58 ` Catalin Marinas
2013-04-15 11:43 ` Catalin Marinas
2013-04-15 11:43 ` Catalin Marinas
2013-04-15 13:09 ` Christopher Covington
2013-04-15 13:09 ` Christopher Covington
2013-04-15 15:23 ` Catalin Marinas
2013-04-15 15:23 ` Catalin Marinas
2013-04-15 13:19 ` Will Deacon
2013-04-15 13:19 ` Will Deacon
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=20130415101159.GA25095@localhost.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.