Re: [PATCH -v3 0/6] rcu,nohz,kvm: use RCU extended quiescent state when running KVM guest

[Rik van Riel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/09/2015 10:01 PM, Paul E. McKenney wrote:
> On Tue, Feb 10, 2015 at 02:44:17AM +0100, Frederic Weisbecker
> wrote:
>> On Mon, Feb 09, 2015 at 08:22:59PM -0500, Rik van Riel wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>> 
>>> On 02/09/2015 08:15 PM, Will Deacon wrote:
>>>> Hi Rik,
>>>> 
>>>> On Mon, Feb 09, 2015 at 04:04:38PM +0000, riel@xxxxxxxxxx
>>>> wrote:
>>>>> Apologies to Catalin and Will for not fixing up ARM. I am
>>>>> not familiar with ARM assembly, and not sure how to pass a
>>>>> constant argument to a function from assembly code on ARM
>>>>> :)
>>>> 
>>>> It's a bit of a faff getting enum values into asm -- we
>>>> actually have to duplicate the definitions using #defines to
>>>> get at the constants. Perhaps it would be cleaner to leave 
>>>> context_tracking_user_{enter,exit} intact as C wrappers
>>>> around context_tracking_{enter,exit} passing the appropriate
>>>> constant? That way we don't actually need to change the arch
>>>> code at all.
>>> 
>>> If Paul and Frederic have no objections, I would be happy to do
>>> that.
>>> 
>>> Paul, Frederic?
>> 
>> Sure, that's fine by me.
> 
> And if it is fine by Frederic, it is fine by me!

I'll send a new series tomorrow that addresses Will's concern,
as well as Paulo's latest suggestions.

- -- 
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU2XTsAAoJEM553pKExN6D2ZcH/R7KIkJLpaWwxM2Iy0iEy+9r
CA2Tem1wXiDRMLzvDEKQHGlX8ea2o/VWNwjSMeRzDJbd3D9wsfPBMROXOXuji3Cc
FI2XBrC+fax43vWaIcKDb/GrQanffed2VZ1klL2twTShUOaSBPXFofZ1DISvrySP
//QOe7DbgYpqYJZ2KC+KohclvIkepAbo3AuiZKj97staw4IzP4kVJi1zAk0qbDDQ
6m7X4hvHnkfiSx0YLNRJ54j3i9/py5/rbUlnNP9LAxdQzOQQCFUSUKnn9zIMBZ03
e1W77VAQLI9+URXgeuSn7928PE+eqQQJwwdLzt0ckVojJL3i8J5SfoxTMr1sZh0=
=ft08
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/