From: Fenghua Yu <fenghua.yu@intel.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/resctrl: remove redundant assignment to variable chunks
Date: Tue, 7 Dec 2021 22:43:50 +0000 [thread overview]
Message-ID: <Ya/jpoUWCy5shYI6@otcwcpicx3.sc.intel.com> (raw)
In-Reply-To: <20211207223735.35173-1-colin.i.king@gmail.com>
On Tue, Dec 07, 2021 at 10:37:35PM +0000, Colin Ian King wrote:
> The variable chunks is being shifted right and re-assinged the shifted
> value which is then returned. Since chunks is not being read afterwards
> the assignment is redundant and the >>= operator can be replaced with a
> shift >> operator instead.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> arch/x86/kernel/cpu/resctrl/monitor.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/resctrl/monitor.c b/arch/x86/kernel/cpu/resctrl/monitor.c
> index c9f0f3d63f75..eaf25a234ff5 100644
> --- a/arch/x86/kernel/cpu/resctrl/monitor.c
> +++ b/arch/x86/kernel/cpu/resctrl/monitor.c
> @@ -282,7 +282,7 @@ static u64 mbm_overflow_count(u64 prev_msr, u64 cur_msr, unsigned int width)
> u64 shift = 64 - width, chunks;
>
> chunks = (cur_msr << shift) - (prev_msr << shift);
> - return chunks >>= shift;
> + return chunks >> shift;
> }
>
> static u64 __mon_event_count(u32 rmid, struct rmid_read *rr)
Reviewed-by: Fenghua Yu <fenghua.yu@intel.com>
Thanks.
-Fenghua
next prev parent reply other threads:[~2021-12-07 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 22:37 Colin Ian King
2021-12-07 22:43 ` Fenghua Yu [this message]
2021-12-09 18:02 ` [tip: x86/cache] x86/resctrl: Remove " tip-bot2 for Colin Ian King
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=Ya/jpoUWCy5shYI6@otcwcpicx3.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=bp@alien8.de \
--cc=colin.i.king@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--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®