From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Richard Weinberger <richard@nod.at>
Cc: Peter Lafreniere <peter@n8pjl.ca>,
Johannes Berg <johannes@sipsolutions.net>,
linux-um <linux-um@lists.infradead.org>
Subject: Re: [PATCH] um: Enable preemption in UML
Date: Thu, 21 Sep 2023 09:00:25 +0100 [thread overview]
Message-ID: <f30a2744-4a0d-910c-39da-771520d3f8e2@cambridgegreys.com> (raw)
In-Reply-To: <1267632977.64055.1695281421091.JavaMail.zimbra@nod.at>
On 21/09/2023 08:30, Richard Weinberger wrote:
> ----- Ursprüngliche Mail -----
>> Von: "anton ivanov" <anton.ivanov@cambridgegreys.com>
>> An: "Peter Lafreniere" <peter@n8pjl.ca>
>> CC: "Johannes Berg" <johannes@sipsolutions.net>, "linux-um" <linux-um@lists.infradead.org>, "richard" <richard@nod.at>
>> Gesendet: Donnerstag, 21. September 2023 09:12:33
>> Betreff: Re: [PATCH] um: Enable preemption in UML
>> On 20/09/2023 15:49, Peter Lafreniere wrote:
>>> On Wed, Sep 20, 2023 at 08:31, anton.ivanov@cambridgegreys.com wrote:
>>>> From: Anton Ivanov anton.ivanov@cambridgegreys.com
>>>>
>>>>
>>>> Preemption requires saving/restoring FPU state. This patch
>>>> adds support for it using GCC intrinsics.
>>>>
>>>> Signed-off-by: Anton Ivanov anton.ivanov@cambridgegreys.com
> I'm not so sure whether we should really directly start with CONFIG_PREEMPT.
I have managed to make it work except the IRQ return bit suggested by Peter. We are quite paranoid regarding locking and we are UP so nearly all of it worked out of the box.
> How about implementing CONFIG_PREEMPT_COUNT first?
Sure. Will try that today.
>
> Thanks,
> //richard
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-09-21 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 12:31 [PATCH] um: Enable preemption in UML anton.ivanov
2023-09-20 14:49 ` Peter Lafreniere
2023-09-20 15:03 ` Anton Ivanov
2023-09-21 7:12 ` Anton Ivanov
2023-09-21 7:30 ` Richard Weinberger
2023-09-21 8:00 ` Anton Ivanov [this message]
2023-09-20 15:04 ` Peter Lafreniere
2023-09-20 15:38 ` Anton Ivanov
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=f30a2744-4a0d-910c-39da-771520d3f8e2@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=peter@n8pjl.ca \
--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).