linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-um@lists.infradead.org
Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH] um: clean up mm creation
Date: Fri, 22 Sep 2023 21:30:35 +0200	[thread overview]
Message-ID: <c035e1648328db216fa5f34b4b9ac8a5f0bc82a1.camel@sipsolutions.net> (raw)
In-Reply-To: <20230922131638.2c57ec713d1c.Id11dff4b349e6a8f0136bb6bb09f6e01a80befbb@changeid>

On Fri, 2023-09-22 at 13:16 +0200, Johannes Berg wrote:
> Note that this fixes what seems like an issue - we look
> at current->mm when we copy, but that doesn't seem right
> in the case of clone() without copying the MM. This is
> probably saved by the forced flush later right now.
> 

After finding flush_thread(), that's clearly not true ;-)

But that basically leaves the only thing slower here the
start_userspace() itself, i.e. basically userspace_tramp()?

johannes

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

      parent reply	other threads:[~2023-09-22 19:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 11:16 [PATCH] um: clean up mm creation Johannes Berg
2023-09-22 13:41 ` Anton Ivanov
2023-09-22 14:20   ` Johannes Berg
2023-09-22 15:31   ` Benjamin Berg
2023-09-22 15:49     ` Anton Ivanov
2023-09-22 19:41   ` Johannes Berg
2023-09-22 20:08     ` Anton Ivanov
2023-09-22 20:12       ` Johannes Berg
2023-09-22 20:17         ` Anton Ivanov
2023-09-23  5:29         ` Anton Ivanov
2023-09-23 19:58           ` Johannes Berg
2023-09-22 13:49 ` Benjamin Berg
2023-09-22 18:15 ` Johannes Berg
2023-09-22 19:30 ` Johannes Berg [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=c035e1648328db216fa5f34b4b9ac8a5f0bc82a1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-um@lists.infradead.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).