diff options
| author | Fabiano Rosas <farosas@linux.ibm.com> | 2022-08-17 00:25:17 +0200 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2022-09-27 17:07:19 +0200 |
| commit | 0a5bfb824a6ea35e54b7e5ac6f881beea5e309d2 (patch) | |
| tree | ef96714f4fdd91c3fb3a25ba5e28b39b0fd61f4a /arch/powerpc/kvm/book3s_64_mmu_host.c | |
| parent | Linux 6.0-rc2 (diff) | |
| download | linux-0a5bfb824a6ea35e54b7e5ac6f881beea5e309d2.tar.xz linux-0a5bfb824a6ea35e54b7e5ac6f881beea5e309d2.zip | |
KVM: PPC: Book3S HV: Fix decrementer migration
We used to have a workaround[1] for a hang during migration that was
made ineffective when we converted the decrementer expiry to be
relative to guest timebase.
The point of the workaround was that in the absence of an explicit
decrementer expiry value provided by userspace during migration, KVM
needs to initialize dec_expires to a value that will result in an
expired decrementer after subtracting the current guest timebase. That
stops the vcpu from hanging after migration due to a decrementer
that's too large.
If the dec_expires is now relative to guest timebase, its
initialization needs to be guest timebase-relative as well, otherwise
we end up with a decrementer expiry that is still larger than the
guest timebase.
1- https://git.kernel.org/torvalds/c/5855564c8ab2
Fixes: 3c1a4322bba7 ("KVM: PPC: Book3S HV: Change dec_expires to be relative to guest timebase")
Signed-off-by: Fabiano Rosas <farosas@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20220816222517.1916391-1-farosas@linux.ibm.com
Diffstat (limited to 'arch/powerpc/kvm/book3s_64_mmu_host.c')
0 files changed, 0 insertions, 0 deletions