[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160528120259.GA7163@dhcp-128-8.nay.redhat.com>
Date: Sat, 28 May 2016 20:02:59 +0800
From: Minfei Huang <mnghuan@...il.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Andy Lutomirski <luto@...capital.net>,
Borislav Petkov <bp@...e.de>,
Andrew Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] pvclock: Add a new wrapper function to only get
variable flags
On 05/27/16 at 06:06P, Paolo Bonzini wrote:
>
>
> On 27/05/2016 17:40, Andy Lutomirski wrote:
> > On Thu, May 26, 2016 at 11:17 PM, Minfei Huang <mnghuan@...il.com> wrote:
> >> There is a generic function __pvclock_read_cycles to be used to get both
> >> flags and cycles. For function pvclock_read_flags, it's useless to get
> >> cycles value. To make this function be more effective, add a new wrapper
> >> function to only get variable flags.
> >
> > Why not just get rid of this function entirely?
>
> I agree. If you want to abstract the retry logic, perhaps you can add
Hmm, I will get rid of pvclock_read_flags, and repost it.
Thanks
Minfei
> pvclock_read_{begin,retry} functions like seqlock_read_{begin,retry}?
>
> Thanks,
>
> Paolo
Powered by blists - more mailing lists