From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org
Cc: richard@nod.at
Subject: Re: [PATCH v5] um: Enable preemption in UML
Date: Fri, 22 Sep 2023 13:17:52 +0200 [thread overview]
Message-ID: <b6c39036cffa4a062fb89b8267e9ee618ee1313e.camel@sipsolutions.net> (raw)
In-Reply-To: <2e7356cb-07c9-bb62-7f4d-b0e4c7af88cf@cambridgegreys.com>
On Fri, 2023-09-22 at 11:55 +0100, Anton Ivanov wrote:
> On 22/09/2023 10:55, Johannes Berg wrote:
> > On Fri, 2023-09-22 at 11:51 +0200, Johannes Berg wrote:
> > > On Fri, 2023-09-22 at 10:19 +0100, Anton Ivanov wrote:
> > > > > So maybe that works - perhaps with a big comment?
> > > > Ack. Will add this to the patch and run it through its paces.
> > > >
> > > We can also just get rid of it entirely:
> > >
> > And then we can remove all the skas0 stuff, including init_thread_regs
> > and all.
> >
> > Seems the cost would be basically that we now pagefault everything
> > that's used between fork() and exec()? But is that so much and so
> > important?
>
> Needs testing :)
Yes. I sent a patch just now, works for me.
> Let's get the PREEMPT out of the door first.
Dunno. It has a conflict, but I think it's kind of a bugfix, the whole
mm creation copying from 'current' seems fishy when you consider
clone(CLONE_VM).
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2023-09-22 11:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 6:52 [PATCH v5] um: Enable preemption in UML anton.ivanov
2023-09-22 7:27 ` Richard Weinberger
2023-09-22 7:29 ` Anton Ivanov
2023-09-22 7:30 ` Johannes Berg
2023-09-22 7:38 ` Anton Ivanov
2023-09-22 7:40 ` Johannes Berg
2023-09-22 8:01 ` Anton Ivanov
2023-09-22 8:13 ` Johannes Berg
2023-09-22 8:40 ` Anton Ivanov
2023-09-22 8:41 ` Johannes Berg
2023-09-22 8:43 ` Johannes Berg
2023-09-22 9:04 ` Johannes Berg
2023-09-22 9:12 ` Anton Ivanov
2023-09-22 9:06 ` Anton Ivanov
2023-09-22 9:10 ` Johannes Berg
2023-09-22 9:14 ` Johannes Berg
2023-09-22 9:19 ` Anton Ivanov
2023-09-22 9:51 ` Johannes Berg
2023-09-22 9:55 ` Johannes Berg
2023-09-22 10:55 ` Anton Ivanov
2023-09-22 11:17 ` 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=b6c39036cffa4a062fb89b8267e9ee618ee1313e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).