From: Michael Ellerman <mpe@ellerman.id.au>
To: Kent Overstreet <kent.overstreet@linux.dev>,
linux-bcachefs@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Export kvm_guest static key, for bcachefs six locks
Date: Thu, 14 Sep 2023 12:26:53 +1000 [thread overview]
Message-ID: <87a5tp8p76.fsf@mail.lhotse> (raw)
In-Reply-To: <20230914000115.1035594-1-kent.overstreet@linux.dev>
Kent Overstreet <kent.overstreet@linux.dev> writes:
> bcachefs's six locks need kvm_guest, via
> ower_on_cpu() -> vcpu_is_preempted() -> is_kvm_guest()
>
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> Cc: linuxppc-dev@lists.ozlabs.org
> ---
> arch/powerpc/kernel/firmware.c | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
I'm happy for you to take this via your tree.
cheers
> diff --git a/arch/powerpc/kernel/firmware.c b/arch/powerpc/kernel/firmware.c
> index 20328f72f9f2..8987eee33dc8 100644
> --- a/arch/powerpc/kernel/firmware.c
> +++ b/arch/powerpc/kernel/firmware.c
> @@ -23,6 +23,8 @@ EXPORT_SYMBOL_GPL(powerpc_firmware_features);
>
> #if defined(CONFIG_PPC_PSERIES) || defined(CONFIG_KVM_GUEST)
> DEFINE_STATIC_KEY_FALSE(kvm_guest);
> +EXPORT_SYMBOL_GPL(kvm_guest);
> +
> int __init check_kvm_guest(void)
> {
> struct device_node *hyper_node;
> --
> 2.40.1
next prev parent reply other threads:[~2023-09-14 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 0:01 [PATCH] powerpc: Export kvm_guest static key, for bcachefs six locks Kent Overstreet
2023-09-14 2:26 ` Michael Ellerman [this message]
2023-09-14 19:50 ` Kent Overstreet
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=87a5tp8p76.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).