[PATCH v2 1/1] Drivers: hv: vmbus: Don't release fb_mmio resource in vmbus_free_mmio()

From: Michael Kelley The VMBus driver manages the MMIO space it owns via the hyperv_mmio resource tree. Because the synthetic video framebuffer portion of the MMIO space is initially setup by the Hyper-V host for each guest, the VMBus driver does an early reserve of that portion of MMIO space in

Re: [PATCH 1/7] x86/hyperv: Fix output argument to hypercall that changes page visibility

On Wed, Feb 26, 2025 at 02:59:53PM -0800, Nuno Das Neves wrote: > On 2/26/2025 12:06 PM, mhkelle...@gmail.com wrote: > > From: Michael Kelley > > > > The hypercall in hv_mark_gpa_visibility() is invoked with an input > > argument and an output argument. The output argument ostensibly returns > >

Re: [PATCH hyperv-next v5 06/11] arm64, x86: hyperv: Report the VTL the system boots in

On Fri, Mar 07, 2025 at 02:02:58PM -0800, Roman Kisel wrote: > The hyperv guest code might run in various Virtual Trust Levels. > > Report the level when the kernel boots in the non-default (0) > one. > > Signed-off-by: Roman Kisel > --- > arch/arm64/hyperv/mshyperv.c | 2 ++ > arch/x86/hyperv/

Re: [PATCH 1/1] Drivers: hv: vmbus: Don't release fb_mmio resource in vmbus_free_mmio()

On Sat, Mar 08, 2025 at 08:50:12PM -0800, Saurabh Singh Sengar wrote: > On Mon, Feb 10, 2025 at 09:01:14PM -0800, mhkelle...@gmail.com wrote: > > From: Michael Kelley > > > > The VMBus driver manages the MMIO space it owns via the hyperv_mmio > > resource tree. Because the synthetic video framebu

RE: [EXTERNAL] Re: [PATCH net] net: mana: Support holes in device list reply msg

> -Original Message- > From: Jakub Kicinski > Sent: Friday, March 7, 2025 10:50 PM > To: Haiyang Zhang > Cc: linux-hyperv@vger.kernel.org; net...@vger.kernel.org; Dexuan Cui > ; step...@networkplumber.org; KY Srinivasan > ; Paul Rosswurm ; > o...@aepfle.de; vkuzn...@redhat.com; da...@d

[patch 02/10] genirq/msi: Use lock guards for MSI descriptor locking

Provide a lock guard for MSI descriptor locking and update the core code accordingly. No functional change intended. Signed-off-by: Thomas Gleixner --- include/linux/msi.h |3 + kernel/irq/msi.c| 104 +++- 2 files changed, 42 insertions(+

Re: [patch 10/10] genirq/msi: Rename msi_[un]lock_descs()

On 3/9/2025 12:41 AM, Thomas Gleixner wrote: Now that all abuse is gone and the legit users are converted to guard(msi_descs_lock), rename the lock functions and document them as internal. No functional chance. s/chance/change? Signed-off-by: Thomas Gleixner

[patch 05/10] PCI/MSI: Switch to MSI descriptor locking to guard()

Convert the code to use the new guard(msi_descs_lock). No functional change intended. Signed-off-by: Thomas Gleixner Cc: Bjorn Helgaas Cc: linux-...@vger.kernel.org --- drivers/pci/msi/api.c |6 ++ drivers/pci/msi/msi.c | 30 -- 2 files changed, 14 inserti

[patch 08/10] PCI/TPH: Replace the broken MSI-X control word update

The driver walks the MSI descriptors to test whether a descriptor exists for a given index. That's just abuse of the MSI internals. The same test can be done with a single function call by looking up whether there is a Linux interrupt number assigned at the index. What's worse is that the functio

[patch 09/10] scsi: ufs: qcom: Remove the MSI descriptor abuse

The driver abuses the MSI descriptors for internal purposes. Aside of core code and MSI providers nothing has to care about their existence. They have been encapsulated with a lot of effort because this kind of abuse caused all sorts of issues including a maintainability nightmare. Rewrite the cod

[patch 10/10] genirq/msi: Rename msi_[un]lock_descs()

Now that all abuse is gone and the legit users are converted to guard(msi_descs_lock), rename the lock functions and document them as internal. No functional chance. Signed-off-by: Thomas Gleixner --- include/linux/msi.h |8 kernel/irq/msi.c| 16 ++-- 2 files chan

[patch 07/10] PCI/MSI: Provide a sane mechanism for TPH

The PCI/TPH driver fiddles with the MSI-X control word of an active interrupt completely unserialized against concurrent operations issued from the interrupt core. It also brings the PCI/MSI-X internal cached control word out of sync. Provide a function, which has the required serialization and ke

[patch 04/10] NTB/msi: Switch MSI descriptor locking to lock guard()

Convert the code to use the new guard(msi_descs_lock). No functional change intended. Signed-off-by: Thomas Gleixner Cc: Jon Mason Cc: Dave Jiang Cc: Allen Hubbe Cc: n...@lists.linux.dev --- drivers/ntb/msi.c | 22 -- 1 file changed, 8 insertions(+), 14 deletions(-) --

[patch 06/10] PCI: hv: Switch MSI descriptor locking to guard()

Convert the code to use the new guard(msi_descs_lock). No functional change intended. Signed-off-by: Thomas Gleixner Cc: Haiyang Zhang Cc: Wei Liu Cc: Bjorn Helgaas Cc: linux-hyperv@vger.kernel.org Cc: linux-...@vger.kernel.org --- drivers/pci/controller/pci-hyperv.c | 14 -- 1

[patch 03/10] soc: ti: ti_sci_inta_msi: Switch MSI descriptor locking to guard()

Convert the code to use the new guard(msi_descs_lock). No functional change intended. Signed-off-by: Thomas Gleixner Cc: Nishanth Menon Cc: Tero Kristo Cc: Santosh Shilimkar --- drivers/soc/ti/ti_sci_inta_msi.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) --- a/drivers

[patch 00/10] genirq/msi: Spring cleaning

While converting the MSI descriptor locking to a lock guard() I stumbled over various abuse of MSI descriptors (again). The following series cleans up the offending code and converts the MSI descriptor locking over to lock guard(). The series applies on Linus tree and is also available from git:

[patch 01/10] genirq/msi: Make a few functions static

None of these functions are used outside of the MSI core. Signed-off-by: Thomas Gleixner --- include/linux/msi.h |5 - kernel/irq/msi.c| 40 +++- 2 files changed, 7 insertions(+), 38 deletions(-) --- a/include/linux/msi.h +++ b/include/linux/msi