On Fri, Aug 20, 2021 at 2:29 AM Marc Zyngier wrote:
>
> On Thu, 19 Aug 2021 23:34:06 +0100,
> Raghavendra Rao Ananta wrote:
> >
> > Potentially, the guests could trigger a debug exception that's
> > outside the exception class range.
>
> How? All the exception classes that lead to this functions
On Thu, Aug 19, 2021 at 11:43 AM Marcelo Tosatti wrote:
>
> On Mon, Aug 16, 2021 at 12:11:25AM +, Oliver Upton wrote:
> > Sean noticed that KVM_GET_CLOCK was checking kvm_arch.use_master_clock
> > outside of the pvclock sync lock. This is problematic, as the clock
> > value written to the
On Mon, Aug 16, 2021 at 12:11:27AM +, Oliver Upton wrote:
> Handling the migration of TSCs correctly is difficult, in part because
> Linux does not provide userspace with the ability to retrieve a (TSC,
> realtime) clock pair for a single instant in time. In lieu of a more
> convenient
Potentially, the guests could trigger a debug exception that's
outside the exception class range. This could lead to an
excessive syslog flooding. Hence, ratelimit the error message.
Signed-off-by: Raghavendra Rao Ananta
---
arch/arm64/kvm/handle_exit.c | 2 +-
1 file changed, 1 insertion(+), 1
On Wed, 28 Jul 2021 15:32:30 +, David Brazdil wrote:
> the range_is_memory function in hyp.
>
> David Brazdil (2):
> KVM: arm64: Fix off-by-one in range_is_memory
> KVM: arm64: Minor optimization of range_is_memory
>
> arch/arm64/kvm/hyp/nvhe/mem_protect.c | 11 ---
> 1 file
On Tue, 17 Aug 2021 09:11:19 +0100, Fuad Tabba wrote:
> Changes since v3 [1]:
> - Redid calculating restricted values of feature register fields, ensuring
> that
> the code distinguishes between unsigned and (potentially in the future)
> signed fields (Will)
> - Refactoring and fixes (Drew,
On Thu, 19 Aug 2021 23:34:06 +0100,
Raghavendra Rao Ananta wrote:
>
> Potentially, the guests could trigger a debug exception that's
> outside the exception class range.
How? All the exception classes that lead to this functions are already
handled in the switch/case statement.
> This could
On Fri, 06 Aug 2021 14:40:00 +0100,
Quentin Perret wrote:
>
> On Friday 06 Aug 2021 at 12:31:07 (+0100), Will Deacon wrote:
> > From: Marc Zyngier
> >
> > The protected mode relies on a separate helper to load the
> > S2 context. Move over to the __load_guest_stage2() helper
> > instead.
> >
On Thu, 19 Aug 2021 19:03:05 +0100, Marc Zyngier wrote:
> When a mapped level interrupt (a timer, for example) is deactivated
> by the guest, the corresponding host interrupt is equally deactivated.
> However, the fate of the pending state still needs to be dealt
> with in SW.
>
> This is
