From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: [PATCH 1/1] restart only same bit-ness
Date: Mon, 8 Feb 2010 11:05:55 -0600 [thread overview]
Message-ID: <20100208170555.GA16943@us.ibm.com> (raw)
v19-rc3 actually tries to reset the TIF_IA32 flag according to
how it was set at checkpoint. It should not, at least for now.
Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
---
arch/x86/kernel/checkpoint.c | 21 +++++++++++++++------
1 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kernel/checkpoint.c b/arch/x86/kernel/checkpoint.c
index 5952e27..b01a2fc 100644
--- a/arch/x86/kernel/checkpoint.c
+++ b/arch/x86/kernel/checkpoint.c
@@ -283,12 +283,21 @@ int restore_thread(struct ckpt_ctx *ctx)
load_TLS(thread, cpu);
put_cpu();
-#if defined(CONFIG_X86_64) && defined(CONFIG_COMPAT)
- if (h->thread_info_flags & _TIF_IA32)
- set_thread_flag(TIF_IA32);
- else
- clear_thread_flag(TIF_IA32);
-#endif
+ {
+ int pre, post;
+ /*
+ * Eventually we'd like to support mixed-bit restart, but for
+ * now don't pretend to.
+ */
+ pre = test_thread_flag(TIF_IA32);
+ post = h->thread_info_flags & _TIF_IA32;
+ if ((pre && !post) || (post && !pre)) {
+ ret = -EINVAL;
+ ckpt_err(ctx, ret, "%d-bit restarting %d-bit\n",
+ pre ? 32 : 64, post ? 32 : 64);
+ goto out;
+ }
+ }
/* TODO: restore TIF flags as necessary (e.g. TIF_NOTSC) */
--
1.6.0.4
next reply other threads:[~2010-02-08 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 17:05 Serge E. Hallyn [this message]
[not found] ` <20100208170555.GA16943-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-08 20:39 ` [PATCH 1/1] restart only same bit-ness Matt Helsley
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=20100208170555.GA16943@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.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