linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Paul Gofman <pgofman@codeweavers.com>,
	david@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
	kernel@collabora.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/userfaultfd: Support WP on multiple VMAs
Date: Fri, 17 Feb 2023 11:03:52 -0500	[thread overview]
Message-ID: <Y++laOl3OLw7zMPL@x1n> (raw)
In-Reply-To: <5f234d04-684e-9338-44b6-df23f7166578@collabora.com>

On Fri, Feb 17, 2023 at 03:59:25PM +0500, Muhammad Usama Anjum wrote:
> > But what if the user wants to do that during when you're tracing it using
> > userfaultfd?  Can it happen?
> Sorry, I've not tested tracing.

No worry.  It's not a request to test tracing; it's more or less to make
sure it works for you if it cannot trace a program that uses uffd.  If it's
not a problem to you, then it's not a problem to me either. And it's not
anything special to async but in general to uffd.  Thanks,

-- 
Peter Xu



      reply	other threads:[~2023-02-17 16:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 16:31 [PATCH v2 1/2] mm/userfaultfd: Support WP on multiple VMAs Muhammad Usama Anjum
2023-02-13 16:31 ` [PATCH v2 2/2] mm/userfaultfd: add VM_WARN_ONCE() Muhammad Usama Anjum
2023-02-13 16:54 ` [PATCH v2 1/2] mm/userfaultfd: Support WP on multiple VMAs Peter Xu
2023-02-13 17:50   ` Muhammad Usama Anjum
2023-02-13 21:11     ` Peter Xu
2023-02-14  8:49       ` Muhammad Usama Anjum
2023-02-14 21:50         ` Peter Xu
2023-02-15  7:08           ` Muhammad Usama Anjum
2023-02-15 21:45             ` Peter Xu
2023-02-16  6:25               ` Muhammad Usama Anjum
2023-02-16 16:41                 ` Peter Xu
2023-02-17 10:59                   ` Muhammad Usama Anjum
2023-02-17 16:03                     ` Peter Xu [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=Y++laOl3OLw7zMPL@x1n \
    --to=peterx@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pgofman@codeweavers.com \
    --cc=usama.anjum@collabora.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).