From owner-freebsd-hackers  Fri Jun 16 21:56:25 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 66E2437B8DB; Fri, 16 Jun 2000 21:56:17 -0700 (PDT)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (isdn8.imasy.or.jp [202.227.24.200])
	by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e5H4uC296370;
	Sat, 17 Jun 2000 13:56:12 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: acpi-jp@jp.freebsd.org, dcs@newsguy.com
Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: ACPI project progress report
In-Reply-To: <394AB05C.569DD4DD@newsguy.com>
References: <20000617002156A.iwasaki@jp.FreeBSD.org>
	<394AAE60.B6F0EE2A@newsguy.com>
	<394AB05C.569DD4DD@newsguy.com>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000617135611E.iwasaki@jp.FreeBSD.org>
Date: Sat, 17 Jun 2000 13:56:11 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 45
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

> "Daniel C. Sobral" wrote:
> > 
> > Mitsuru IWASAKI wrote:
> > >
> > >  - support S2, S3, S4 (hibernation) sleeping transition.  S4 sleep
> > >    require some hack in boot loader.... needs help.
> > 
> > I thought hibernation was entirely controlled by kernel? What do you
>                                                    ^^^^^^
> Err, BIOS.
> 
> > need?

Yes, we need to consider both.  In ACPI spec. 1.0b 9.1.4 S4 Sleeping
State, this is described that S4 supports two entry mechanisms: OS
initiated and BIOS initiated.

From: Intel, Microsoft, Toshiba
Subject: Advanced Configuration and Power Interface Specification 1.0b
Date: Tue, 2 Feb 1999 07:55:24 +0900
> In the OS-initiated S4 sleeping state, the OS is responsible for
> saving all system context. Before entering the S4 state, the OS will
> save context of all memory. Upon awakening, the OS will then restore
> the system context.  When the OS re-enumerates buses coming out of the
> S4 sleeping state, it will discover any devices that have come and
> gone, and configure devices as they are turned on.

I think OS-initiated S4 (hibernation) in FreeBSD has enough advantages
because we can do `Save-to-Disk' anywhere even on non-laptop machines
which BIOS doesn't support hibernation.
FreeBSD supports crash dump facility here, so I'm expecting that
`Save-to-Disk' by kernel would not be so difficult. We might need
dedicated swap partition for OS-initiated S4 because used swap areas
need to be protected for the system oprerations after awakening.
The boot loader is the best place for restoring the system context in
FreeBSD I think.

Unfortunately I don't have enough knowledge on crash dump and boot
loader to implement OS-initiated S4 transition (actually, this is not
related with ACPI at all).
I love to see someone say `hey!  I'll take this one!' :-)

Thanks


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message