All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andreas Steinmetz <ast@domdv.de>, Pavel Machek <pavel@suse.cz>,
	Dave Jones <davej@codemonkey.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: amd64-agp vs. swsusp
Date: Thu, 21 Jul 2005 03:25:02 +0200	[thread overview]
Message-ID: <42DEF96E.60103@stud.feec.vutbr.cz> (raw)
In-Reply-To: <200507210123.16537.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Thursday, 21 of July 2005 00:07, Michal Schmidt wrote:
>>I also tried putting a printk before restore_processor_state(), but I'm 
>>not sure if it is safe to use printk there.
> 
> 
> Yes, it is, but you may be unable to see the message if the box reboots before
> it can be displayed.

OK, but then I also tried putting a 5s long busy wait there and the 
reset was not delayed. Therefore, the reset must be occurring before 
restore_processor_state().
Or is there a reason why
	for(i=0; i<5000; i++)
		udelay(1000);
wouldn't work as expected?

Michal

  reply	other threads:[~2005-07-21  1:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 20:51 amd64-agp vs. swsusp Michal Schmidt
2005-07-19 21:03 ` Andreas Steinmetz
2005-07-19 21:26   ` Michal Schmidt
2005-07-20  9:15     ` Rafael J. Wysocki
2005-07-20 22:07       ` Michal Schmidt
2005-07-20 23:23         ` Rafael J. Wysocki
2005-07-21  1:25           ` Michal Schmidt [this message]
2005-07-21  9:41             ` Rafael J. Wysocki
2005-07-21  5:31         ` Pavel Machek
2005-07-21 10:43           ` Michal Schmidt
2005-07-21 15:20             ` Pavel Machek
2005-07-21 15:24               ` Michal Schmidt
2005-07-21 20:05                 ` Rafael J. Wysocki
2005-08-04 21:25 ` Andrew Morton
2005-08-04 21:40   ` Pavel Machek
2005-08-07 22:17     ` Michal Schmidt
2005-08-04 21:54   ` Cal Peake
2005-08-05 10:32     ` Andreas Steinmetz
2005-08-05 22:38       ` Cal Peake
2005-08-06 10:40         ` Andreas Steinmetz

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=42DEF96E.60103@stud.feec.vutbr.cz \
    --to=xschmi00@stud.feec.vutbr.cz \
    --cc=ast@domdv.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.