On Fri, Jul 26, 2024 at 03:59:09PM -0700, Roman Kisel wrote:
> The VMBus driver uses ACPI for interrupt assignment on
> arm64 hence it won't function in the VTL mode where only
> DeviceTree can be used.
>
> Update the VMBus driver to discover interrupt configuration
> via DeviceTree and indicate D
From: Saurabh Singh Sengar Sent: Monday, August
5, 2024 1:30 AM
>
> On Fri, Jul 26, 2024 at 03:59:09PM -0700, Roman Kisel wrote:
> > The VMBus driver uses ACPI for interrupt assignment on
> > arm64 hence it won't function in the VTL mode where only
> > DeviceTree can be used.
> >
> > Update the
On 8/2/2024 6:20 PM, Wei Liu wrote:
On Fri, Jul 26, 2024 at 03:59:10PM -0700, Roman Kisel wrote:
The hyperv-pci driver uses ACPI for MSI IRQ domain configuration on
arm64. It won't be able to do that in the VTL mode where only DeviceTree
can be used.
Update the hyperv-pci driver to get vPCI
On 8/2/2024 6:21 PM, Wei Liu wrote:
On Fri, Jul 26, 2024 at 03:59:04PM -0700, Roman Kisel wrote:
The arm64 Hyper-V startup path relies on ACPI to detect
running under a Hyper-V compatible hypervisor. That
doesn't work on non-ACPI systems.
Hoist the ACPI detection logic into a separate functi
On 8/2/2024 6:22 PM, Wei Liu wrote:
On Fri, Jul 26, 2024 at 03:59:07PM -0700, Roman Kisel wrote:
To run in the VTL mode, Hyper-V drivers have to know what
VTL the system boots in, and the arm64/hyperv code does not
update the variable that stores the value.
Update the variable to enable the
On 8/4/2024 8:53 PM, Saurabh Singh Sengar wrote:
On Fri, Jul 26, 2024 at 03:59:04PM -0700, Roman Kisel wrote:
The arm64 Hyper-V startup path relies on ACPI to detect
running under a Hyper-V compatible hypervisor. That
doesn't work on non-ACPI systems.
Hoist the ACPI detection logic into a se
On 8/4/2024 9:05 PM, Saurabh Singh Sengar wrote:
On Mon, Aug 05, 2024 at 03:01:58AM +, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
Kconfig dependencies for arm64 guests on Hyper-V require that be ACPI enabled,
and limit VTL mode to x86/x64. To enable VT
On Mon, Aug 05, 2024 at 08:17:05AM -0700, Roman Kisel wrote:
>
>
> On 8/4/2024 8:53 PM, Saurabh Singh Sengar wrote:
> >On Fri, Jul 26, 2024 at 03:59:04PM -0700, Roman Kisel wrote:
> >>The arm64 Hyper-V startup path relies on ACPI to detect
> >>running under a Hyper-V compatible hypervisor. That
>
On 8/4/2024 11:28 PM, Saurabh Singh Sengar wrote:
On Fri, Jul 26, 2024 at 03:59:07PM -0700, Roman Kisel wrote:
To run in the VTL mode, Hyper-V drivers have to know what
VTL the system boots in, and the arm64/hyperv code does not
update the variable that stores the value.
Update the variable
On 8/5/2024 7:12 AM, Michael Kelley wrote:
From: Saurabh Singh Sengar Sent: Monday, August
5, 2024 1:30 AM
On Fri, Jul 26, 2024 at 03:59:09PM -0700, Roman Kisel wrote:
The VMBus driver uses ACPI for interrupt assignment on
arm64 hence it won't function in the VTL mode where only
DeviceTre
On 8/5/2024 8:46 AM, Saurabh Singh Sengar wrote:
On Mon, Aug 05, 2024 at 08:17:05AM -0700, Roman Kisel wrote:
On 8/4/2024 8:53 PM, Saurabh Singh Sengar wrote:
On Fri, Jul 26, 2024 at 03:59:04PM -0700, Roman Kisel wrote:
The arm64 Hyper-V startup path relies on ACPI to detect
running under
On 8/5/2024 7:51 AM, Roman Kisel wrote:
On 8/2/2024 6:20 PM, Wei Liu wrote:
On Fri, Jul 26, 2024 at 03:59:10PM -0700, Roman Kisel wrote:
The hyperv-pci driver uses ACPI for MSI IRQ domain configuration on
arm64. It won't be able to do that in the VTL mode where only DeviceTree
can be used.
On 8/4/2024 8:02 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
To run in the VTL mode, Hyper-V drivers have to know what
VTL the system boots in, and the arm64/hyperv code does not
have the means to compute that.
Refactor the code to hoist the function th
On 8/4/2024 8:02 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
To run in the VTL mode, Hyper-V drivers have to know what
VTL the system boots in, and the arm64/hyperv code does not
update the variable that stores the value.
Update the variable to enable t
On 8/4/2024 8:03 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Monday, July 29, 2024 9:51
AM
On 7/27/2024 2:17 AM, Arnd Bergmann wrote:
On Sat, Jul 27, 2024, at 10:56, Krzysztof Kozlowski wrote:
On 27/07/2024 00:59, Roman Kisel wrote:
@@ -2338,6 +2372,21 @@ static int vmbus_device_
On 8/4/2024 8:03 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
The hyperv-pci driver uses ACPI for MSI IRQ domain configuration on
arm64. It won't be able to do that in the VTL mode where only DeviceTree
can be used.
Update the hyperv-pci driver to get vP
On 8/4/2024 8:01 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
The arm64 Hyper-V startup path relies on ACPI to detect
running under a Hyper-V compatible hypervisor. That
doesn't work on non-ACPI systems.
Hoist the ACPI detection logic into a separate fun
From: Roman Kisel Sent: Monday, August 5, 2024
8:24 AM
>
> On 8/4/2024 9:05 PM, Saurabh Singh Sengar wrote:
> > On Mon, Aug 05, 2024 at 03:01:58AM +, Michael Kelley wrote:
> >> From: Roman Kisel Sent: Friday, July 26, 2024
> >> 3:59
> PM
> >>>
> >>> Kconfig dependencies for arm64 guests on
Use native_read_cr*() helpers to read control registers into vmsa->cr*
instead of open-coded assembly.
No functional change intended, unless there was a purpose to specifying
rax.
Signed-off-by: Yosry Ahmed
---
v1 -> v2:
- Fixed a silly bug that overwrote vmsa->cr3 instead of reading
vmsa->cr
From: Roman Kisel Sent: Monday, August 5, 2024
9:20 AM
>
> On 8/4/2024 8:02 PM, Michael Kelley wrote:
> > From: Roman Kisel Sent: Friday, July 26, 2024
> > 3:59
> PM
> >>
> >> To run in the VTL mode, Hyper-V drivers have to know what
> >> VTL the system boots in, and the arm64/hyperv code does
From: Roman Kisel Sent: Monday, August 5, 2024
9:51 AM
[snip]
> >> diff --git a/arch/arm64/include/asm/mshyperv.h
> >> b/arch/arm64/include/asm/mshyperv.h
> >> index a975e1a689dd..a7a3586f7cb1 100644
> >> --- a/arch/arm64/include/asm/mshyperv.h
> >> +++ b/arch/arm64/include/asm/mshyperv.h
> >>
On 8/5/2024 1:30 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Monday, August 5, 2024
9:51 AM
[snip]
diff --git a/arch/arm64/include/asm/mshyperv.h
b/arch/arm64/include/asm/mshyperv.h
index a975e1a689dd..a7a3586f7cb1 100644
--- a/arch/arm64/include/asm/mshyperv.h
+++ b/arch/arm64/incl
On 8/5/2024 1:13 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Monday, August 5, 2024
9:20 AM
On 8/4/2024 8:02 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, July 26, 2024 3:59
PM
To run in the VTL mode, Hyper-V drivers have to know what
VTL the system boots in, and the
> >
> > On 8/4/2024 9:05 PM, Saurabh Singh Sengar wrote:
> > > On Mon, Aug 05, 2024 at 03:01:58AM +, Michael Kelley wrote:
> > >> From: Roman Kisel Sent: Friday, July 26,
> > >> 2024 3:59
> > PM
> > >>>
> > >>> Kconfig dependencies for arm64 guests on Hyper-V require that be ACPI
> > >>> en
From: Long Li
After napi_complete_done() is called, another NAPI may be running on
another CPU and ring the doorbell before the current CPU does. When
combined with unnecessary rings when there is no need to ARM the CQ, this
triggers error paths in the hardware.
Fix this by always ring the doorb
From: Wei Liu Sent: Friday, August 2, 2024 4:50 PM
>
> On Tue, Jun 11, 2024 at 07:51:48AM -0700, Roman Kisel wrote:
> >
> >
> > On 6/5/2024 7:55 PM, mhkelle...@gmail.com wrote:
> > > From: Michael Kelley
> > >
> > > A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
> > > a
Increase default VMBus channels in Linux netvsc from 8 to 16
to align with Azure Windows VM and improve networking throughput.
Set channels to 16 for VMs with more than 16 vCPUs;
otherwise, channels depend on VM's vCPU count.
Performance tests showed significant improvement in throughput:
- 0.54%
27 matches
Mail list logo
