From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Xin Li (Intel)" <xin@zytor.com>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin (Intel)" <hpa@zytor.com>,
Sohil Mehta <sohil.mehta@intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/traps: Initialize DR7 by writing its architectural reset value
Date: Thu, 26 Jun 2025 06:32:01 -0700 [thread overview]
Message-ID: <aF1L0fbNL6xE0C8d@google.com> (raw)
In-Reply-To: <20250626090439.GBaF0NJ34n065_4vb-@fat_crate.local>
On Thu, Jun 26, 2025, Borislav Petkov wrote:
> On Tue, Jun 24, 2025 at 08:35:22PM -0000, tip-bot2 for Xin Li (Intel) wrote:
> > The following commit has been merged into the x86/urgent branch of tip:
> >
> > Commit-ID: fa7d0f83c5c4223a01598876352473cb3d3bd4d7
> > Gitweb: https://git.kernel.org/tip/fa7d0f83c5c4223a01598876352473cb3d3bd4d7
> > Author: Xin Li (Intel) <xin@zytor.com>
> > AuthorDate: Fri, 20 Jun 2025 16:15:04 -07:00
> > Committer: Dave Hansen <dave.hansen@linux.intel.com>
> > CommitterDate: Tue, 24 Jun 2025 13:15:52 -07:00
> >
> > x86/traps: Initialize DR7 by writing its architectural reset value
> >
> > Initialize DR7 by writing its architectural reset value to always set
> > bit 10, which is reserved to '1', when "clearing" DR7 so as not to
> > trigger unanticipated behavior if said bit is ever unreserved, e.g. as
> > a feature enabling flag with inverted polarity.
>
> OMG, who wrote that "text"?
I'm pretty sure I can take credit for the latter half. You're welcome :-)
next prev parent reply other threads:[~2025-06-26 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 20:35 [tip: x86/urgent] x86/traps: Initialize DR7 by writing its architectural reset value tip-bot2 for Xin Li (Intel)
2025-06-26 9:04 ` Borislav Petkov
2025-06-26 13:32 ` Sean Christopherson [this message]
2025-06-26 13:56 ` Borislav Petkov
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=aF1L0fbNL6xE0C8d@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sohil.mehta@intel.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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