On 18/08/20 12:16, Will Deacon wrote:
> Please note that I'm planning on rewriting most of the arm64 KVM page-table
> code for 5.10, so if you can get this series in early (e.g. for -rc2), then
> it would _really_ help with managing the kvm/arm64 queue for the next merge
> window.
Yes, I plan to s
On Tue, 11 Aug 2020 11:27:23 +0100, Will Deacon wrote:
> While stress-testing my arm64 stage-2 page-table rewrite [1], I ran into
> a sleeping while atomic BUG() during OOM that I can reproduce with
> mainline.
>
> The problem is that the arm64 page-table code periodically calls
> cond_resched_loc
On 2020-08-18 11:16, Will Deacon wrote:
On Tue, Aug 18, 2020 at 08:31:08AM +0200, Paolo Bonzini wrote:
On 11/08/20 12:27, Will Deacon wrote:
> Will Deacon (2):
> KVM: Pass MMU notifier range flags to kvm_unmap_hva_range()
> KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not s
On Tue, Aug 18, 2020 at 08:31:08AM +0200, Paolo Bonzini wrote:
> On 11/08/20 12:27, Will Deacon wrote:
> > Will Deacon (2):
> > KVM: Pass MMU notifier range flags to kvm_unmap_hva_range()
> > KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set
> >
> > arch/arm64/include/asm
On 11/08/20 12:27, Will Deacon wrote:
> Hi all,
>
> While stress-testing my arm64 stage-2 page-table rewrite [1], I ran into
> a sleeping while atomic BUG() during OOM that I can reproduce with
> mainline.
>
> The problem is that the arm64 page-table code periodically calls
> cond_resched_lock()
Hi all,
While stress-testing my arm64 stage-2 page-table rewrite [1], I ran into
a sleeping while atomic BUG() during OOM that I can reproduce with
mainline.
The problem is that the arm64 page-table code periodically calls
cond_resched_lock() when unmapping the stage-2 page-tables, but in the
cas
