linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: containers@lists.osdl.org, linuxppc-dev@ozlabs.org,
	Nathan Lynch <ntl@pobox.com>
Subject: Re: [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation
Date: Wed, 4 Feb 2009 09:54:06 -0600	[thread overview]
Message-ID: <20090204155406.GA2039@us.ibm.com> (raw)
In-Reply-To: <1233718789.16867.156.camel@pasglop>

Quoting Benjamin Herrenschmidt (benh@kernel.crashing.org):
> 
> > +struct cr_hdr_cpu {
> > +	struct pt_regs pt_regs;
> > +	/* relevant fields from thread_struct */
> > +	double fpr[32][TS_FPRWIDTH];
> > +	unsigned int fpscr;
> > +	int fpexc_mode;
> > +	/* unsigned int align_ctl; this is never updated? */
> > +	unsigned long dabr;
> > +};
> 
> Is there some version or other identification somewhere ? If not there
> should be. ie, we're going to add things here. For example, what about
> the vector registers ? Also, some CPUs will have more HW debug registers
> than just the DABR (we plan to add support for all the BookE architected
> IACs and DACs for example), etc...

The arch-independent checkpoint header does have kernel
maj:min:rev:patch info.  We expect to have to do more,
assuming that the .config can change the arch-dependent
cpu header (i.e. perhaps TS_FPRWIDTH could be changed).

-serge

  reply	other threads:[~2009-02-04 15:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 22:41 [RFC/PATCH 0/3] checkpoint/restart for powerpc Nathan Lynch
2009-01-28 22:41 ` [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation Nathan Lynch
2009-01-29  6:41   ` Oren Laadan
2009-01-29 21:40     ` Nathan Lynch
2009-01-30  0:11       ` Oren Laadan
2009-01-30 20:25         ` Nathan Lynch
2009-02-17  7:03       ` Nathan Lynch
2009-02-17 20:02         ` [PATCH 1/3 v2] powerpc: heckpoint/restart implementation Nathan Lynch
2009-02-24 19:58         ` [PATCH 1/3] powerpc: bare minimum checkpoint/restart implementation Serge E. Hallyn
2009-02-24 21:11           ` Nathan Lynch
2009-03-13  3:36             ` Oren Laadan
2009-03-13  3:31         ` Oren Laadan
2009-03-13 15:42           ` Cedric Le Goater
2009-03-16 18:37           ` Nathan Lynch
2009-03-17  6:55             ` Cedric Le Goater
2009-03-18  9:15               ` Oren Laadan
2009-01-30  4:01     ` Serge E. Hallyn
2009-01-30  3:55   ` Serge E. Hallyn
2009-02-04  3:39   ` Benjamin Herrenschmidt
2009-02-04 15:54     ` Serge E. Hallyn [this message]
2009-02-04 20:58       ` Benjamin Herrenschmidt
2009-02-04 23:44         ` Oren Laadan
2009-02-05  0:16           ` Benjamin Herrenschmidt
2009-02-05  3:30             ` Oren Laadan
2009-02-05 16:09             ` Serge E. Hallyn
2009-02-05 21:01               ` Benjamin Herrenschmidt
2009-01-28 22:41 ` [PATCH 2/3] powerpc: wire up checkpoint and restart syscalls Nathan Lynch
2009-01-28 22:41 ` [PATCH 3/3] allow checkpoint/restart on powerpc Nathan Lynch

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=20090204155406.GA2039@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=containers@lists.osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ntl@pobox.com \
    /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).