From: Miroslav Benes <mbenes@suse.cz>
To: boris.ostrovsky@oracle.com, jgross@suse.com,
sstabellini@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, jpoimboe@redhat.com
Cc: x86@kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
jslaby@suse.cz, Miroslav Benes <mbenes@suse.cz>
Subject: [PATCH 0/2] x86/xen: Make idle tasks reliable
Date: Thu, 12 Mar 2020 15:20:05 +0100 [thread overview]
Message-ID: <20200312142007.11488-1-mbenes@suse.cz> (raw)
The unwinder reports idle tasks' stack on XEN PV as unreliable which
complicates things for at least live patching. The two patches in the
series try to amend that by using similar approach as non-XEN x86 does.
However, I did not come up with a nice solution for secondary CPUs idle
tasks. The patch just shows the idea what should be done but it is an
ugly hack. Ideas are more than welcome.
Miroslav Benes (2):
x86/xen: Make the boot CPU idle task reliable
x86/xen: Make the secondary CPU idle tasks reliable
arch/x86/xen/smp_pv.c | 3 ++-
arch/x86/xen/xen-head.S | 14 +++++++++++++-
2 files changed, 15 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2020-03-12 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:20 Miroslav Benes [this message]
2020-03-12 14:20 ` [PATCH 1/2] x86/xen: Make the boot CPU idle task reliable Miroslav Benes
2020-03-12 15:04 ` [Xen-devel] " Andrew Cooper
2020-03-12 15:17 ` Miroslav Benes
2020-03-16 14:33 ` Boris Ostrovsky
2020-03-17 9:13 ` Miroslav Benes
2020-03-12 14:20 ` [RFC PATCH 2/2] x86/xen: Make the secondary CPU idle tasks reliable Miroslav Benes
2020-03-13 8:26 ` Jürgen Groß
2020-03-13 9:54 ` Miroslav Benes
2020-03-16 15:51 ` Miroslav Benes
2020-03-16 20:35 ` Josh Poimboeuf
2020-03-17 9:16 ` Miroslav Benes
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=20200312142007.11488-1-mbenes@suse.cz \
--to=mbenes@suse.cz \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 NNTP newsgroup(s).