From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: linux-um@lists.infradead.org
Subject: Re: [PATCH v4] um: Enable preemption in UML
Date: Fri, 22 Sep 2023 07:31:08 +0100 [thread overview]
Message-ID: <22f59852-d58e-00d4-3733-cddcc9d1e7e4@kot-begemot.co.uk> (raw)
In-Reply-To: <1842425402.67064.1695333308356.JavaMail.zimbra@nod.at>
On 21/09/2023 22:55, Richard Weinberger wrote:
> ----- Ursprüngliche Mail -----
>> Von: "anton ivanov" <anton.ivanov@cambridgegreys.com>
>> An: "richard" <richard@nod.at>
>> CC: "linux-um" <linux-um@lists.infradead.org>, "Johannes Berg" <johannes@sipsolutions.net>
>> Gesendet: Donnerstag, 21. September 2023 23:41:16
>> Betreff: Re: [PATCH v4] um: Enable preemption in UML
>> On 21/09/2023 22:02, Richard Weinberger wrote:
>>> ----- Ursprüngliche Mail -----
>>>> Von: "anton ivanov" <anton.ivanov@cambridgegreys.com>
>>>> An: "linux-um" <linux-um@lists.infradead.org>
>>>> CC: "Johannes Berg" <johannes@sipsolutions.net>, "richard" <richard@nod.at>,
>>>> "anton ivanov"
>>>> <anton.ivanov@cambridgegreys.com>
>>>> Gesendet: Donnerstag, 21. September 2023 17:55:22
>>>> Betreff: [PATCH v4] um: Enable preemption in UML
>>>> From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
>>>>
>>>> Preemption requires saving/restoring FPU state. This patch
>>>> adds support for it using GCC intrinsics.
>>> This patch triggers here the following splat:
>> Ack. I will look into it tomorrow.
> Thx!
> I had a brief look, UML's init_IRQ() seems to return now with interrupts enabled.
> Dunno why, I need some sleep now.
Tlb. Looking at other architectures (and specifically x86) it needs preempt_disable/enable around critical sections.
From there you may end up in the wrong state across the board.
>
>> There will be places where it will bomb out. F.E. I am chasing one is
>> triggered by the NFS server (it may be the same as in this trace - it
>> happens around the end of the initial setup).
>>
>> All in all it looks better than I expected.
> True that! :-)
>
> Thanks,
> //richard
>
> _______________________________________________
> linux-um mailing list
> linux-um@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
--
Anton R. Ivanov
https://www.kot-begemot.co.uk/
_______________________________________________
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 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 15:55 [PATCH v4] um: Enable preemption in UML anton.ivanov
2023-09-21 15:59 ` Anton Ivanov
2023-09-21 17:11 ` Peter Lafreniere
2023-09-21 21:02 ` Richard Weinberger
2023-09-21 21:41 ` Anton Ivanov
2023-09-21 21:55 ` Richard Weinberger
2023-09-22 6:31 ` Anton Ivanov [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=22f59852-d58e-00d4-3733-cddcc9d1e7e4@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).