Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Wednesday 07 March 2007 07:57, 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. I merged them all for now. Thanks. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Wednesday 07 March 2007 07:57, 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. I merged them all for now. Thanks. -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 07:07:23PM +1100, Nigel Cunningham wrote: > Hi. > > On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote: > > On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > > > 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). > > > > > > > Hi Nigel, > > > > Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't > > have access to any machine supporting S3. I tested it at the time of my last > > posting and it had worked well. Appreciate your help. > > Tested with rc3 (rc2 wouldn't compile), and it works fine. > Thanks a lot Nigel. > If you're willing, please add > > Signed-off-by: Nigel Cunningham <[EMAIL PROTECTED]> > > or > > Acked-by: Nigel Cunningham <[EMAIL PROTECTED]> > > to the hibernation related parts as you see appropriate, since I helped > (albeit in a minor way compared to your work and Eric's work) with > preparing and testing them for RHEL5 and have confirmed they're still ok > in this version. Sure. You have helped a lot. I think either Andi or Andrew needs to add "Acked-by:" string while adding the hibernation related patches (Assuming they decide do pick up the patches.) Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
Hi. On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote: > On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > > 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). > > > > Hi Nigel, > > Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't > have access to any machine supporting S3. I tested it at the time of my last > posting and it had worked well. Appreciate your help. Tested with rc3 (rc2 wouldn't compile), and it works fine. If you're willing, please add Signed-off-by: Nigel Cunningham <[EMAIL PROTECTED]> or Acked-by: Nigel Cunningham <[EMAIL PROTECTED]> to the hibernation related parts as you see appropriate, since I helped (albeit in a minor way compared to your work and Eric's work) with preparing and testing them for RHEL5 and have confirmed they're still ok in this version. Regards, Nigel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
Hi. On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote: On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: 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). Hi Nigel, Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't have access to any machine supporting S3. I tested it at the time of my last posting and it had worked well. Appreciate your help. Tested with rc3 (rc2 wouldn't compile), and it works fine. If you're willing, please add Signed-off-by: Nigel Cunningham [EMAIL PROTECTED] or Acked-by: Nigel Cunningham [EMAIL PROTECTED] to the hibernation related parts as you see appropriate, since I helped (albeit in a minor way compared to your work and Eric's work) with preparing and testing them for RHEL5 and have confirmed they're still ok in this version. Regards, Nigel - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 07:07:23PM +1100, Nigel Cunningham wrote: Hi. On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote: On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: 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). Hi Nigel, Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't have access to any machine supporting S3. I tested it at the time of my last posting and it had worked well. Appreciate your help. Tested with rc3 (rc2 wouldn't compile), and it works fine. Thanks a lot Nigel. If you're willing, please add Signed-off-by: Nigel Cunningham [EMAIL PROTECTED] or Acked-by: Nigel Cunningham [EMAIL PROTECTED] to the hibernation related parts as you see appropriate, since I helped (albeit in a minor way compared to your work and Eric's work) with preparing and testing them for RHEL5 and have confirmed they're still ok in this version. Sure. You have helped a lot. I think either Andi or Andrew needs to add Acked-by: string while adding the hibernation related patches (Assuming they decide do pick up the patches.) Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > 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). > Ok. Got hold of a system which supports Standby mode (S1) and it works fine with 2.6.21-rc2 + relocatable patchset. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > 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). > Hi Nigel, Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't have access to any machine supporting S3. I tested it at the time of my last posting and it had worked well. Appreciate your help. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Wed, Mar 07, 2007 at 07:07:39AM -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) Hi Arjan, I have tested these patches for suspend to RAM and suspend to disk and they work fine. In the past we had few issues with suspend to disk and now these issues have been resolved in this patchset. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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. Regards, Nigel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
Arjan van de Ven <[EMAIL PROTECTED]> writes: > 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) It should be noted what broke was the non-portable constructs in the generic suspend code. In particular using __pa() outside of architecture code is not allowed. Using virt_to_phys() on addresses not part of the kernel's linear mapping is not generically supported. text/data are not required to be part of the kernel's linear mapping. This patchset now causes all code using these non-portable constructs to fail on x86_64. Which I think is a good thing so we can more easily spot these kinds of problems. Patches 15 and 16 appear to make the swpsuspend code rely on portable constructs. I will let Vivek reply to the amount of testing he has done in this area. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
Arjan van de Ven [EMAIL PROTECTED] writes: 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) It should be noted what broke was the non-portable constructs in the generic suspend code. In particular using __pa() outside of architecture code is not allowed. Using virt_to_phys() on addresses not part of the kernel's linear mapping is not generically supported. text/data are not required to be part of the kernel's linear mapping. This patchset now causes all code using these non-portable constructs to fail on x86_64. Which I think is a good thing so we can more easily spot these kinds of problems. Patches 15 and 16 appear to make the swpsuspend code rely on portable constructs. I will let Vivek reply to the amount of testing he has done in this area. Eric - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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. Regards, Nigel - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Wed, Mar 07, 2007 at 07:07:39AM -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) Hi Arjan, I have tested these patches for suspend to RAM and suspend to disk and they work fine. In the past we had few issues with suspend to disk and now these issues have been resolved in this patchset. Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: 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). Hi Nigel, Is it possible to test S3 with 2.6.21-rc2 kernels also. Right now I don't have access to any machine supporting S3. I tested it at the time of my last posting and it had worked well. Appreciate your help. Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/20] x86_64 Relocatable bzImage support (V4)
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: 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). Ok. Got hold of a system which supports Standby mode (S1) and it works fine with 2.6.21-rc2 + relocatable patchset. Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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. As on now, this mainly helps distros who have to ship an extra kernel compiled for a different physical address to capture the kernel crash dump. This patchset will allow distros and kdump users to use production kernel itself as dump capture kernel and there is no need to ship/build an extra kernel. I am hopeful people will find other interesting usages down the line. Eric has done all the heavy weight lifting requird to make this patchset work. Last time I posted this patchset (V3), there were minor comments which I have taken care of. Following are the changes since V3. - Reduced the usage of _AC() macro to only shift operations, as per Andi's comment. - Restored the CONFIG_PHYSICAL_START option. - Fixed few bugs with suspend to disk code path. It would be good if these patches get into -mm so that it can undergo more testing. I have been testing them and these just work fine for me. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/20] x86_64 Relocatable bzImage support (V4)
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. As on now, this mainly helps distros who have to ship an extra kernel compiled for a different physical address to capture the kernel crash dump. This patchset will allow distros and kdump users to use production kernel itself as dump capture kernel and there is no need to ship/build an extra kernel. I am hopeful people will find other interesting usages down the line. Eric has done all the heavy weight lifting requird to make this patchset work. Last time I posted this patchset (V3), there were minor comments which I have taken care of. Following are the changes since V3. - Reduced the usage of _AC() macro to only shift operations, as per Andi's comment. - Restored the CONFIG_PHYSICAL_START option. - Fixed few bugs with suspend to disk code path. It would be good if these patches get into -mm so that it can undergo more testing. I have been testing them and these just work fine for me. Thanks Vivek - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
