From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 1/1] fill vdso with syscall32_setup_pages if TIF_IA32 on x86_64
Date: Wed, 27 Jan 2010 15:51:47 -0500 [thread overview]
Message-ID: <4B60A763.4030806@cs.columbia.edu> (raw)
In-Reply-To: <20100127201037.GA23119-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Serge E. Hallyn wrote:
> Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
>> Cool !
>>
>> So what do we have working now for 64 bit kernel (for 32 bit kernel
>> we know it works...):
>>
>> 'restart' checkpointed
>> program program
>> ----------------------------------------
>> 64bit 64bit -> works
>> 32bit 32bit -> works
>>
>> 64bit 32bit -> ?????
>
> Actually the other way around works - /bin/restart_32 < 64bit.out
> works just fine. /bin/restart_64 < 32bit.out does not. The reason
> is that destroy_mm() ends up calling do_munmap on a 64-bit mapping
> after the switch to 32-bit had been made, and it refuses bc
> vma->vm_start > TASK_SIZE.
>
> Perhaps getting it to work will be as simple as temporarily switching
> back to 64-bit during destroy_mm().
Interesting, I didn't think about it.
So yes, switching temporarily should work. An alternative we can
do the call destroy_mm() earlier, as it may suit us.
>
>> Does it make sense to allow the opposite transition: 'restart' starts
>> as a 32bit and becomes a 64bit after it restores the state from the
>> image ?
>>
>> And what about if you checkpoint on a 32 bit kernel and try to
>> restart on a 64 bit kernel, and vice versa ? (in both cases, the
>> program of course is 32bit, and we can assume same physical host
>> for now).
>
> I have no hw right now where I could test such a thing. Do you?
>
Couldn't you use the same machine you are using - just reboot it
between checkpoint and restart with a 32bit kernel ... ?
Oren.
next prev parent reply other threads:[~2010-01-27 20:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 7:16 [PATCH 1/1] fill vdso with syscall32_setup_pages if TIF_IA32 on x86_64 Serge E. Hallyn
[not found] ` <20100127071636.GA16624-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-27 14:59 ` Oren Laadan
[not found] ` <Pine.LNX.4.64.1001270954120.8974-CXF6herHY6ykSYb+qCZC/1i27PF6R63G9nwVQlTi/Pw@public.gmane.org>
2010-01-27 20:10 ` Serge E. Hallyn
[not found] ` <20100127201037.GA23119-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-27 20:51 ` Oren Laadan [this message]
[not found] ` <4B60A763.4030806-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-01-27 21:10 ` Serge E. Hallyn
[not found] ` <20100127211052.GA27579-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-27 21:13 ` Oren Laadan
[not found] ` <4B60AC7E.2010908-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-05 23:38 ` Serge E. Hallyn
[not found] ` <20100205233800.GA17057-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-06 1:04 ` Oren Laadan
[not found] ` <4B6CC00C.2090509-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-06 6:26 ` Matt Helsley
[not found] ` <20100206062650.GG3714-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-02-06 15:43 ` Oren Laadan
2010-02-08 17:40 ` Oren Laadan
2010-02-06 17:09 ` Serge E. Hallyn
[not found] ` <20100206170902.GA20497-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2010-02-08 14:43 ` Oren Laadan
[not found] ` <4B7022FE.4060704-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-08 15:31 ` Serge E. Hallyn
[not found] ` <20100208153145.GB9120-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-08 16:17 ` Oren Laadan
[not found] ` <4B703936.3010200-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-02-09 14:54 ` Serge E. Hallyn
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=4B60A763.4030806@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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