[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8cfe5678-b8c0-471c-8ad2-2c232c4bbc24@web.de>
Date: Thu, 24 Jul 2025 13:26:41 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Naman Jain <namjain@...ux.microsoft.com>,
"K . Y . Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>, Wei Liu <wei.liu@...nel.org>,
Dexuan Cui <decui@...rosoft.com>, Michael Kelley <mhklinux@...look.com>,
linux-hyperv@...r.kernel.org
Cc: Roman Kisel <romank@...ux.microsoft.com>,
Anirudh Rayabharam <anrayabh@...ux.microsoft.com>,
Saurabh Sengar <ssengar@...ux.microsoft.com>,
Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>,
Nuno Das Neves <nunodasneves@...ux.microsoft.com>,
Alok Tiwari <alok.a.tiwari@...cle.com>, "Paul E. McKenney"
<paulmck@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 0/2] Drivers: hv: Introduce new driver - mshv_vtl
…
>> Do you see opportunities to extend guard applications for further data structures?
…
> So I actually extended using guard to all the other places where I was
> using manual mutex lock/unlock. I had to reorganize the code a bit,
> which made the overall flow simpler and more robust. If I am missing
> something, please let me know.
Can you imagine that similar adjustments will become helpful at further
source code places also according to other pairs of function/macro calls?
https://elixir.bootlin.com/linux/v6.16-rc7/source/include/linux/rcupdate.h#L1155-L1167
How do you think about to fiddle any more with “constructors” and “destructors”?
Regards,
Markus
Powered by blists - more mailing lists