From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>,
Aneesh Kumar K.V <aneesh.kumar@kernel.org>,
Luming Yu <luming.yu@shingroup.cn>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"npiggin@gmail.com" <npiggin@gmail.com>
Cc: "shenghui.qu@shingroup.cn" <shenghui.qu@shingroup.cn>,
"dawei.li@shingroup.cn" <dawei.li@shingroup.cn>,
"luming.yu@gmail.com" <luming.yu@gmail.com>,
"ke.zhao@shingroup.cn" <ke.zhao@shingroup.cn>
Subject: Re: [PATCH v1 2/2] powerpc/debug: hook to user return notifier infrastructure
Date: Tue, 20 Feb 2024 09:02:02 +0000 [thread overview]
Message-ID: <0638f0a2-782b-411f-9937-c62d99e9562b@csgroup.eu> (raw)
In-Reply-To: <2acd6623-952b-4659-bc26-c632e94560a8@csgroup.eu>
Le 20/02/2024 à 09:51, Christophe Leroy a écrit :
>
>
> Le 19/12/2023 à 07:33, Michael Ellerman a écrit :
>> Aneesh Kumar K.V <aneesh.kumar@kernel.org> writes:
>>> Luming Yu <luming.yu@shingroup.cn> writes:
>>>
>>>> Before we have powerpc to use the generic entry infrastructure,
>>>> the call to fire user return notifier is made temporarily in powerpc
>>>> entry code.
>>>>
>>>
>>> It is still not clear what will be registered as user return notifier.
>>> Can you summarize that here?
>>
>> fire_user_return_notifiers() is defined in kernel/user-return-notifier.c
>>
>> That's built when CONFIG_USER_RETURN_NOTIFIER=y.
>>
>> That is not user selectable, it's only enabled by:
>>
>> arch/x86/kvm/Kconfig: select USER_RETURN_NOTIFIER
>>
>> So it looks to me like (currently) it's always a nop and does nothing.
>>
>> Which makes me wonder what the point of wiring this feature up is :)
>> Maybe it's needed for some other feature I don't know about?
>>
>> Arguably we could just enable it because we can, and it currently does
>> nothing so it's unlikely to break anything. But that also makes it
>> impossible to test the implementation is correct, and runs the risk that
>> one day in the future when it does get enabled only then do we discover
>> it doesn't work.
>
> Opened an "issue" for the day we need it:
> https://github.com/KSPP/linux/issues/348
Correct one is https://github.com/linuxppc/issues/issues/477
next prev parent reply other threads:[~2024-02-20 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 3:13 [PATCH v1 2/2] powerpc/debug: hook to user return notifier infrastructure Luming Yu
2023-12-18 9:24 ` Aneesh Kumar K.V
2023-12-19 6:33 ` Michael Ellerman
2024-02-20 8:51 ` Christophe Leroy
2024-02-20 9:02 ` Christophe Leroy [this message]
2024-08-28 3:17 ` 虞陆铭
2024-08-28 5:46 ` Christophe Leroy
2024-08-28 6:50 ` Luming Yu
2024-08-28 7:27 ` Christophe Leroy
2024-08-29 9:58 ` Luming Yu
2024-09-02 8:34 ` Luming Yu
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=0638f0a2-782b-411f-9937-c62d99e9562b@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=aneesh.kumar@kernel.org \
--cc=dawei.li@shingroup.cn \
--cc=ke.zhao@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luming.yu@gmail.com \
--cc=luming.yu@shingroup.cn \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shenghui.qu@shingroup.cn \
/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).