From: Maxim Levitsky <mlevitsk@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: seanjc@google.com
Subject: Re: [PATCH 0/2] KVM: x86: never write to memory from kvm_vcpu_check_block
Date: Wed, 20 Jul 2022 12:31:17 +0300 [thread overview]
Message-ID: <63508f39e42738d145b3534e6768a9a09c9ca37e.camel@redhat.com> (raw)
In-Reply-To: <20220427173758.517087-1-pbonzini@redhat.com>
On Wed, 2022-04-27 at 13:37 -0400, Paolo Bonzini wrote:
> Maxim reported the following backtrace:
>
> [ 1355.807187] kvm_vcpu_map+0x159/0x190 [kvm]
> [ 1355.807628] nested_svm_vmexit+0x4c/0x7f0 [kvm_amd]
> [ 1355.808036] ? kvm_vcpu_block+0x54/0xa0 [kvm]
> [ 1355.808450] svm_check_nested_events+0x97/0x390 [kvm_amd]
> [ 1355.808920] kvm_check_nested_events+0x1c/0x40 [kvm]
> [ 1355.809396] kvm_arch_vcpu_runnable+0x4e/0x190 [kvm]
> [ 1355.809892] kvm_vcpu_check_block+0x4f/0x100 [kvm]
> [ 1355.811259] kvm_vcpu_block+0x6b/0xa0 [kvm]
>
> due to kmap being called in non-sleepable (!TASK_RUNNING) context.
> Fix it by extending kvm_x86_ops->nested_ops.hv_timer_pending and
> getting rid of one annoying instance of kvm_check_nested_events.
>
> Paolo
>
Any update on this patch series? Pinging so it is not forgotten.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2022-07-20 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:37 Paolo Bonzini
2022-04-27 17:37 ` [PATCH 1/3] KVM: x86: make vendor code check for all nested events Paolo Bonzini
2022-04-27 20:40 ` Maxim Levitsky
2022-04-29 18:40 ` Paolo Bonzini
2022-04-29 17:03 ` Sean Christopherson
2022-04-29 17:09 ` Paolo Bonzini
2022-04-29 17:35 ` Sean Christopherson
2022-04-27 17:37 ` [PATCH 2/3] KVM: x86: a vCPU with a pending triple fault is runnable Paolo Bonzini
2022-04-27 20:41 ` Maxim Levitsky
2022-04-27 17:37 ` [PATCH 3/3] KVM: x86: never write to memory from kvm_vcpu_check_block Paolo Bonzini
2022-04-27 20:42 ` Maxim Levitsky
2022-07-20 9:31 ` Maxim Levitsky [this message]
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=63508f39e42738d145b3534e6768a9a09c9ca37e.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®