From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Replace ltp_syscall with tst_syscall
Date: Thu, 20 Jan 2022 13:41:35 +0100 [thread overview]
Message-ID: <YelYf/wKsbjwvcHM@pevik> (raw)
In-Reply-To: <4ab9da33-ba2d-953b-515e-8b44a12dea6b@suse.com>
> Hi Petr!
> From my point of view, it would be nice if lapi code would only contain
> fallback code, without LTP API that requires tst_test.h or test.h. So it
> would be easy to split fallback code from "utilities" headers containing the
> most common functionalities to break the test if fallback functions are
> failing. This is the case of lapi/syscalls.h where tst_syscall is defined,
> but IMHO it should be defined out, somewhere in a "utils" header imported by
> tst_test.h or by tests which requires specific functionalities.
Well, we want to use tst_{brk,res}() in lapi :(. And these depend on counting
which mmap shared memory (see setup_ipc()). Thus things depend to each other.
Kind regards,
Petr
> This is possible only if all the tests are already in the new LTP API
> version tho, since old tests require to be refactored first.
Yep, that's the first thing to do, that's why we did not concentrated on
functional rewrite like this one, but on converting tests. Luckily lots of them
has been already rewritten.
Kind regards,
Petr
> Kind regards,
> Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-20 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 15:27 [LTP] [PATCH v1] Replace ltp_syscall with tst_syscall Andrea Cervesato
2022-01-20 12:16 ` Petr Vorel
2022-01-20 12:30 ` Andrea Cervesato via ltp
2022-01-20 12:41 ` Petr Vorel [this message]
2022-01-24 14:44 ` Cyril Hrubis
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=YelYf/wKsbjwvcHM@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@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