Re: [x86] only print out DR registers if they are not power-ondefaults.
From: Dave Jones
Date: Tue Jun 18 2013 - 10:08:09 EST
On Tue, Jun 18, 2013 at 10:43:56AM +0200, Borislav Petkov wrote:
> On Tue, Jun 18, 2013 at 12:11:32AM -0400, Dave Jones wrote:
> > The DR registers are rarely useful when decoding oopses.
> > With screen real estate during oopses at a premium, we can save two lines
> > by only printing out these registers when they are set to something other
> > than they power-on state.
> Makes sense, except...
> > Signed-off-by: Dave Jones <davej@xxxxxxxxxx>
> > diff -durpN '--exclude-from=/home/davej/.exclude' /home/davej/src/kernel/git-trees/linux/arch/x86/kernel/process_64.c linux-dj/arch/x86/kernel/process_64.c
> > --- /home/davej/src/kernel/git-trees/linux/arch/x86/kernel/process_64.c 2013-05-01 10:02:52.064151923 -0400
> > +++ linux-dj/arch/x86/kernel/process_64.c 2013-05-06 20:35:09.219868881 -0400
> > @@ -105,11 +105,18 @@ void __show_regs(struct pt_regs *regs, i
> > get_debugreg(d0, 0);
> > get_debugreg(d1, 1);
> > get_debugreg(d2, 2);
> > - printk(KERN_DEFAULT "DR0: %016lx DR1: %016lx DR2: %016lx\n", d0, d1, d2);
> > get_debugreg(d3, 3);
> > get_debugreg(d6, 6);
> > get_debugreg(d7, 7);
> > +
> > + /* Only print out debug registers if they are in their non-default state. */
> > + if ((d0 == 0) && (d1 == 0) && (d2 == 0) && (d3 == 0) &&
> > + (d6 & ~DR6_RESERVED) && (d7 == 0x400))
> ... I'm not sure about %dr6. So we're not dumping %dr6 when, a.o.
> any of the bits in the bit slices [3:0], [15:13] are set (bit 12
> is Read-As-Zero). Now those mean stuff like Breakpoint-Condition
> Detected or Debug-Register-Access Detected and so on and I think this is
> meaningful information.
> So actually, we wouldn't want to dump %dr6 when its contents are its
> default contents, i.e, 0xffff0ff0, i.e. the test should be:
> (d6 == DR6_RESERVED)
My intent here was to ignore cases where the reserved bits haven't been set.
I occasionally see DR6: 00000000fffe0ff0 for eg.
But maybe you're right, and that is a clue and is worth printing ?
I can't personally recall ever diagnosing a bug using those register dumps
in the last 15 years.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/