From: Peter Zijlstra <peterz@infradead.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] perf/x86/intel: Don't accidentally clear high bits in bdw_limit_period()
Date: Mon, 19 Mar 2018 08:35:30 +0000 [thread overview]
Message-ID: <20180319083530.GE4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180317115216.GB4035@mwanda>
On Sat, Mar 17, 2018 at 02:52:16PM +0300, Dan Carpenter wrote:
> We intended to clear the lowest 6 bits but because of a type bug we
> clear the high 32 bits as well. Andi says that periods are rarely more
> than U32_MAX so this bug probably doesn't have a huge runtime impact.
Thanks Dan!
prev parent reply other threads:[~2018-03-19 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 11:52 [PATCH] perf/x86/intel: Don't accidentally clear high bits in bdw_limit_period() Dan Carpenter
2018-03-19 8:35 ` Peter Zijlstra [this message]
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=20180319083530.GE4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kernel-janitors@vger.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