From: lma <lma@suse.de>
To: Peter Xu <peterx@redhat.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, lma@suse.de,
dgilbert@redhat.com
Subject: Re: [PATCH 0/3] Postcopy migration: Add userfaultfd- user-mode-only capability
Date: Fri, 15 Oct 2021 13:38:06 +0800 [thread overview]
Message-ID: <7c0161fab24b06fa249061780a7f30d4@suse.de> (raw)
In-Reply-To: <YWjAqX13PYhBgbVh@t490s>
在 2021-10-15 07:43,Peter Xu 写道:
> On Thu, Oct 14, 2021 at 05:15:48PM +0800, Lin Ma wrote:
>> Since kernel v5.11, Unprivileged user (without SYS_CAP_PTRACE
>> capability)
>> must pass UFFD_USER_MODE_ONLY to userfaultd in case
>> unprivileged_userfaultfd
>> sysctl knob is 0.
>> Please refer to https://lwn.net/Articles/819834/ and the kernel
>> commits:
>> 37cd0575 userfaultfd: add UFFD_USER_MODE_ONLY
>> d0d4730a userfaultfd: add user-mode only option to
>> unprivileged_userfaultfd sysctl knob
>>
>> This patch set adds a migration capability to pass UFFD_USER_MODE_ONLY
>> for postcopy migration.
>
> Then it's at least no KVM, no vhost, am I right? Could I ask is there
> a real
> user behind this? Thanks,
Well, The "user-mode-only" has nothing to do with qemu's user-mode
emulation.
The unprivileged_userfaultfd sysctl knob controls whether unprivileged
users can use the userfaultfd system calls.
set it to 1 to allow unprivileged users to use the userfaultfd system
calls.
set it to 0 to restrict userfaultfd to only privileged users (with
SYS_CAP_PTRACE capability).
If host's unprivileged_userfaultfd sysctl knob is 0(The default value of
this knob is changed to 0 since host kernel v5.11):
Qemu must pass the UFFD_USER_MODE_ONLY flag when creating userfaultfd
object for postcopy migration in case qemu runs as unprivileged user.
Before host kernel v5.11, If host's unprivileged_userfaultfd sysctl knob
is 0, Then postcopy migration is not allowed in case qemu runs as
unprivileged user.
Thanks,
Lin
next prev parent reply other threads:[~2021-10-15 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 9:15 [PATCH 0/3] Postcopy migration: Add userfaultfd- user-mode-only capability Lin Ma
2021-10-14 9:15 ` [PATCH 1/3] migration: introduce postcopy-uffd-usermode-only capability Lin Ma
2021-10-14 9:15 ` [PATCH 2/3] migration: postcopy-uffd-usermode-only documentation Lin Ma
2021-10-14 9:15 ` [PATCH 3/3] tests: add postcopy-uffd-usermode-only capability into migration-test Lin Ma
2021-10-14 23:43 ` [PATCH 0/3] Postcopy migration: Add userfaultfd- user-mode-only capability Peter Xu
2021-10-15 5:38 ` lma [this message]
2021-10-15 6:12 ` Peter Xu
2021-10-15 8:16 ` lma
2021-10-15 8:28 ` Peter Xu
2021-10-15 9:49 ` lma
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=7c0161fab24b06fa249061780a7f30d4@suse.de \
--to=lma@suse.de \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).