From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, Keith Busch <kbusch@kernel.org>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH v4 1/6] io_uring/mock: add basic infra for test mock files
Date: Mon, 2 Jun 2025 07:44:16 -0600 [thread overview]
Message-ID: <d1282c0d-21fb-46b5-926c-8b11b0448969@kernel.dk> (raw)
In-Reply-To: <f6d26646-6cff-4aa2-bdf6-e63695f068a1@gmail.com>
On 5/30/25 12:21 PM, Pavel Begunkov wrote:
> On 5/30/25 19:04, Keith Busch wrote:
>> On Fri, May 30, 2025 at 01:51:58PM +0100, Pavel Begunkov wrote:
>>> +++ b/io_uring/mock_file.h
>>> @@ -0,0 +1,22 @@
>>> +#ifndef IOU_MOCK_H
>>> +#define IOU_MOCK_H
>>> +
>>> +#include <linux/types.h>
>>> +
>>> +struct io_uring_mock_probe {
>>> + __u64 features;
>>> + __u64 __resv[9];
>>> +};
>>> +
>>> +struct io_uring_mock_create {
>>> + __u32 out_fd;
>>> + __u32 flags;
>>> + __u64 __resv[15];
>>> +};
>>> +
>>> +enum {
>>> + IORING_MOCK_MGR_CMD_PROBE,
>>> + IORING_MOCK_MGR_CMD_CREATE,
>>> +};
>>> +
>>> +#endif
>>
>> Shouldn't this go in a linux/uapi header instead?
>
> Depends on whether we want distribute it to machines where it's
> not supposed to be enabled ever. I couldn't find any notion of
> debug headers in header installation, what people usually do
> in this case?
It still needs to go in uapi, as it is a user api of sorts. Otherwise
we'd need to duplicate it in test programs.
--
Jens Axboe
next prev parent reply other threads:[~2025-06-02 13:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 12:51 [PATCH v4 0/6] io_uring/mock: add basic infra for test mock files Pavel Begunkov
2025-05-30 12:51 ` [PATCH v4 1/6] " Pavel Begunkov
2025-05-30 13:28 ` Jens Axboe
2025-05-30 13:57 ` Pavel Begunkov
2025-05-30 14:36 ` Jens Axboe
2025-05-30 14:09 ` Pavel Begunkov
2025-05-30 14:12 ` Pavel Begunkov
2025-05-30 14:26 ` Pavel Begunkov
2025-05-30 14:41 ` Jens Axboe
2025-05-30 15:11 ` Pavel Begunkov
2025-05-30 15:30 ` Jens Axboe
2025-05-30 18:14 ` Pavel Begunkov
2025-06-02 15:19 ` Jens Axboe
2025-06-02 15:31 ` Pavel Begunkov
2025-06-02 15:41 ` Jens Axboe
2025-05-30 18:04 ` Keith Busch
2025-05-30 18:21 ` Pavel Begunkov
2025-06-02 13:44 ` Jens Axboe [this message]
2025-05-30 12:51 ` [PATCH v4 2/6] io_uring/mock: add cmd using vectored regbufs Pavel Begunkov
2025-05-30 13:25 ` Jens Axboe
2025-05-30 13:40 ` Pavel Begunkov
2025-05-30 14:37 ` Jens Axboe
2025-05-30 14:53 ` Pavel Begunkov
2025-05-30 15:34 ` Jens Axboe
2025-05-30 12:52 ` [PATCH v4 3/6] io_uring/mock: add sync read/write Pavel Begunkov
2025-05-30 12:52 ` [PATCH v4 4/6] io_uring/mock: allow to choose FMODE_NOWAIT Pavel Begunkov
2025-05-30 12:52 ` [PATCH v4 5/6] io_uring/mock: support for async read/write Pavel Begunkov
2025-05-30 13:27 ` Jens Axboe
2025-05-30 13:49 ` Pavel Begunkov
2025-05-30 14:38 ` Jens Axboe
2025-05-30 12:52 ` [PATCH v4 6/6] io_uring/mock: add trivial poll handler Pavel Begunkov
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=d1282c0d-21fb-46b5-926c-8b11b0448969@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@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