On Sun, Mar 09, 2025 at 08:52:08PM -0700, 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 framebuffer portion of the
> MMIO space is initially setup by the Hyper-V host for each
On 10/03/2025 18:05, Roman Kisel wrote:
>
>
> On 3/10/2025 2:28 AM, Krzysztof Kozlowski wrote:
>> On Fri, Mar 07, 2025 at 02:02:59PM -0800, Roman Kisel wrote:
>>> To boot on ARM64, VMBus requires configuring interrupts. Missing
>>> DMA coherence property is sub-optimal as the VMBus transations ar
On 3/5/2025 12:36 PM, Naman Jain wrote:
On 2/27/2025 11:54 AM, Naman Jain wrote:
On 2/26/2025 8:03 PM, Greg Kroah-Hartman wrote:
On Wed, Feb 26, 2025 at 05:51:46PM +0530, Naman Jain wrote:
On 2/26/2025 3:33 PM, Greg Kroah-Hartman wrote:
On Wed, Feb 26, 2025 at 10:43:41AM +0530, Naman
On Mon, Mar 10, 2025 at 03:12:01PM -0700, lon...@linuxonhyperv.com wrote:
> From: Long Li
>
> Hyper-V may offer a non latency sensitive device with subchannels without
> monitor bit enabled. The decision is entirely on the Hyper-V host not
> configurable within guest.
>
> When a device has subch
From: lon...@linuxonhyperv.com Sent: Monday, March
10, 2025 3:12 PM
>
> Hyper-V may offer a non latency sensitive device with subchannels without
> monitor bit enabled. The decision is entirely on the Hyper-V host not
> configurable within guest.
>
> When a device has subchannels, also signal e
On 3/8/2025 1:05 PM, Arnd Bergmann wrote:
On Fri, Mar 7, 2025, at 23:02, Roman Kisel wrote:
@@ -5,18 +5,20 @@ menu "Microsoft Hyper-V guest support"
config HYPERV
tristate "Microsoft Hyper-V client drivers"
depends on (X86 && X86_LOCAL_APIC && HYPERVISOR_GUEST) \
-
From: Arnd Bergmann Sent: Saturday, March 8, 2025 1:05 PM
>
> On Fri, Mar 7, 2025, at 23:02, Roman Kisel wrote:
> > @@ -5,18 +5,20 @@ menu "Microsoft Hyper-V guest support"
> > config HYPERV
> > tristate "Microsoft Hyper-V client drivers"
> > depends on (X86 && X86_LOCAL_APIC && HYPERVIS
On Mon, Mar 10, 2025 at 09:42:15AM -0700, Roman Kisel wrote:
>
>
> On 3/9/2025 5:31 PM, Wei Liu wrote:
> > 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
From: Thorsten Blum Sent: Monday, March 10, 2025
12:26 PM
>
> The union vmpacket_largest_possible_header and several structs have not
> been used for a long time afaict - remove them.
>
> Signed-off-by: Thorsten Blum
> ---
> include/linux/hyperv.h | 47
On Tue, Mar 11, 2025 at 8:54 AM Jason Wang wrote:
>
> On Mon, Mar 10, 2025 at 10:15 PM Stefano Garzarella
> wrote:
> >
> > On Thu, 6 Mar 2025 at 01:17, Jason Wang wrote:
> > >
> > > On Wed, Mar 5, 2025 at 5:30 PM Stefano Garzarella
> > > wrote:
> > > >
> > > > On Wed, Mar 05, 2025 at 02:27:12
On Tue, Mar 11, 2025 at 4:14 AM Bobby Eshleman wrote:
>
> On Wed, Mar 05, 2025 at 01:46:54PM +0800, Jason Wang wrote:
> > On Wed, Mar 5, 2025 at 8:39 AM Bobby Eshleman
> > wrote:
> > >
> > > On Tue, Apr 28, 2020 at 06:00:52PM +0200, Stefano Garzarella wrote:
> > > > On Tue, Apr 28, 2020 at 04:13
On Mon, Mar 10, 2025 at 10:15 PM Stefano Garzarella wrote:
>
> On Thu, 6 Mar 2025 at 01:17, Jason Wang wrote:
> >
> > On Wed, Mar 5, 2025 at 5:30 PM Stefano Garzarella
> > wrote:
> > >
> > > On Wed, Mar 05, 2025 at 02:27:12AM -0500, Michael S. Tsirkin wrote:
> > > >On Tue, Mar 04, 2025 at 04:39
On Wed, Mar 05, 2025 at 01:46:54PM +0800, Jason Wang wrote:
> On Wed, Mar 5, 2025 at 8:39 AM Bobby Eshleman wrote:
> >
> > On Tue, Apr 28, 2020 at 06:00:52PM +0200, Stefano Garzarella wrote:
> > > On Tue, Apr 28, 2020 at 04:13:22PM +0800, Jason Wang wrote:
> >
> > WRT netdev, do we foresee big gai
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
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 vPCI MSI IRQ domain in the DeviceTree
>
From: Arnd Bergmann Sent: Monday, March 10, 2025 2:21 PM
>
> On Mon, Mar 10, 2025, at 22:01, Michael Kelley wrote:
> > From: Arnd Bergmann Sent: Saturday, March 8, 2025 1:05 PM
> >> > config HYPERV_VTL_MODE
> >> > bool "Enable Linux to boot in VTL context"
> >> > -depends on X8
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
PM
>
> Using acpi_irq_create_hierarchy() in the cases where the code
> also handles OF leads to code duplication as the ACPI subsystem
> doesn't provide means to compute the IRQ domain parent whereas
> the OF does.
>
> Introduce acpi_get_gsi_di
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
PM
>
> Various parts of the hyperv code need to know what VTL
> the kernel runs at, most notably VMBus needs that to
> establish communication with the host.
>
> Initialize the Virtual Trust Level field to enable
> booting in the Virtual Trust
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
PM
>
> The ARM64 PCI code for hyperv needs to know the VMBus root
> device, and it is private.
>
> Provide a function that returns it. Rename it from "hv_dev"
> as "hv_dev" as a symbol is very overloaded. No functional
> changes.
>
> Signed-of
From: Long Li
Hyper-V may offer a non latency sensitive device with subchannels without
monitor bit enabled. The decision is entirely on the Hyper-V host not
configurable within guest.
When a device has subchannels, also signal events for the subchannel
if its monitor bit is disabled.
This patc
On 3/10/2025 2:16 PM, Michael Kelley wrote:
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
PM
In the Subject line,
s/detectting/detecting/
[...]
s/cenrtal/central/
My bad, will fix! Thanks for spotting that, I'll be sure to have
the spellchecker on.
--
Thank you,
Roman
On 3/10/2025 2:17 PM, Krzysztof Kozlowski wrote:
On 10/03/2025 19:07, Roman Kisel wrote:
It is modeled as a bus in the kernel:
https://www.kernel.org/doc/html/latest/virt/hyperv/vmbus.html
Please upstream bindings for the bus devices and extend the example here
with these devices.
The se
On 3/7/2025 9:38 AM, Michael Kelley wrote:
> From: Nuno Das Neves Sent: Friday,
> February 28, 2025 4:38 PM
>>
>> On 2/26/2025 3:43 PM, Stanislav Kinsburskii wrote:
>>> On Wed, Feb 26, 2025 at 03:08:02PM -0800, Nuno Das Neves wrote:
This will handle SYNIC interrupts such as intercepts, doorb
On Mon, Mar 10, 2025, at 22:01, Michael Kelley wrote:
> From: Arnd Bergmann Sent: Saturday, March 8, 2025 1:05 PM
>> > config HYPERV_VTL_MODE
>> >bool "Enable Linux to boot in VTL context"
>> > - depends on X86_64 && HYPERV
>> > + depends on (X86_64 || ARM64)
>> >depends on SMP
>> > +
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
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 function. Then
> use the vendor-specific
On 10/03/2025 19:07, Roman Kisel wrote:
>
> It is modeled as a bus in the kernel:
> https://www.kernel.org/doc/html/latest/virt/hyperv/vmbus.html
>
>> Please upstream bindings for the bus devices and extend the example here
>> with these devices.
>
> The set of synthetic devices that reside on t
From: Roman Kisel Sent: Friday, March 7, 2025 2:03
PM
>
In the Subject line,
s/detectting/detecting/
> The KVM/arm64 uses SMCCC to detect hypervisor presence. That code is
> private, and it follows the SMCCC specification. Other existing and
> emerging hypervisor guest implementations can and
On 3/10/2025 9:41 AM, Bjorn Helgaas wrote:
On Fri, Mar 07, 2025 at 02:03:03PM -0800, 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 ge
From: Thorsten Blum Sent: Monday, March 10, 2025 1:41
PM
>
> On 10. Mar 2025, at 21:21, Michael Kelley wrote:
> >
> > It appears to me that struct vmdata_gpa_direct and struct
> > vmadditional_data are also unused. Did you keep them for
> > some reason? Or could they also be deleted in this patc
From: Thomas Gleixner Sent: Sunday, March 9, 2025 12:42 AM
>
> 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-..
On Sat, Mar 8, 2025 at 6:04 AM 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
> have the means to compute that.
>
> Refactor the code to hoist the function that detects VTL,
> make it arch-neutral to be
On Sat, Mar 8, 2025 at 6:05 AM Roman Kisel wrote:
>
> The ARM64 PCI code for hyperv needs to know the VMBus root
> device, and it is private.
>
> Provide a function that returns it. Rename it from "hv_dev"
> as "hv_dev" as a symbol is very overloaded. No functional
> changes.
>
> Signed-off-by: Ro
On Thu, Feb 27, 2025 at 7:09 AM Nuno Das Neves
wrote:
>
> Factor out the check for enabling auto eoi, to be reused in root
> partition code.
>
> Signed-off-by: Nuno Das Neves
> ---
Reviewed-by: Tianyu Lan
--
Thanks
Tianyu Lan
On Sun, Mar 09, 2025 at 10:01:33PM +, Haiyang Zhang wrote:
>
>
> > -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
On Fri, Mar 07, 2025 at 02:02:59PM -0800, Roman Kisel wrote:
> To boot on ARM64, VMBus requires configuring interrupts. Missing
> DMA coherence property is sub-optimal as the VMBus transations are
> cache-coherent.
>
> Add interrupts to be able to boot on ARM64. Add DMA coherence to
> avoid doing
34 matches
Mail list logo
