From: Johannes Berg <johannes@sipsolutions.net>
To: linux-um@lists.infradead.org
Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: Re: [PATCH v10] um: Enable preemption in UML
Date: Tue, 02 Jul 2024 12:24:47 +0200 [thread overview]
Message-ID: <a7e7f619bc73fff0f54dccc1129feb3c721cb49d.camel@sipsolutions.net> (raw)
In-Reply-To: <20240702102549.d2fcea450854.I12f5a53d80ec1e425e66ef272b1e95cb523b608e@changeid>
On Tue, 2024-07-02 at 10:25 +0200, Johannes Berg wrote:
> From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
>
> Since userspace state is saved in the MM process, kernel using
> FPU still doesn't really need to do anything, so this really
> is as simple as enabling preemption. The irq critical section
> in sigio_handler() needs preempt_disable()/preempt_enable().
For the record, my main interest in this is to unlock debugging for RCU
lists, sleep, etc.
johannes
prev parent reply other threads:[~2024-07-02 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 8:25 [PATCH v10] um: Enable preemption in UML Johannes Berg
2024-07-02 10:07 ` Anton Ivanov
2024-07-02 10:18 ` Johannes Berg
2024-07-02 10:20 ` Johannes Berg
2024-07-02 10:21 ` Anton Ivanov
2024-07-02 10:24 ` 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=a7e7f619bc73fff0f54dccc1129feb3c721cb49d.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