[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1173309302.13442.0.camel@nigel.suspend2.net>
Date: Thu, 08 Mar 2007 10:15:02 +1100
From: Nigel Cunningham <nigel@...el.suspend2.net>
To: Arjan van de Ven <arjan@...radead.org>
Cc: vgoyal@...ibm.com,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
Reloc Kernel List <fastboot@...ts.osdl.org>,
ebiederm@...ssion.com, akpm@...ux-foundation.org, ak@...e.de,
hpa@...or.com, magnus.damm@...il.com, lwang@...hat.com,
dzickus@...hat.com, pavel@...e.cz, rjw@...k.pl
Subject: Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
Hi.
On Thu, 2007-03-08 at 07:49 +1100, Nigel Cunningham wrote:
> Hi.
>
> On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote:
> > On Wed, 2007-03-07 at 12:27 +0530, Vivek Goyal wrote:
> > > Hi,
> > >
> > > Here is another attempt on x86_64 relocatable bzImage patches(V4). This
> > > patchset makes a bzImage relocatable and same kernel binary can be loaded
> > > and run from different physical addresses.
> >
> >
> > have these patches been extensively tested with various suspend
> > scenarios? (S1,S3,S4 in acpi speak or s2ram and s2disk in Linux speak)
>
> We did work on this for RHEL5, getting relocatable kernel support
> working fine with S4. While doing it and since, I've been running
> Suspend2 with the same patch.
>
> Since that work, Vivek has done more modifications, but I can confirm
> that the basic design is reliable with S4. Haven't tried S3, but can do.
> Will report back shortly.
S3 works okay here with a relocatable x86_64 kernel (2.6.20).
Regards,
Nigel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists