From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
npiggin@gmail.com, christophe.leroy@csgroup.eu, shuah@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftest/powerpc/benchmark: remove requirement libc-dev
Date: Fri, 16 Aug 2024 09:01:43 +0530 [thread overview]
Message-ID: <ac8e76a3-35e4-41c0-a4f5-4987128fce26@linux.ibm.com> (raw)
In-Reply-To: <87wmkk27ka.fsf@mail.lhotse>
[-- Attachment #1: Type: text/plain, Size: 3294 bytes --]
On 8/13/24 1:11 PM, Michael Ellerman wrote:
> Madhavan Srinivasan<maddy@linux.ibm.com> writes:
>> Currently exec-target.c file is linked as static and this
>> post a requirement to install libc dev package to build.
> I think specifically the problem is that the test requires a static
> libc, which is packaged separately in some distros from the regular libc
> headers, am I right?
Thats right
> On Fedora the package is glibc-static, as opposed to glibc-devel, which
> the tests still require.
>
> So this patch removes the requirement to have glibc-static installed.
> Any idea what the package is called on Debian/Ubuntu?
This is what i could find in ubuntu VM, package is "libgcc-13-dev"
Description about this package
Binary package "libgcc-13-dev" in ubuntu noble Noble (24.04)
libgcc-13-dev GCC support library (development files) This package
contains the headers and static library files necessary for building C
programs which use libgcc, libgomp, libquadmath, libssp or libitm.
Maddy
>
> cheers
>
>> Without it, build-break when compiling selftest/powerpc/benchmark.
>>
>> CC exec_target
>> /usr/bin/ld: cannot find -lc: No such file or directory
>> collect2: error: ld returned 1 exit status
>>
>> exec_target.c is using "syscall" library function which
>> could be replaced with a inline assembly and the same is
>> proposed as a fix here.
>>
>> Suggested-by: Michael Ellerman<mpe@ellerman.id.au>
>> Signed-off-by: Madhavan Srinivasan<maddy@linux.ibm.com>
>> ---
>> Chnagelog v1:
>> - Add comment for clobber register and proper list of
>> clobber registers as suggested by Michael Ellerman and
>> Christophe Leroy
>>
>> .../selftests/powerpc/benchmarks/Makefile | 2 +-
>> .../selftests/powerpc/benchmarks/exec_target.c | 16 ++++++++++++++--
>> 2 files changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/testing/selftests/powerpc/benchmarks/Makefile b/tools/testing/selftests/powerpc/benchmarks/Makefile
>> index 1321922038d0..ca4483c238b9 100644
>> --- a/tools/testing/selftests/powerpc/benchmarks/Makefile
>> +++ b/tools/testing/selftests/powerpc/benchmarks/Makefile
>> @@ -18,4 +18,4 @@ $(OUTPUT)/context_switch: LDLIBS += -lpthread
>>
>> $(OUTPUT)/fork: LDLIBS += -lpthread
>>
>> -$(OUTPUT)/exec_target: CFLAGS += -static -nostartfiles
>> +$(OUTPUT)/exec_target: CFLAGS += -nostartfiles
>> diff --git a/tools/testing/selftests/powerpc/benchmarks/exec_target.c b/tools/testing/selftests/powerpc/benchmarks/exec_target.c
>> index c14b0fc1edde..a6408d3f26cd 100644
>> --- a/tools/testing/selftests/powerpc/benchmarks/exec_target.c
>> +++ b/tools/testing/selftests/powerpc/benchmarks/exec_target.c
>> @@ -7,10 +7,22 @@
>> */
>>
>> #define _GNU_SOURCE
>> -#include <unistd.h>
>> #include <sys/syscall.h>
>>
>> void _start(void)
>> {
>> - syscall(SYS_exit, 0);
>> + asm volatile (
>> + "li %%r0, %[sys_exit];"
>> + "li %%r3, 0;"
>> + "sc;"
>> + :
>> + : [sys_exit] "i" (SYS_exit)
>> + /*
>> + * "sc" will clobber r0, r3-r13, cr0, ctr, xer and memory.
>> + * Even though sys_exit never returns, handle clobber
>> + * registers.
>> + */
>> + : "r0", "r3", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
>> + "r11", "r12", "r13", "cr0", "ctr", "xer", "memory"
>> + );
>> }
>> --
>> 2.45.2
[-- Attachment #2: Type: text/html, Size: 4981 bytes --]
next prev parent reply other threads:[~2024-08-16 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 9:41 [PATCH v2] selftest/powerpc/benchmark: remove requirement libc-dev Madhavan Srinivasan
2024-08-13 7:41 ` Michael Ellerman
2024-08-16 3:31 ` Madhavan Srinivasan [this message]
2024-09-12 12:00 ` 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=ac8e76a3-35e4-41c0-a4f5-4987128fce26@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shuah@kernel.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).