From: "Michal Suchánek" <msuchanek@suse.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Naveen N Rao <naveen@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Paul Mackerras <paulus@ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] powerpc/sstep: Unexport analyze_instr, emulate_vsx_load, emulate_vsx_store
Date: Tue, 1 Oct 2024 14:59:37 +0200 [thread overview]
Message-ID: <ZvvyOeT019FoMPPg@kitsune.suse.cz> (raw)
In-Reply-To: <8e6c75db-5c98-4f82-8151-5f86c53f4cf2@csgroup.eu>
On Tue, Oct 01, 2024 at 02:08:18PM +0200, Christophe Leroy wrote:
>
>
> Le 01/10/2024 à 12:08, Michal Suchanek a écrit :
> > There is no modular user of analyze_instr, and the latter two are only
> > used by sstep itself.
>
> analyze_instr() is used in arch/powerpc/kvm/emulate_loadstore.c which can be
> a module as far as I can see in Makefile:
>
> common-objs-y += powerpc.o emulate_loadstore.o
>
> kvm-book3s_64-module-objs := \
> $(common-objs-y) \
> book3s.o \
> book3s_rtas.o \
> $(kvm-book3s_64-objs-y)
>
> kvm-objs-$(CONFIG_KVM_BOOK3S_64) := $(kvm-book3s_64-module-objs)
>
> config KVM_BOOK3S_64
> tristate "KVM support for PowerPC book3s_64 processors"
Indeed, missed that it can be modular thruogh this indirection.
Thanks
Michal
>
>
> >
> > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> > ---
> > arch/powerpc/lib/sstep.c | 3 ---
> > 1 file changed, 3 deletions(-)
> >
> > diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
> > index e65f3fb68d06..a0557b0d9a24 100644
> > --- a/arch/powerpc/lib/sstep.c
> > +++ b/arch/powerpc/lib/sstep.c
> > @@ -863,7 +863,6 @@ void emulate_vsx_load(struct instruction_op *op, union vsx_reg *reg,
> > break;
> > }
> > }
> > -EXPORT_SYMBOL_GPL(emulate_vsx_load);
> > NOKPROBE_SYMBOL(emulate_vsx_load);
> > void emulate_vsx_store(struct instruction_op *op, const union vsx_reg *reg,
> > @@ -955,7 +954,6 @@ void emulate_vsx_store(struct instruction_op *op, const union vsx_reg *reg,
> > break;
> > }
> > }
> > -EXPORT_SYMBOL_GPL(emulate_vsx_store);
> > NOKPROBE_SYMBOL(emulate_vsx_store);
> > static nokprobe_inline int do_vsx_load(struct instruction_op *op,
> > @@ -3172,7 +3170,6 @@ int analyse_instr(struct instruction_op *op, const struct pt_regs *regs,
> > op->val = SRR1_PROGTRAP;
> > return 0;
> > }
> > -EXPORT_SYMBOL_GPL(analyse_instr);
> > NOKPROBE_SYMBOL(analyse_instr);
> > /*
next prev parent reply other threads:[~2024-10-01 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 10:08 [PATCH 1/2] powerpc/sstep: Unexport analyze_instr, emulate_vsx_load, emulate_vsx_store Michal Suchanek
2024-10-01 10:08 ` [PATCH 2/2] powerpc/sstep: make emulate_vsx_load and emulate_vsx_store static Michal Suchanek
2024-10-01 12:08 ` [PATCH 1/2] powerpc/sstep: Unexport analyze_instr, emulate_vsx_load, emulate_vsx_store Christophe Leroy
2024-10-01 12:59 ` Michal Suchánek [this message]
2024-10-01 12:29 ` Paul Mackerras
2024-10-01 13:03 ` [PATCH] powerpc/sstep: make emulate_vsx_load and emulate_vsx_store static Michal Suchanek
2024-11-17 12:09 ` 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=ZvvyOeT019FoMPPg@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=christophe.leroy@csgroup.eu \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulus@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