All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, Suzuki K Poulose <suzuki.poulose@arm.com>,
	James Morse <james.morse@arm.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Paul Mackerras <paulus@ozlabs.org>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: [PATCH 0/2] KVM: arm64: Fix sleeping while atomic BUG() on OOM
Date: Tue, 18 Aug 2020 11:30:17 +0100	[thread overview]
Message-ID: <edbd49c6ad999b71af3c2a64c920f418@kernel.org> (raw)
In-Reply-To: <20200818101607.GB15543@willie-the-truck>

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 set
>> >
>> >  arch/arm64/include/asm/kvm_host.h   |  2 +-
>> >  arch/arm64/kvm/mmu.c                | 19 ++++++++++++++-----
>> >  arch/mips/include/asm/kvm_host.h    |  2 +-
>> >  arch/mips/kvm/mmu.c                 |  3 ++-
>> >  arch/powerpc/include/asm/kvm_host.h |  3 ++-
>> >  arch/powerpc/kvm/book3s.c           |  3 ++-
>> >  arch/powerpc/kvm/e500_mmu_host.c    |  3 ++-
>> >  arch/x86/include/asm/kvm_host.h     |  3 ++-
>> >  arch/x86/kvm/mmu/mmu.c              |  3 ++-
>> >  virt/kvm/kvm_main.c                 |  3 ++-
>> >  10 files changed, 30 insertions(+), 14 deletions(-)
>> >
>> 
>> These would be okay for 5.9 too, so I plan to queue them myself before
>> we fork for 5.10.
> 
> Thanks, Paolo. Let me know if you want me to rebase/repost.
> 
> 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.
> 
> Otherwise, could you and Marc please set up a shared branch with just 
> these,
> so I can use it as a base?
> 
> Please let me know.

Given that this doesn't directly applies to -rc1, I'll push out a branch
shortly with the conflicts resolved.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sean Christopherson <sean.j.christopherson@intel.com>,
	Paul Mackerras <paulus@ozlabs.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 0/2] KVM: arm64: Fix sleeping while atomic BUG() on OOM
Date: Tue, 18 Aug 2020 11:30:17 +0100	[thread overview]
Message-ID: <edbd49c6ad999b71af3c2a64c920f418@kernel.org> (raw)
In-Reply-To: <20200818101607.GB15543@willie-the-truck>

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 set
>> >
>> >  arch/arm64/include/asm/kvm_host.h   |  2 +-
>> >  arch/arm64/kvm/mmu.c                | 19 ++++++++++++++-----
>> >  arch/mips/include/asm/kvm_host.h    |  2 +-
>> >  arch/mips/kvm/mmu.c                 |  3 ++-
>> >  arch/powerpc/include/asm/kvm_host.h |  3 ++-
>> >  arch/powerpc/kvm/book3s.c           |  3 ++-
>> >  arch/powerpc/kvm/e500_mmu_host.c    |  3 ++-
>> >  arch/x86/include/asm/kvm_host.h     |  3 ++-
>> >  arch/x86/kvm/mmu/mmu.c              |  3 ++-
>> >  virt/kvm/kvm_main.c                 |  3 ++-
>> >  10 files changed, 30 insertions(+), 14 deletions(-)
>> >
>> 
>> These would be okay for 5.9 too, so I plan to queue them myself before
>> we fork for 5.10.
> 
> Thanks, Paolo. Let me know if you want me to rebase/repost.
> 
> 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.
> 
> Otherwise, could you and Marc please set up a shared branch with just 
> these,
> so I can use it as a base?
> 
> Please let me know.

Given that this doesn't directly applies to -rc1, I'll push out a branch
shortly with the conflicts resolved.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2020-08-18 10:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 10:27 [PATCH 0/2] KVM: arm64: Fix sleeping while atomic BUG() on OOM Will Deacon
2020-08-11 10:27 ` Will Deacon
2020-08-11 10:27 ` [PATCH 1/2] KVM: Pass MMU notifier range flags to kvm_unmap_hva_range() Will Deacon
2020-08-11 10:27   ` Will Deacon
2020-08-19 23:57   ` Sasha Levin
2020-08-19 23:57     ` Sasha Levin
2020-08-26 13:54   ` Sasha Levin
2020-08-26 13:54     ` Sasha Levin
2020-08-11 10:27 ` [PATCH 2/2] KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set Will Deacon
2020-08-11 10:27   ` Will Deacon
2020-08-11 10:52   ` Suzuki K Poulose
2020-08-11 10:52     ` Suzuki K Poulose
2020-08-18  6:31 ` [PATCH 0/2] KVM: arm64: Fix sleeping while atomic BUG() on OOM Paolo Bonzini
2020-08-18  6:31   ` Paolo Bonzini
2020-08-18 10:16   ` Will Deacon
2020-08-18 10:16     ` Will Deacon
2020-08-18 10:30     ` Marc Zyngier [this message]
2020-08-18 10:30       ` Marc Zyngier
2020-08-20  7:26     ` Paolo Bonzini
2020-08-20  7:26       ` Paolo Bonzini
2020-08-18 10:34 ` Marc Zyngier
2020-08-18 10:34   ` Marc Zyngier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=edbd49c6ad999b71af3c2a64c920f418@kernel.org \
    --to=maz@kernel.org \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@ozlabs.org \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.