From: Peter Zijlstra <peterz@infradead.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Tony Luck <tony.luck@intel.com>,
Christopherson Sean J <sean.j.christopherson@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH RFC v2 2/4] x86/bus_lock: Handle warn and fatal in #DB for bus lock
Date: Thu, 29 Oct 2020 10:27:47 +0100 [thread overview]
Message-ID: <20201029092747.GI2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201028202804.3562179-3-fenghua.yu@intel.com>
On Wed, Oct 28, 2020 at 08:28:02PM +0000, Fenghua Yu wrote:
> diff --git a/arch/x86/include/uapi/asm/debugreg.h b/arch/x86/include/uapi/asm/debugreg.h
> index d95d080b30e3..61078319fc6c 100644
> --- a/arch/x86/include/uapi/asm/debugreg.h
> +++ b/arch/x86/include/uapi/asm/debugreg.h
> @@ -16,7 +16,7 @@
> are either reserved or not of interest to us. */
>
> /* Define reserved bits in DR6 which are always set to 1 */
> -#define DR6_RESERVED (0xFFFF0FF0)
> +#define DR6_RESERVED (0xFFFF07F0)
NAK
next prev parent reply other threads:[~2020-10-29 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 20:28 [PATCH RFC v2 0/4] x86/bus_lock: Enable bus lock detection Fenghua Yu
2020-10-28 20:28 ` [PATCH RFC v2 1/4] x86/cpufeatures: Enumerate #DB for " Fenghua Yu
2020-10-28 20:28 ` [PATCH RFC v2 2/4] x86/bus_lock: Handle warn and fatal in #DB for bus lock Fenghua Yu
2020-10-29 9:27 ` Peter Zijlstra [this message]
2020-10-30 19:39 ` Fenghua Yu
2020-10-28 20:28 ` [PATCH RFC v2 3/4] x86/bus_lock: Set rate limit " Fenghua Yu
2020-10-28 20:28 ` [PATCH RFC v2 4/4] Documentation: Change doc for split_lock_detect parameter Fenghua Yu
2020-10-29 5:14 ` Randy Dunlap
2020-10-30 19:42 ` Fenghua Yu
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=20201029092747.GI2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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
all inboxes | Powered by JetHome®