linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Cyrill Gorcunov <gorcunov@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	David Miller <davem@davemloft.net>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH v2] x86: make DR*_RESERVED unsigned long
Date: Fri, 26 Apr 2013 19:15:26 +0200	[thread overview]
Message-ID: <20130426171526.GA30875@redhat.com> (raw)
In-Reply-To: <517AAED5.7040400@zytor.com>

On 04/26, H. Peter Anvin wrote:
>
> On 04/26/2013 09:38 AM, Oleg Nesterov wrote:
> >
> > 	- do_debug:
> >
> > 		dr6 &= ~DR6_RESERVED;
> >
> > 	  this also wrongly clears 32-63 bits. Fortunately these
> > 	  bits are reserved and must be zero.
>
> I don't think this is wrongly at all.

OK, I meant that it also clears the bits that are not specified in
DR6_RESERVED mask.

> The whole point is to mask out
> the bits that the handler doesn't want to deal with, so masking out the
> reserved bits [63:32] seems reasonable to me.

Then we should do

	- #define DR6_RESERVED    0xFFFF0FF0
	+ #define DR6_RESERVED    0xFFFFFFFFFFFF0FF0

?

or what? (just in case, I will happily agree with "do nothing" ;)

> The comment should probably be corrected, though.

Which one?

	/* Define reserved bits in DR6 which are always set to 1 */
	#define DR6_RESERVED    (0xFFFF0FF0UL)

	/* Filter out all the reserved bits which are preset to 1 */
	dr6 &= ~DR6_RESERVED;

I guess both should be updated then. But if I read the doc correctly
the lower reserved bits are set to 1.

However do_debug() does set_debugreg(0, 6) and this looks correct, the
doc says "debug handlers should clear the register before returning to
the interrupted task".

Oleg.


  reply	other threads:[~2013-04-26 17:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+55aFwpLu0qNms=hkQr43yqD0K9DgESNm91OEWKT1ZuT8MU6Q@mail.gmail.com>
2013-04-23  0:23 ` Unsigned widening casts of binary "not" operations Linus Torvalds
2013-04-23  8:59   ` David Laight
2013-04-23 14:29     ` Linus Torvalds
2013-04-23 15:24       ` David Laight
2013-04-23 15:42         ` Linus Torvalds
2013-04-23 15:52           ` Theodore Ts'o
2013-04-23 16:05             ` Linus Torvalds
2013-04-23 17:37           ` David Miller
2013-04-23 17:52             ` Linus Torvalds
2013-04-23 17:56               ` David Miller
2013-04-23 18:21                 ` Linus Torvalds
2013-04-24 12:36             ` Geert Uytterhoeven
2013-04-23  0:32 ` H. Peter Anvin
2013-04-23 13:00 ` Theodore Ts'o
2013-04-24  7:26 ` Ingo Molnar
2013-04-24  7:47   ` Cyrill Gorcunov
2013-04-25  1:13     ` Lin Ming
2013-04-24 17:07   ` [PATCH] x86: make DR*_RESERVED unsigned long Oleg Nesterov
2013-04-24 18:45     ` H. Peter Anvin
2013-04-25 14:48       ` Oleg Nesterov
2013-04-26 16:38         ` [PATCH v2] " Oleg Nesterov
2013-04-26 16:44           ` H. Peter Anvin
2013-04-26 17:15             ` Oleg Nesterov [this message]
2013-04-27 14:45               ` Oleg Nesterov
2013-04-27 16:20                 ` H. Peter Anvin
2013-04-28  0:58                 ` Frederic Weisbecker
2013-04-28 17:27                   ` Oleg Nesterov
2013-04-28 17:32                     ` H. Peter Anvin
2013-04-28 17:39                       ` Oleg Nesterov
2013-04-28 17:43                         ` H. Peter Anvin
2013-04-24 22:48     ` [PATCH] " Frederic Weisbecker
2013-04-24 23:06       ` H. Peter Anvin
2013-04-24 23:31         ` Frederic Weisbecker
2013-04-25  1:20           ` H. Peter Anvin

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=20130426171526.GA30875@redhat.com \
    --to=oleg@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=x86@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 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).