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 Hyper-V drivers to boot
> in the
On Fri, Jul 26, 2024 at 03:59:06PM -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
> have the means to compute that.
>
> Refactor the code to hoist the function that detects VTL,
> make it arch-neut
On Fri, Jul 26, 2024 at 03:59:05PM -0700, Roman Kisel wrote:
> Kconfig dependencies for arm64 guests on Hyper-V require that be ACPI enabled,
> and limit VTL mode to x86/x64. To enable VTL mode on arm64 as well, update the
> dependencies. Since VTL mode requires DeviceTree instead of ACPI, don’t
>
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 function,
> use the new SMC added rece
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 MSI IRQ domain in the DeviceTree
On Fri, Aug 02, 2024 at 03:51:37PM +, Michael Kelley wrote:
> From: Roman Kisel Sent: Thursday, August 1, 2024
> 2:23 PM
> >
> > When hv_synic_disable_regs was introduced, it received the description
> > of hv_synic_cleanup. Fix that.
> >
> > Fixes: dba61cda3046 ("Drivers: hv: vmbus: Break
On Wed, Jul 03, 2024 at 04:44:05PM +, Michael Kelley wrote:
> From: Anthony Nandaa Sent: Tuesday, July 2, 2024 3:23
> AM
> > Signed-off-by: Anthony Nandaa
> > Reviewed-by: Michael Kelley
>
> Reviewed-by: Michael Kelley
Applied to hyperv-fixes. Thanks.
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
> > available. In this case, set X86_FEATURE_TSC_KNOWN_FREQ so that Linux
On Fri, 2024-08-02 at 15:44 +, Michael Kelley wrote:
> Did a basic smoke test of this two-patch series on a Hyper-V Gen 1
> VM and on a Gen 2 VM. All looks good and behaves as expected.
>
> On the Gen 1 VM, the PIT is used briefly at boot (takes ~35 interrupts)
> before the Hyper-V synthetic t
From: Roman Kisel Sent: Thursday, August 1, 2024
2:23 PM
>
> When hv_synic_disable_regs was introduced, it received the description
> of hv_synic_cleanup. Fix that.
>
> Fixes: dba61cda3046 ("Drivers: hv: vmbus: Break out synic enable and disable
> operations")
>
> Signed-off-by: Roman Kisel
>
From: David Woodhouse Sent: Friday, August 2, 2024 6:56 AM
>
> Leaving the PIT interrupt running can cause noticeable steal time for
> virtual guests. The VMM generally has a timer which toggles the IRQ input
> to the PIC and I/O APIC, which takes CPU time away from the guest. Even
> on real hard
On Fri, 2024-08-02 at 07:55 -0700, Sean Christopherson wrote:
> On Fri, Aug 02, 2024, David Woodhouse wrote:
> > On Thu, 2024-08-01 at 20:54 +0200, Thomas Gleixner wrote:
> > > On Thu, Aug 01 2024 at 16:14, Michael Kelley wrote:
> > > > I don't have a convenient way to test my sequence on KVM.
> >
On Fri, Aug 02, 2024, David Woodhouse wrote:
> On Thu, 2024-08-01 at 20:54 +0200, Thomas Gleixner wrote:
> > On Thu, Aug 01 2024 at 16:14, Michael Kelley wrote:
> > > I don't have a convenient way to test my sequence on KVM.
> >
> > But still fails in KVM
>
> By KVM you mean the in-kernel one tha
From: David Woodhouse
Leaving the PIT interrupt running can cause noticeable steal time for
virtual guests. The VMM generally has a timer which toggles the IRQ input
to the PIC and I/O APIC, which takes CPU time away from the guest. Even
on real hardware, running the counter may use power needles
From: David Woodhouse
According to the data sheet, writing the MODE register should stop the
counter (and thus the interrupts). This appears to work on real hardware,
at least modern Intel and AMD systems. It should also work on Hyper-V.
However, on some buggy virtual machines the mode change do
On Fri, 2024-08-02 at 15:27 +0200, Thomas Gleixner wrote:
> > Top two commits of
> > https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/clocks
> >
> > I'll repost properly if you're happy with them?
>
> Just make the disable unconditional.
Oops, thought I'd done that too. Turns
On Fri, Aug 02 2024 at 12:04, David Woodhouse wrote:
> On Fri, 2024-08-02 at 12:49 +0200, Thomas Gleixner wrote:
>> So fine, we can go with the patch from Li, but the changelog needs a
>> rewrite and the code want's a big fat comment.
>
> Nah, it wants to be MODE, COUNT, COUNT, MODE to handle all k
On Fri, 2024-08-02 at 12:49 +0200, Thomas Gleixner wrote:
> On Fri, Aug 02 2024 at 09:07, David Woodhouse wrote:
> > On Thu, 2024-08-01 at 20:57 +0200, Thomas Gleixner wrote:
> > > It's not counting right out of reset. But once it started counting it's
> > > tedious to stop :)
> >
> > My reading o
On Fri, Aug 02 2024 at 09:07, David Woodhouse wrote:
> On Thu, 2024-08-01 at 20:57 +0200, Thomas Gleixner wrote:
>> It's not counting right out of reset. But once it started counting it's
>> tedious to stop :)
>
> My reading of the data sheet definitely suggests that it *shouldn't*
> be.
>
> Mode 0
From: David Woodhouse
According to the data sheet, writing the MODE register should stop the
counter (and thus the interrupts). This appears to work on real hardware,
at least modern Intel and AMD systems. It should also work on Hyper-V.
However, on some buggy virtual machines the mode change do
On Thu, 2024-08-01 at 22:31 +0100, David Woodhouse wrote:
> On 1 August 2024 22:22:56 BST, Thomas Gleixner wrote:
> > On Thu, Aug 01 2024 at 21:49, David Woodhouse wrote:
> > > On Thu, 2024-08-01 at 22:00 +0200, Thomas Gleixner wrote:
> > > > > I justify my cowardice on the basis that it doesn't *
On Thu, 2024-08-01 at 20:54 +0200, Thomas Gleixner wrote:
> On Thu, Aug 01 2024 at 16:14, Michael Kelley wrote:
> > From: Thomas Gleixner Sent: Thursday, August
> > 1, 2024 7:21 AM
> > FWIW, in Hyper-V guests with the Hyper-V quirk removed, tglx's new
> > sequence does *not* stop the PIT. But this
On Thu, 2024-08-01 at 20:57 +0200, Thomas Gleixner wrote:
> On Thu, Aug 01 2024 at 19:25, David Woodhouse wrote:
> > On Thu, 2024-08-01 at 18:49 +0100, David Woodhouse wrote:
> > > > The stop sequence is wrong:
> > > >
> > > > When there is a count in progress, writing a new LSB before the
> >
23 matches
Mail list logo
