From: xieziyao <xieziyao@huawei.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] syscalls/aio: Convert libaio wrapper function to kernel syscall
Date: Tue, 4 May 2021 06:19:39 +0000 [thread overview]
Message-ID: <f4927571ebe74ea4b378e475befda3c7@huawei.com> (raw)
In-Reply-To: <YJDYAnOZgAgu5y6A@pevik>
Hi, Petr, Jan,
I am working on adapting the new API to the testsuite of syscalls/io_*.
At the same time, I prefer to replace libaio wrapper function with raw system call(tst_syscall(__NR_io_*)) just for the aio testcases of kernel/syscalls, since this method may be more straightforward, no need to rely on other libraries.
Glad to see your discussion and participation, thanks.
Kind regards,
Ziyao
From: Petr Vorel<pvorel@suse.cz<mailto:pvorel@suse.cz>>
To: Jan Stancek<jstancek@redhat.com<mailto:jstancek@redhat.com>>
Cc: xieziyao<xieziyao@huawei.com<mailto:xieziyao@huawei.com>>;ltp<ltp@lists.linux.it<mailto:ltp@lists.linux.it>>;Richard Palethorpe<rpalethorpe@suse.com<mailto:rpalethorpe@suse.com>>
Subject: Re: [LTP] [PATCH 0/3] syscalls/aio: Convert libaio wrapper function to kernel syscall
Time: 2021-05-04 13:13:53
Hi Jan,
> On Mon, May 3, 2021 at 9:03 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Ziyao,
> > > Instead of using the libaio wrapper function, the system call is changed
> > to be invoked via syscall(2).
> I probably missed some discussion. Why are we replacing it with syscall?
you haven't missed anything. io_destroy(ctx) (libaio.h) is being replaced with
raw syscall (tst_syscall(__NR_io_destroy, ctx).
Kind regards,
Petr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210504/f92c4e36/attachment-0001.htm>
prev parent reply other threads:[~2021-05-04 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 11:50 [LTP] [PATCH 0/3] syscalls/aio: Convert libaio wrapper function to kernel syscall Xie Ziyao
2021-04-29 11:50 ` [LTP] [PATCH 1/3] syscalls/io_destroy: " Xie Ziyao
2021-04-29 11:50 ` [LTP] [PATCH 2/3] syscalls/io_setup: " Xie Ziyao
2021-04-29 11:50 ` [LTP] [PATCH 3/3] syscalls/io_submit: " Xie Ziyao
2021-05-04 12:09 ` Cyril Hrubis
2021-05-06 12:27 ` Xie Ziyao
2021-05-06 12:57 ` Petr Vorel
2021-05-06 13:58 ` Cyril Hrubis
2021-05-06 18:22 ` Petr Vorel
2021-05-07 8:35 ` Xie Ziyao
2021-05-03 19:03 ` [LTP] [PATCH 0/3] syscalls/aio: " Petr Vorel
2021-05-04 4:08 ` Jan Stancek
2021-05-04 5:13 ` Petr Vorel
2021-05-04 6:19 ` xieziyao [this message]
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=f4927571ebe74ea4b378e475befda3c7@huawei.com \
--to=xieziyao@huawei.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