[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7f842f3-199a-bf28-79a5-5f357dea469c@redhat.com>
Date: Thu, 22 Dec 2016 13:33:54 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Roman Kagan <rkagan@...tuozzo.com>, Olaf Hering <olaf@...fle.de>,
Radim Krčmář <rkrcmar@...hat.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Haiyang Zhang <haiyangz@...rosoft.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
"Denis V . Lunev" <den@...nvz.org>
Subject: Re: [PATCH 03/15] hyperv: use standard bitops
On 21/12/2016 14:23, Roman Kagan wrote:
> On Wed, Dec 21, 2016 at 01:00:44PM +0100, Olaf Hering wrote:
>> On Tue, Dec 20, Roman Kagan wrote:
>>
>> Reverting commit 22356585712d ("staging: hv: use sync_bitops when
>> interacting with the hypervisor") is save because .......
>>
>>> - sync_set_bit(channel->monitor_bit,
>>> + set_bit(channel->monitor_bit,
>
> It isn't indeed. I didn't realize there was a UP case where it made a
> difference, and failed to locate the commit where it changed.
>
> I'll drop this part, thanks.
Perhaps the sync_bitops should be renamed to virt_bitops. This would
match virt_* memory barriers and would make their usage much more obvious.
Paolo
Powered by blists - more mailing lists