[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6439df1c-df4a-9820-edb2-0ff41b581d37@redhat.com>
Date: Mon, 7 Oct 2019 14:01:53 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Like Xu <like.xu@...ux.intel.com>, kvm@...r.kernel.org,
rkrcmar@...hat.com, sean.j.christopherson@...el.com,
vkuznets@...hat.com, peterz@...radead.org,
Jim Mattson <jmattson@...gle.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
ak@...ux.intel.com, wei.w.wang@...el.com, kan.liang@...el.com,
like.xu@...el.com, ehankland@...gle.com, arbel.moshe@...cle.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] perf/core: Provide a kernel-internal interface to
recalibrate event period
On 30/09/19 09:22, Like Xu wrote:
> -static int perf_event_period(struct perf_event *event, u64 __user *arg)
> +static int _perf_event_period(struct perf_event *event, u64 value)
__perf_event_period or perf_event_period_locked would be more consistent
with other code in Linux.
Paolo
Powered by blists - more mailing lists