From: tip-bot for Paul Mundt <lethal@linux-sh.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
stern@rowland.harvard.edu, lethal@linux-sh.org,
fweisbec@gmail.com, tglx@linutronix.de,
prasad@linux.vnet.ibm.com, mingo@elte.hu
Subject: [tip:perf/core] x86/hw-breakpoints: Actually flush thread breakpoints in flush_thread().
Date: Sat, 21 Nov 2009 13:36:38 GMT [thread overview]
Message-ID: <tip-41a48d14f6991020c9bb6b93e289ca5b411ed09a@git.kernel.org> (raw)
In-Reply-To: <20091005102306.GA7889@linux-sh.org>
Commit-ID: 41a48d14f6991020c9bb6b93e289ca5b411ed09a
Gitweb: http://git.kernel.org/tip/41a48d14f6991020c9bb6b93e289ca5b411ed09a
Author: Paul Mundt <lethal@linux-sh.org>
AuthorDate: Mon, 5 Oct 2009 19:23:06 +0900
Committer: Frederic Weisbecker <fweisbec@gmail.com>
CommitDate: Tue, 3 Nov 2009 18:05:44 +0100
x86/hw-breakpoints: Actually flush thread breakpoints in flush_thread().
flush_thread() tries to do a TIF_DEBUG check before calling in to
flush_thread_hw_breakpoint() (which subsequently clears the thread flag),
but for some reason, the x86 code is manually clearing TIF_DEBUG
immediately before the test, so this path will never be taken.
This kills off the erroneous clear_tsk_thread_flag() and lets
flush_thread_hw_breakpoint() actually get invoked.
Presumably folks were getting lucky with testing and the
free_thread_info() -> free_thread_xstate() path was taking care of the
flush there.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Acked-by: "K.Prasad" <prasad@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Alan Stern <stern@rowland.harvard.edu>
LKML-Reference: <20091005102306.GA7889@linux-sh.org>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
arch/x86/kernel/process.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index 2275ce5..cf8ee00 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -107,8 +107,6 @@ void flush_thread(void)
}
#endif
- clear_tsk_thread_flag(tsk, TIF_DEBUG);
-
if (unlikely(test_tsk_thread_flag(tsk, TIF_DEBUG)))
flush_thread_hw_breakpoint(tsk);
memset(tsk->thread.tls_array, 0, sizeof(tsk->thread.tls_array));
prev parent reply other threads:[~2009-11-21 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 10:23 [PATCH -tip] x86: hw-breakpoints: " Paul Mundt
2009-10-05 10:49 ` K.Prasad
2009-10-09 3:40 ` Paul Mundt
2009-10-09 7:53 ` Frederic Weisbecker
2009-10-17 23:42 ` Frederic Weisbecker
2009-10-18 6:25 ` Paul Mundt
2009-10-18 16:43 ` Frederic Weisbecker
2009-10-19 19:48 ` Frederic Weisbecker
2009-10-19 23:24 ` Paul Mundt
2009-10-20 7:49 ` Frederic Weisbecker
2009-11-21 13:36 ` tip-bot for Paul Mundt [this message]
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=tip-41a48d14f6991020c9bb6b93e289ca5b411ed09a@git.kernel.org \
--to=lethal@linux-sh.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=prasad@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
/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
Powered by JetHome