From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Chunfu Wen <chwen@redhat.com>
Cc: ltp <ltp-bounces+ricardo=marliere.net@lists.linux.it>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Add test case to cover the setting resource limit64 for process
Date: Wed, 19 Feb 2025 10:29:40 +0100 [thread overview]
Message-ID: <a611713d-898b-4e35-979b-13d52b28ec09@suse.com> (raw)
In-Reply-To: <CAAA2g-1G6q_+049zVD8=ZwuighYa6YHiXwzyXKUG8Uy3RAqaUw@mail.gmail.com>
Hi,
On 2/19/25 03:35, Chunfu Wen wrote:
> Hello,
> See inline comments.
> Best Regards,
> Chunfu Wen
>
> On Tue, Feb 18, 2025 at 9:29 PM Andrea Cervesato
> <andrea.cervesato@suse.com> wrote:
>
> Hi!
>
> The whole test is a duplication of the setrlimit06, so it's better to
> work on that one and to introduce the 64bits support using 64bit test
> variant.
> [chwen]Maybe it is a good idea to use separate setrlimit07.c file
> to support using 64bit testing, since it can bring into two
> benefits. 1)align with gettrlimit, it has separate
> file getrlimit03.c for 64bits, and it help easily extend more
> scernao cases for 64bits 2) Putting them in separate file is more
> convenient for users to select test case specfic 64bits testing
> once users need that.
>
If the goal is to generate a 64bit binary so users can easily run it
without variants, you don't need a new file but to edit the Makefile adding:
include $(abs_srcdir)/../utils/newer_64.mk
%_64: CPPFLAGS += -D_FILE_OFFSET_BITS=64
In this way you will have a 64bit binary for each test in the folder. At
that point, to switch between syscalls according to the 64bit
architecture definition is easy and runtest file will need to be updated
accordingly. If you take a look at the other test cases you will find
many examples on this method.
Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-19 9:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 2:31 [LTP] [PATCH] Add test case to cover the setting resource limit64 for process chunfuwen
2025-02-18 11:44 ` Ricardo B. Marlière
2025-02-18 13:29 ` Andrea Cervesato via ltp
2025-02-19 2:35 ` Chunfu Wen
2025-02-19 9:29 ` Andrea Cervesato via ltp [this message]
2025-02-19 6:47 ` [LTP] [PATCH v2] " chunfuwen
2025-02-19 16:44 ` Petr Vorel
2025-02-20 2:08 ` Li Wang
2025-02-20 9:35 ` Petr Vorel
2025-02-20 8:01 ` Chunfu Wen
2025-02-20 8:35 ` [LTP] [PATCH v3] " Chunfu Wen
2025-02-21 10:34 ` Andrea Cervesato via ltp
2025-02-24 3:06 ` Chunfu Wen
2025-02-24 3:07 ` [LTP] [PATCH v4] " Chunfu Wen
2025-02-26 1:15 ` Chunfu Wen
2025-02-28 3:41 ` Li Wang
2025-02-28 7:45 ` Andrea Cervesato via ltp
2025-02-28 8:39 ` Li Wang
2025-02-28 9:22 ` Li Wang
2025-02-28 11:37 ` Petr Vorel
2025-02-26 9:21 ` Li Wang
2025-02-19 16:50 ` [LTP] [PATCH v2] " Petr Vorel
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=a611713d-898b-4e35-979b-13d52b28ec09@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chwen@redhat.com \
--cc=ltp-bounces+ricardo=marliere.net@lists.linux.it \
/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