linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Roland McGrath <roland@redhat.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Vegard Nossum <vegardno@ifi.uio.no>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [RFC Patch 1/2][Bugfix][x86][hw-breakpoint] Clear reserved bits of DR6 in do_debug()
Date: Fri, 1 Jan 2010 00:19:49 +0530	[thread overview]
Message-ID: <20091231184949.GB3676@in.ibm.com> (raw)
In-Reply-To: <20091230234458.GA23808@nowhere>

On Thu, Dec 31, 2009 at 12:45:00AM +0100, Frederic Weisbecker wrote:
> On Sat, Dec 26, 2009 at 11:57:25PM +0530, K.Prasad wrote:
> > Clear the reserved bits from the stored copy of debug status register (DR6).
> > This will help easy bitwise operations.
> > 
> > Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
> > ---
> >  arch/x86/include/asm/debugreg.h |    3 +++
> >  arch/x86/kernel/traps.c         |    3 +++
> >  2 files changed, 6 insertions(+)
> > 
> > Index: linux-2.6-tip/arch/x86/include/asm/debugreg.h
> > ===================================================================
> > --- linux-2.6-tip.orig/arch/x86/include/asm/debugreg.h
> > +++ linux-2.6-tip/arch/x86/include/asm/debugreg.h
> > @@ -14,6 +14,9 @@
> >     which debugging register was responsible for the trap.  The other bits
> >     are either reserved or not of interest to us. */
> >  
> > +/* Define reserved bits in DR6 which are always set to 1 */
> > +#define DR6_RESERVED	(0xFFFF0FF0)
> > +
> 
> 
> The 12th bit seems to be also reserved.
> Shouldn't it be 0xffff1ff0 ?
> 

The 12th bit is reserved to be 0 always.

> What kind of bitwise operations do you think it could help?
> 
> All of the operations I can find on dr6 are simple masks
> test/set/clear.
> 

As you found out later, this bitmask helps us in
hw_breakpoint_handler().

Thanks,
K.Prasad


  reply	other threads:[~2009-12-31 18:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091226175533.149765731@linux.vnet.ibm.com>
2009-12-26 18:27 ` [RFC Patch 1/2][Bugfix][x86][hw-breakpoint] Clear reserved bits of DR6 in do_debug() K.Prasad
2009-12-30 23:45   ` Frederic Weisbecker
2009-12-31 18:49     ` K.Prasad [this message]
2010-01-10  3:22       ` Frederic Weisbecker
2009-12-26 18:28 ` [RFC Patch 2/2][Bugfix][x86][hw-breakpoint] Fix return-code to notifier chain in hw_breakpoint_handler K.Prasad
2009-12-31  0:33   ` Frederic Weisbecker
2009-12-31  0:38   ` Frederic Weisbecker
2009-12-31 19:02     ` K.Prasad
2010-01-10  3:18       ` Frederic Weisbecker
2010-01-11 19:15         ` Jan Kiszka
2010-01-16 19:41           ` K.Prasad
2010-01-20  6:01             ` K.Prasad
2010-01-22  9:14               ` Jan Kiszka
2010-01-22  9:21                 ` K.Prasad
2010-01-25 22:21                   ` Frederic Weisbecker
2010-01-27 10:29                     ` K.Prasad
2009-12-31  0:44   ` Frederic Weisbecker
2010-01-25 22:11   ` Frederic Weisbecker
2010-01-27 10:28     ` K.Prasad
2010-01-27 16:11       ` 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=20091231184949.GB3676@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=roland@redhat.com \
    --cc=stern@rowland.harvard.edu \
    --cc=vegardno@ifi.uio.no \
    /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;
as well as URLs for NNTP newsgroup(s).