From: Richard Weinberger <richard@nod.at>
To: anton ivanov <anton.ivanov@cambridgegreys.com>
Cc: linux-um <linux-um@lists.infradead.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v4] um: Enable preemption in UML
Date: Thu, 21 Sep 2023 23:02:04 +0200 (CEST) [thread overview]
Message-ID: <992345997.66924.1695330124883.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20230921155522.283582-1-anton.ivanov@cambridgegreys.com>
----- 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:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at init/main.c:992 start_kernel+0x541/0x6b6
Interrupts were enabled early
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.0-rc2-ga74d8f8592e5 #128
Stack:
60381b94 00000001 604d3d80 6002b6f6
60444bdd 00000001 604d3e20 6037ecfa
604d3db0 60389b2f 604d3da0 60381b94
Call Trace:
[<60381b94>] ? _printk+0x0/0x94
[<600212b1>] show_stack+0x13c/0x14b
[<60381b94>] ? _printk+0x0/0x94
[<6002b6f6>] ? um_set_signals+0x0/0x3f
[<6037ecfa>] ? sprintf+0x0/0x95
[<60389b2f>] dump_stack_lvl+0x4d/0x5a
[<60381b94>] ? _printk+0x0/0x94
[<60389b56>] dump_stack+0x1a/0x1c
[<60033ebc>] __warn+0xd9/0x109
[<60033fbd>] warn_slowpath_fmt+0xd1/0xdf
[<60033eec>] ? warn_slowpath_fmt+0x0/0xdf
[<60381b94>] ? _printk+0x0/0x94
[<60050e2c>] ? __blocking_notifier_chain_register+0x33/0x78
[<60381b94>] ? _printk+0x0/0x94
[<60050e83>] ? blocking_notifier_chain_register+0x12/0x14
[<6005fa92>] ? register_pm_notifier+0x1d/0x1f
[<600152c9>] ? random_init+0xc2/0x126
[<60381b94>] ? _printk+0x0/0x94
[<60001c40>] start_kernel+0x541/0x6b6
[<6004deb0>] ? parse_args+0x0/0x2b9
[<6002b609>] ? block_signals+0x0/0x16
[<60003b9d>] start_kernel_proc+0x49/0x4d
[<60061863>] ? kmsg_dump_register+0x6d/0x75
[<6001ffdb>] new_thread_handler+0x81/0xb2
[<60003b52>] ? kmsg_dumper_stdout_init+0x1a/0x1c
[<60022e52>] uml_finishsetup+0x54/0x59
---[ end trace 0000000000000000 ]---
x86_64 defconfig + CONFIG_PREEMPT_VOLUNTARY=y
Thanks,
//richard
_______________________________________________
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 21:02 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 [this message]
2023-09-21 21:41 ` Anton Ivanov
2023-09-21 21:55 ` Richard Weinberger
2023-09-22 6:31 ` 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=992345997.66924.1695330124883.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--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