From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Fabiano Rosas <farosas@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org, npiggin@gmail.com
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix vcore_blocked tracepoint
Date: Tue, 24 May 2022 20:51:54 +1000 [thread overview]
Message-ID: <165338951438.1711920.10689960042369328588.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220328215831.320409-1-farosas@linux.ibm.com>
On Mon, 28 Mar 2022 18:58:31 -0300, Fabiano Rosas wrote:
> We removed most of the vcore logic from the P9 path but there's still
> a tracepoint that tried to dereference vc->runner.
>
>
Applied to powerpc/topic/ppc-kvm.
[1/1] KVM: PPC: Book3S HV: Fix vcore_blocked tracepoint
https://git.kernel.org/powerpc/c/ad55bae7dc364417434b69dd6c30104f20d0f84d
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Fabiano Rosas <farosas@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org, npiggin@gmail.com
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Fix vcore_blocked tracepoint
Date: Tue, 24 May 2022 10:51:54 +0000 [thread overview]
Message-ID: <165338951438.1711920.10689960042369328588.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220328215831.320409-1-farosas@linux.ibm.com>
On Mon, 28 Mar 2022 18:58:31 -0300, Fabiano Rosas wrote:
> We removed most of the vcore logic from the P9 path but there's still
> a tracepoint that tried to dereference vc->runner.
>
>
Applied to powerpc/topic/ppc-kvm.
[1/1] KVM: PPC: Book3S HV: Fix vcore_blocked tracepoint
https://git.kernel.org/powerpc/c/ad55bae7dc364417434b69dd6c30104f20d0f84d
cheers
next prev parent reply other threads:[~2022-05-24 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 21:58 [PATCH] KVM: PPC: Book3S HV: Fix vcore_blocked tracepoint Fabiano Rosas
2022-03-28 21:58 ` Fabiano Rosas
2022-03-29 8:19 ` Nicholas Piggin
2022-03-29 8:19 ` Nicholas Piggin
2022-05-24 10:51 ` Michael Ellerman [this message]
2022-05-24 10:51 ` Michael Ellerman
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=165338951438.1711920.10689960042369328588.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=farosas@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 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.