From: Frederic Weisbecker <fweisbec@gmail.com>
To: "K.Prasad" <prasad@linux.vnet.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [Patch 05/12] Use wrapper routines around debug registers in processor related functions
Date: Sat, 30 May 2009 20:37:10 +0200 [thread overview]
Message-ID: <20090530183709.GA8739@nowhere> (raw)
In-Reply-To: <20090530105129.GF9512@in.ibm.com>
On Sat, May 30, 2009 at 04:21:29PM +0530, K.Prasad wrote:
> This patch enables the use of wrapper routines to access the debug/breakpoint
> registers.
>
> Original-patch-by: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
> Reviewed-by: Alan Stern <stern@rowland.harvard.edu>
> ---
> arch/x86/kernel/smpboot.c | 3 +++
> arch/x86/power/cpu_32.c | 16 +++-------------
> arch/x86/power/cpu_64.c | 15 +++------------
> 3 files changed, 9 insertions(+), 25 deletions(-)
>
> Index: linux-2.6-tip.hbkpt/arch/x86/kernel/smpboot.c
> ===================================================================
> --- linux-2.6-tip.hbkpt.orig/arch/x86/kernel/smpboot.c
> +++ linux-2.6-tip.hbkpt/arch/x86/kernel/smpboot.c
> @@ -63,6 +63,7 @@
> #include <asm/apic.h>
> #include <asm/setup.h>
> #include <asm/uv/uv.h>
> +#include <asm/debugreg.h>
> #include <linux/mc146818rtc.h>
>
> #include <asm/smpboot_hooks.h>
> @@ -326,6 +327,7 @@ notrace static void __cpuinit start_seco
> setup_secondary_clock();
>
> wmb();
> + load_debug_registers();
> cpu_idle();
> }
>
> @@ -1252,6 +1254,7 @@ void cpu_disable_common(void)
> remove_cpu_from_maps(cpu);
> unlock_vector_lock();
> fixup_irqs();
> + hw_breakpoint_disable();
> }
>
> int native_cpu_disable(void)
> Index: linux-2.6-tip.hbkpt/arch/x86/power/cpu_32.c
> ===================================================================
> --- linux-2.6-tip.hbkpt.orig/arch/x86/power/cpu_32.c
> +++ linux-2.6-tip.hbkpt/arch/x86/power/cpu_32.c
> @@ -13,6 +13,7 @@
> #include <asm/mce.h>
> #include <asm/xcr.h>
> #include <asm/suspend.h>
> +#include <asm/debugreg.h>
>
> static struct saved_context saved_context;
>
> @@ -48,6 +49,7 @@ static void __save_processor_state(struc
> ctxt->cr2 = read_cr2();
> ctxt->cr3 = read_cr3();
> ctxt->cr4 = read_cr4_safe();
> + hw_breakpoint_disable();
> }
>
> /* Needed by apm.c */
> @@ -80,19 +82,7 @@ static void fix_processor_context(void)
> load_TR_desc(); /* This does ltr */
> load_LDT(¤t->active_mm->context); /* This does lldt */
>
> - /*
> - * Now maybe reload the debug registers
> - */
> - if (current->thread.debugreg7) {
> - set_debugreg(current->thread.debugreg0, 0);
> - set_debugreg(current->thread.debugreg1, 1);
> - set_debugreg(current->thread.debugreg2, 2);
> - set_debugreg(current->thread.debugreg3, 3);
> - /* no 4 and 5 */
> - set_debugreg(current->thread.debugreg6, 6);
> - set_debugreg(current->thread.debugreg7, 7);
> - }
> -
> + load_debug_registers();
This part is breaking the things in the middle.
I think the conversion from thread.debugreg0/1/2/3 to an
array should be done completely early, when you add the headers.
The problem is that your patchset iterates through those two versions
of virtual debug registers, and those two version can't be carried
well while keeping the good granularity of your patchset.
You are dropping the old version of virtual debug registers from
cpu management in favour of the new version which uses the array through
wrappers, whereas the thread code still deals with the old version.
The result, which I haven't tried, is likely to break the things
if I don't apply further patches of this series.
Of course it will build, but the breakpoints won't work anymore
with cpu hotplug or suspend because the threads management still
uses the old version of registers.
I can't apply this patchset if it induces a know regression in
the middle otherwise bisection will become impossible.
I think you need to convert all sites from
thread->debugregX to thread->debugreg[X] early in
the first patch. It will also bring your patchset into
a better logic of progression changes.
Thanks,
Frederic.
> }
>
> static void __restore_processor_state(struct saved_context *ctxt)
> Index: linux-2.6-tip.hbkpt/arch/x86/power/cpu_64.c
> ===================================================================
> --- linux-2.6-tip.hbkpt.orig/arch/x86/power/cpu_64.c
> +++ linux-2.6-tip.hbkpt/arch/x86/power/cpu_64.c
> @@ -16,6 +16,7 @@
> #include <asm/mtrr.h>
> #include <asm/xcr.h>
> #include <asm/suspend.h>
> +#include <asm/debugreg.h>
>
> static void fix_processor_context(void);
>
> @@ -71,6 +72,7 @@ static void __save_processor_state(struc
> ctxt->cr3 = read_cr3();
> ctxt->cr4 = read_cr4();
> ctxt->cr8 = read_cr8();
> + hw_breakpoint_disable();
> }
>
> void save_processor_state(void)
> @@ -159,16 +161,5 @@ static void fix_processor_context(void)
> load_TR_desc(); /* This does ltr */
> load_LDT(¤t->active_mm->context); /* This does lldt */
>
> - /*
> - * Now maybe reload the debug registers
> - */
> - if (current->thread.debugreg7){
> - loaddebug(¤t->thread, 0);
> - loaddebug(¤t->thread, 1);
> - loaddebug(¤t->thread, 2);
> - loaddebug(¤t->thread, 3);
> - /* no 4 and 5 */
> - loaddebug(¤t->thread, 6);
> - loaddebug(¤t->thread, 7);
> - }
> + load_debug_registers();
> }
>
next prev parent reply other threads:[~2009-05-30 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090530103857.715014561@prasadkr_t60p.in.ibm.com>
2009-05-30 10:48 ` [Patch 01/12] Prepare the code for Hardware Breakpoint interfaces K.Prasad
2009-05-30 10:49 ` [Patch 02/12] Introducing generic hardware breakpoint handler interfaces K.Prasad
2009-05-30 10:49 ` [Patch 03/12] x86 architecture implementation of Hardware Breakpoint interfaces K.Prasad
2009-05-30 10:51 ` [Patch 04/12] Modifying generic debug exception to use thread-specific debug registers K.Prasad
2009-05-30 10:51 ` [Patch 05/12] Use wrapper routines around debug registers in processor related functions K.Prasad
2009-05-30 18:37 ` Frederic Weisbecker [this message]
2009-05-30 10:52 ` [Patch 06/12] Use the new wrapper routines to access debug registers in process/thread code K.Prasad
2009-05-30 10:52 ` [Patch 07/12] Modify signal handling code to refrain from re-enabling HW Breakpoints K.Prasad
2009-05-30 10:52 ` [Patch 08/12] Modify Ptrace routines to access breakpoint registers K.Prasad
2009-05-30 10:52 ` [Patch 09/12] Cleanup HW Breakpoint registers before kexec K.Prasad
2009-05-30 10:53 ` [Patch 10/12] Sample HW breakpoint over kernel data address K.Prasad
2009-05-30 10:54 ` [Patch 11/12] ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces - v6 K.Prasad
2009-05-30 10:55 ` [Patch 12/12] Reset bits in dr6 after the corresponding exception is handled K.Prasad
[not found] <20090601180605.799735829@prasadkr_t60p.in.ibm.com>
2009-06-01 18:14 ` [Patch 05/12] Use wrapper routines around debug registers in processor related functions K.Prasad
[not found] <20090521095613.834622717@prasadkr_t60p.in.ibm.com>
2009-05-21 14:02 ` K.Prasad
[not found] <20090515105133.629980476@prasadkr_t60p.in.ibm.com>
2009-05-15 10:57 ` K.Prasad
2009-05-16 0:28 ` K.Prasad
[not found] <20090513160546.592373797@prasadkr_t60p.in.ibm.com>
2009-05-13 16:14 ` K.Prasad
[not found] <20090511114422.133566343@prasadkr_t60p.in.ibm.com>
2009-05-11 11:53 ` K.Prasad
[not found] <20090424055710.764502564@prasadkr_t60p.in.ibm.com>
2009-04-24 6:17 ` K.Prasad
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=20090530183709.GA8739@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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