From: Vaibhav Jain <vaibhav@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 2/2] powerpc/pseries: Set CPU_FTR_DBELL according to ibm,pi-features
Date: Wed, 07 Feb 2024 22:46:11 +0530 [thread overview]
Message-ID: <87bk8sfb50.fsf@vajain21.in.ibm.com> (raw)
In-Reply-To: <20240207035220.339726-2-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> PAPR will define a new ibm,pi-features bit which says that doorbells
> should not be used even on architectures where they exist. This could be
> because they are emulated and slower than using the interrupt controller
> directly for IPIs.
>
> Wire this bit into the pi-features parser to clear CPU_FTR_DBELL, and
> ensure CPU_FTR_DBELL is not in CPU_FTRS_ALWAYS.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
Tested this patch on a PP64-LE lpar with the patch[1] and seeing the
relevant pi-feature bit CPU_FTR_DBELL in `cur_cpu_spec->cpu_features`
getting cleared.
[1]
https://lore.kernel.org/all/20240207035220.339726-1-npiggin@gmail.com
Hence,
Tested-by: Vaibhav Jain <vaibhav@linux.ibm.com>
--
Cheers
~ Vaibhav
next prev parent reply other threads:[~2024-02-07 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 3:52 [PATCH 1/2] powerpc/pseries: Add a clear modifier to ibm,pa/pi-features parser Nicholas Piggin
2024-02-07 3:52 ` [PATCH 2/2] powerpc/pseries: Set CPU_FTR_DBELL according to ibm,pi-features Nicholas Piggin
2024-02-07 17:16 ` Vaibhav Jain [this message]
2024-02-07 17:10 ` [PATCH 1/2] powerpc/pseries: Add a clear modifier to ibm,pa/pi-features parser Vaibhav Jain
2024-02-26 5:56 ` 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=87bk8sfb50.fsf@vajain21.in.ibm.com \
--to=vaibhav@linux.ibm.com \
--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 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).