From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: qemu-devel@nongnu.org, i.maximets@samsung.com
Subject: Re: [Qemu-devel] [PATCH 1/2] userfault: add pid into uffd_msg
Date: Tue, 4 Apr 2017 18:57:37 +0100 [thread overview]
Message-ID: <20170404175737.GL2147@work-vm> (raw)
In-Reply-To: <1489850003-5652-2-git-send-email-a.perevalov@samsung.com>
* Alexey Perevalov (a.perevalov@samsung.com) wrote:
> Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
> ---
> linux-headers/linux/userfaultfd.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/linux-headers/linux/userfaultfd.h b/linux-headers/linux/userfaultfd.h
> index 2ed5dc3..7b299a2 100644
> --- a/linux-headers/linux/userfaultfd.h
> +++ b/linux-headers/linux/userfaultfd.h
> @@ -77,6 +77,7 @@ struct uffd_msg {
> struct {
> __u64 flags;
> __u64 address;
> + pid_t pid;
> } pagefault;
Yes, but we'll just rerun the sync of the headers once your change
lands in the kernel.
Dave
> struct {
> --
> 1.8.3.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-04-04 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170318151328eucas1p24d754940723a0e777a2096a678a2094d@eucas1p2.samsung.com>
2017-03-18 15:13 ` [Qemu-devel] [RFC PATCH 0/2] Calcuate downtime for postcopy live migration Alexey Perevalov
2017-03-18 15:13 ` [Qemu-devel] [PATCH 1/2] userfault: add pid into uffd_msg Alexey Perevalov
2017-04-04 17:57 ` Dr. David Alan Gilbert [this message]
2017-04-05 14:25 ` Alexey Perevalov
2017-04-05 14:30 ` Dr. David Alan Gilbert
2017-03-18 15:13 ` [Qemu-devel] [PATCH 2/2] migration: calculate downtime on dst side Alexey Perevalov
2017-04-04 19:01 ` Dr. David Alan Gilbert
2017-04-05 14:31 ` Alexey Perevalov
2017-03-18 15:18 ` [Qemu-devel] [RFC PATCH 0/2] Calcuate downtime for postcopy live migration no-reply
2017-04-04 19:06 ` Dr. David Alan Gilbert
2017-04-05 14:33 ` Alexey Perevalov
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=20170404175737.GL2147@work-vm \
--to=dgilbert@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=i.maximets@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.