From: Paolo Bonzini <pbonzini@redhat.com>
To: Yan Zhao <yan.y.zhao@intel.com>, Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: VMX: fix lockdep warning on posted intr wakeup
Date: Wed, 29 Mar 2023 13:51:23 +0200 [thread overview]
Message-ID: <75ae80f7-b86e-3380-b3da-0e2201df4b7f@redhat.com> (raw)
In-Reply-To: <ZCOaHWE6aS0vjvya@yzhao56-desk.sh.intel.com>
On 3/29/23 03:53, Yan Zhao wrote:
> Yes, there's no actual deadlock currently.
>
> But without fixing this issue, debug_locks will be set to false along
> with below messages printed. Then lockdep will be turned off and any
> other lock detections like lockdep_assert_held()... will not print
> warning even when it's obviously violated.
Can you use lockdep subclasses, giving 0 to the sched_in path and 1 to
the sched_out path?
Paolo
next prev parent reply other threads:[~2023-03-29 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 11:10 Yan Zhao
2023-03-24 23:13 ` Sean Christopherson
2023-03-29 1:53 ` Yan Zhao
2023-03-29 11:51 ` Paolo Bonzini [this message]
2023-03-30 9:56 ` Yan Zhao
2023-03-30 18:14 ` Sean Christopherson
2023-03-31 0:06 ` Yan Zhao
2023-04-10 17:30 ` Sean Christopherson
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=75ae80f7-b86e-3380-b3da-0e2201df4b7f@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.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®