From: Sean Christopherson <seanjc@google.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH v4 01/10] KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock
Date: Fri, 30 Aug 2024 06:57:14 -0700 [thread overview]
Message-ID: <ZtHPusyTNkQ_a1Y-@google.com> (raw)
In-Reply-To: <1f037b5604deb5f83f05e709b2edf3063372518f.camel@intel.com>
On Fri, Aug 30, 2024, Kai Huang wrote:
>
> > Reviewed-by: Kai Huang <kai.huang@intel.com>
> > Acked-by: Kai Huang <kai.huang@intel.com>
> >
>
> Hmm I must have done a lot for me to receive two credits (and for most patches
> in this series) :-)
>
> I think one Reviewed-by tag is good enough :-)
Heh, indeed. b4 has made me very lazy; I just `b4 am` the patches and let b4
grab all the trailers. I'm guessing something went awry in that flow (or maybe
you acked a previous version or something?)
Anyways, one of Paolo or I can clean this up when applying, assuming we remember
to do so...
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: Kai Huang <kai.huang@intel.com>
Cc: "zhaotianrui@loongson.cn" <zhaotianrui@loongson.cn>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
"maobibo@loongson.cn" <maobibo@loongson.cn>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"maz@kernel.org" <maz@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"anup@brainfault.org" <anup@brainfault.org>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
Chao Gao <chao.gao@intel.com>,
"kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Farrah Chen <farrah.chen@intel.com>
Subject: Re: [PATCH v4 01/10] KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock
Date: Fri, 30 Aug 2024 06:57:14 -0700 [thread overview]
Message-ID: <ZtHPusyTNkQ_a1Y-@google.com> (raw)
In-Reply-To: <1f037b5604deb5f83f05e709b2edf3063372518f.camel@intel.com>
On Fri, Aug 30, 2024, Kai Huang wrote:
>
> > Reviewed-by: Kai Huang <kai.huang@intel.com>
> > Acked-by: Kai Huang <kai.huang@intel.com>
> >
>
> Hmm I must have done a lot for me to receive two credits (and for most patches
> in this series) :-)
>
> I think one Reviewed-by tag is good enough :-)
Heh, indeed. b4 has made me very lazy; I just `b4 am` the patches and let b4
grab all the trailers. I'm guessing something went awry in that flow (or maybe
you acked a previous version or something?)
Anyways, one of Paolo or I can clean this up when applying, assuming we remember
to do so...
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: Kai Huang <kai.huang@intel.com>
Cc: "zhaotianrui@loongson.cn" <zhaotianrui@loongson.cn>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
"maobibo@loongson.cn" <maobibo@loongson.cn>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"maz@kernel.org" <maz@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"anup@brainfault.org" <anup@brainfault.org>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
Chao Gao <chao.gao@intel.com>,
"kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Farrah Chen <farrah.chen@intel.com>
Subject: Re: [PATCH v4 01/10] KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock
Date: Fri, 30 Aug 2024 06:57:14 -0700 [thread overview]
Message-ID: <ZtHPusyTNkQ_a1Y-@google.com> (raw)
In-Reply-To: <1f037b5604deb5f83f05e709b2edf3063372518f.camel@intel.com>
On Fri, Aug 30, 2024, Kai Huang wrote:
>
> > Reviewed-by: Kai Huang <kai.huang@intel.com>
> > Acked-by: Kai Huang <kai.huang@intel.com>
> >
>
> Hmm I must have done a lot for me to receive two credits (and for most patches
> in this series) :-)
>
> I think one Reviewed-by tag is good enough :-)
Heh, indeed. b4 has made me very lazy; I just `b4 am` the patches and let b4
grab all the trailers. I'm guessing something went awry in that flow (or maybe
you acked a previous version or something?)
Anyways, one of Paolo or I can clean this up when applying, assuming we remember
to do so...
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-08-30 13:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 4:35 [PATCH v4 00/10] KVM: Register cpuhp/syscore callbacks when enabling virt Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 01/10] KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 12:45 ` Huang, Kai
2024-08-30 12:45 ` Huang, Kai
2024-08-30 12:45 ` Huang, Kai
2024-08-30 13:57 ` Sean Christopherson [this message]
2024-08-30 13:57 ` Sean Christopherson
2024-08-30 13:57 ` Sean Christopherson
2024-09-03 0:48 ` Huang, Kai
2024-09-03 0:48 ` Huang, Kai
2024-09-03 0:48 ` Huang, Kai
2024-08-30 4:35 ` [PATCH v4 02/10] KVM: Register cpuhp and syscore callbacks when enabling hardware Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 03/10] KVM: Rename symbols related to enabling virtualization hardware Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 04/10] KVM: Rename arch hooks related to per-CPU virtualization enabling Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 12:42 ` Huang, Kai
2024-08-30 12:42 ` Huang, Kai
2024-08-30 12:42 ` Huang, Kai
2024-08-30 4:35 ` [PATCH v4 05/10] KVM: MIPS: Rename virtualization {en,dis}abling APIs to match common KVM Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 06/10] KVM: x86: " Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 12:45 ` Huang, Kai
2024-08-30 12:45 ` Huang, Kai
2024-08-30 12:45 ` Huang, Kai
2024-08-30 4:35 ` [PATCH v4 07/10] KVM: Add a module param to allow enabling virtualization when KVM is loaded Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 08/10] KVM: Add arch hooks for enabling/disabling virtualization Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` [PATCH v4 09/10] x86/reboot: Unconditionally define cpu_emergency_virt_cb typedef Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:35 ` Sean Christopherson
2024-08-30 4:36 ` [PATCH v4 10/10] KVM: x86: Register "emergency disable" callbacks when virt is enabled Sean Christopherson
2024-08-30 4:36 ` Sean Christopherson
2024-08-30 4:36 ` Sean Christopherson
2024-09-04 15:03 ` [PATCH v4 00/10] KVM: Register cpuhp/syscore callbacks when enabling virt Paolo Bonzini
2024-09-04 15:03 ` Paolo Bonzini
2024-09-04 15:03 ` Paolo Bonzini
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=ZtHPusyTNkQ_a1Y-@google.com \
--to=seanjc@google.com \
--cc=kvm-riscv@lists.infradead.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.