public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, pm list <linux-pm@lists.linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [discuss] [PATCH] x86_64: Save registers in saved_context during suspend and hibernation
Date: Tue, 14 Aug 2007 00:26:26 +0200	[thread overview]
Message-ID: <200708140026.27519.rjw@sisk.pl> (raw)
In-Reply-To: <20070813225229.GF3406@bingen.suse.de>

On Tuesday, 14 August 2007 00:52, Andi Kleen wrote:
> On Mon, Aug 13, 2007 at 11:47:06PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> > 
> > During hibernation and suspend on x86_64 save CPU registers in the saved_context
> > structure rather than in a handful of separate variables.
> 
> Nice. These variables always annoyed me too when looking
> at that code.
> 
> >  	DEFINE(pbe_next, offsetof(struct pbe, next));
> >  	BLANK();
> > +	DEFINE(saved_context_rbx, offsetof(struct saved_context, rbx));
> 
> But is there a reason you can't just use a pt_regs and then an array
> for the crNs ? 

Hm, I think I can use pt_regs.  I'll try to redo the patch to use it.

OTOH, crNs already are members of saved_context and are accessed from C.
I wouldn't like to change that code.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

  reply	other threads:[~2007-08-13 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 21:47 [PATCH] x86_64: Save registers in saved_context during suspend and hibernation Rafael J. Wysocki
2007-08-13 22:52 ` Andi Kleen
2007-08-13 22:26   ` Rafael J. Wysocki [this message]
2007-08-14 17:27     ` [discuss] " Rafael J. Wysocki
2007-08-14 19:06       ` Pavel Machek

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=200708140026.27519.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    /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