Linux Container Development
 help / color / mirror / Atom feed
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 linux-cr] s390: save_access_regs for self-checkpoint
Date: Mon, 01 Mar 2010 14:20:21 -0500	[thread overview]
Message-ID: <4B8C1375.3060203@cs.columbia.edu> (raw)
In-Reply-To: <20100225170554.GA16683-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

Applied

Serge E. Hallyn wrote:
> When doing a self-checkpoint, we have to get the access registers
> from hw.
> 
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> ---
>  arch/s390/kernel/checkpoint.c |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/s390/kernel/checkpoint.c b/arch/s390/kernel/checkpoint.c
> index 03307e2..894bca3 100644
> --- a/arch/s390/kernel/checkpoint.c
> +++ b/arch/s390/kernel/checkpoint.c
> @@ -79,7 +79,11 @@ static void s390_copy_regs(int op, struct ckpt_hdr_cpu *h,
>  	}
>  
>  	CKPT_COPY_ARRAY(op, h->fprs, thr->fp_regs.fprs, NUM_FPRS);
> -	CKPT_COPY_ARRAY(op, h->acrs, thr->acrs, NUM_ACRS);
> +	if (op == CKPT_CPT && t == current) {
> +		save_access_regs(h->acrs);
> +	} else {
> +		CKPT_COPY_ARRAY(op, h->acrs, thr->acrs, NUM_ACRS);
> +	}
>  	CKPT_COPY_ARRAY(op, h->per_control_regs,
>  		      thr->per_info.control_regs.words.cr, NUM_CR_WORDS);
>  }

      parent reply	other threads:[~2010-03-01 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 17:05 [PATCH linux-cr] s390: save_access_regs for self-checkpoint Serge E. Hallyn
     [not found] ` <20100225170554.GA16683-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-03-01 19:20   ` Oren Laadan [this message]

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=4B8C1375.3060203@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