[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171201092904.30d9831f@xeon-e3>
Date: Fri, 1 Dec 2017 09:29:04 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: kvm@...r.kernel.org, x86@...nel.org,
Stephen Hemminger <sthemmin@...rosoft.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
Ingo Molnar <mingo@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH RFC 2/6] x86/hyper-v: add a function to read both TSC
and TSC page value simulateneously
On Fri, 1 Dec 2017 14:13:17 +0100
Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> +
> +static inline u64 hv_read_tsc_page_tsc(const struct ms_hyperv_tsc_page *tsc_pg,
> + u64 *cur_tsc)
> +{
> + *cur_tsc = rdtsc();
> +
> + return cur_tsc;
Why do return and setting by reference. Looks like an ugly API.
Powered by blists - more mailing lists