From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org,
Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>,
Dr. David Alan Gilbert <dgilbert@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: Who maintains util/userfaultfd.c?
Date: Thu, 19 Jan 2023 09:12:39 +0100 [thread overview]
Message-ID: <87v8l3hrig.fsf@secure.mitica> (raw)
In-Reply-To: <873587yqm7.fsf@pond.sub.org> (Markus Armbruster's message of "Thu, 19 Jan 2023 07:40:00 +0100")
Markus Armbruster <armbru@redhat.com> wrote:
> commit 0e9b5cd6b238b7ca9a3a50d957f50c37082705a0
> Author: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
> Date: Fri Jan 29 13:14:04 2021 +0300
>
> migration: introduce UFFD-WP low-level interface helpers
>
> Glue code to the userfaultfd kernel implementation.
> Querying feature support, createing file descriptor, feature control,
> memory region registration, IOCTLs on registered registered regions.
>
> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
> Message-Id: <20210129101407.103458-3-andrey.gruzdev@virtuozzo.com>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Fixed up range.start casting for 32bit
>
> added util/userfaultfd.c without covering it in MAINTAINERS. Only user
> is migration/ram.c, as far as I can tell. Should it be added to
> MAINTAINERS section "Migration"?
Hi
It should be added to the Migration maintainers. Who used to develop
in that particular corner is David.
Later, Juan.
next prev parent reply other threads:[~2023-01-19 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 6:40 Who maintains util/userfaultfd.c? Markus Armbruster
2023-01-19 8:12 ` Juan Quintela [this message]
2023-01-19 8:48 ` Markus Armbruster
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=87v8l3hrig.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=andrey.gruzdev@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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).