All of lore.kernel.org
 help / color / mirror / Atom feed
From: xiakaixu <xiakaixu@huawei.com>
To: Kaixu Xia <xiakaixu@huawei.com>, <a.p.zijlstra@chello.nl>,
	<paulus@samba.org>, <mingo@redhat.com>, <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kaixu.xia@linaro.org>
Subject: Re: [PATCH] perf: remove the extra validity check on nr_pages
Date: Fri, 30 Jan 2015 09:49:10 +0800	[thread overview]
Message-ID: <54CAE316.1070300@huawei.com> (raw)
In-Reply-To: <1422352512-75150-1-git-send-email-xiakaixu@huawei.com>

于 2015/1/27 17:55, Kaixu Xia 写道:
ping...

> The function is_power_of_2() also do the check on nr_pages,
> so the first check performed is unnecessary. On the other
> hand, the key point is to ensure @nr_pages is a power-of-two
> number and mostly @nr_pages is a nonzero value, so in the
> most cases, the function is_power_of_2() will be called.
> 
> Signed-off-by: Kaixu Xia <xiakaixu@huawei.com>
> ---
>  kernel/events/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 882f835..abb57c2 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -4268,7 +4268,7 @@ static int perf_mmap(struct file *file, struct vm_area_struct *vma)
>  	 * If we have rb pages ensure they're a power-of-two number, so we
>  	 * can do bitmasks instead of modulo.
>  	 */
> -	if (nr_pages != 0 && !is_power_of_2(nr_pages))
> +	if (!is_power_of_2(nr_pages))
>  		return -EINVAL;
>  
>  	if (vma_size != PAGE_SIZE * (1 + nr_pages))
> 



  reply	other threads:[~2015-01-30  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  9:55 [PATCH] perf: remove the extra validity check on nr_pages Kaixu Xia
2015-01-30  1:49 ` xiakaixu [this message]
2015-02-18 18:41 ` [tip:perf/core] perf: Remove " tip-bot for Kaixu Xia

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=54CAE316.1070300@huawei.com \
    --to=xiakaixu@huawei.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=kaixu.xia@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.