From: Furkan Caliskan <frn1furkan10@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: jgross@suse.com, jbeulich@suse.com, andrew.cooper3@citrix.com,
dfaggioli@suse.com, gwd@xenproject.org, roger@xenproject.org,
anthony.perard@vates.tech, julien@xen.org,
bertrand.marquis@arm.com, michal.orzel@amd.com,
Volodymyr_Babchuk@epam.com, teddy.astie@vates.tech,
Furkan Caliskan <frn1furkan10@gmail.com>
Subject: [PATCH v3 0/2] xen/sched: fix crashes when vcpu creation fails
Date: Mon, 31 Aug 2026 08:16:35 +0300 [thread overview]
Message-ID: <20260831051637.5029-1-frn1furkan10@gmail.com> (raw)
Furkan Caliskan (2):
xen/common: add vcpus_create() and keep max_vcpus in sync
xen/sched: core: kill unarmed timers on sched_init_vcpu() failure
xen/arch/arm/domain_build.c | 15 +++++++--------
xen/arch/x86/mm/mem_sharing.c | 11 ++---------
xen/common/domain.c | 24 ++++++++++++++++++++++++
xen/common/domctl.c | 19 ++++---------------
xen/common/sched/core.c | 16 +++++++++-------
xen/include/xen/domain.h | 1 +
6 files changed, 47 insertions(+), 39 deletions(-)
--
2.34.1
next reply other threads:[~2026-08-31 5:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:16 Furkan Caliskan [this message]
2026-08-31 5:16 ` [PATCH v3 1/2] xen/common: add vcpus_create() and keep max_vcpus in sync Furkan Caliskan
2026-08-31 8:13 ` Jürgen Groß
2026-08-31 9:13 ` Furkan Çalışkan
2026-08-31 9:32 ` [PATCH v4] " Furkan Caliskan
2026-08-31 9:45 ` [PATCH v3 1/2] " Andrew Cooper
2026-08-31 12:59 ` Jürgen Groß
2026-09-01 7:22 ` Jan Beulich
2026-09-01 8:07 ` Jürgen Groß
2026-09-01 8:15 ` Jan Beulich
2026-09-01 8:24 ` Jürgen Groß
2026-09-01 8:36 ` Jan Beulich
2026-09-01 9:03 ` Jürgen Groß
2026-08-31 5:16 ` [PATCH v3 2/2] xen/sched: core: kill unarmed timers on sched_init_vcpu() failure Furkan Caliskan
2026-08-31 8:15 ` Jürgen Groß
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=20260831051637.5029-1-frn1furkan10@gmail.com \
--to=frn1furkan10@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=dfaggioli@suse.com \
--cc=gwd@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger@xenproject.org \
--cc=teddy.astie@vates.tech \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.