Skip to contentSkip to conversation

How does one get paid to work on the kernel?

DISCUSSION Nigel Cunningham 5 participants 18 messages Sep 18, 2003 – Sep 25, 2003

lore
Share & tools
lore
#0 lore raw

Hi all.

I'm about to finish my present employment, and have wondered about the possibility of getting paid to finish off the 2.4 version of Software Suspend and do the port to 2.6. How does one go about seeing if anyone might be interested in funding such a project for a few months?

Regards,

Nigel

Signature · 6 lines
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.
#1 lore raw
Quoted 4 lines · Nigel Cunningham

I'm about to finish my present employment, and have wondered about the possibility of getting paid to finish off the 2.4 version of Software Suspend and do the port to 2.6. How does one go about seeing if anyone might be interested in funding such a project for a few months?

Hasn't that already been done?

Signature · 2 lines
Måns Rullgård
[email protected]
#2 lore raw

There is support in the current kernel for Software Suspend, but the 2.4 version contains a lot of extra functionality that isn't present in 2.6 at the moment. (Support for HighMem, swap files, asynchronous I/O, a nicer user interface, compression...).

Quoted 8 lines · Måns Rullgård
Quoted 4 lines · Nigel Cunningham

I'm about to finish my present employment, and have wondered about the possibility of getting paid to finish off the 2.4 version of Software Suspend and do the port to 2.6. How does one go about seeing if anyone might be interested in funding such a project for a few months?

Hasn't that already been done?

Signature · 6 lines
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.
#3 lore raw
Quoted 4 lines · Nigel Cunningham

There is support in the current kernel for Software Suspend, but the 2.4 version contains a lot of extra functionality that isn't present in 2.6 at the moment. (Support for HighMem, swap files, asynchronous I/O, a nicer user interface, compression...).

I see. BTW, is it possible to boot normally, and later resume from the saved state, provided you don't touch any filesystems or swap areas involved in the suspend? I seem to recall reading somewhere that it would be possible, but I can't find any information on how to do it.

Signature · 2 lines
Måns Rullgård
[email protected]
#4 lore raw

Yes, provided as you say that you don't mount the file systems involved; mounting them will make journalling filesystems run their recoveries, which will in turn make the suspend image inconsistent. It's only really viable if the filesystems were mounted read only to start with... I've just added functionality to the 2.4 version for such a case.

Regards,

Nigel

Quoted 12 lines · Måns Rullgård
Quoted 4 lines · Nigel Cunningham

There is support in the current kernel for Software Suspend, but the 2.4 version contains a lot of extra functionality that isn't present in 2.6 at the moment. (Support for HighMem, swap files, asynchronous I/O, a nicer user interface, compression...).

I see. BTW, is it possible to boot normally, and later resume from the saved state, provided you don't touch any filesystems or swap areas involved in the suspend? I seem to recall reading somewhere that it would be possible, but I can't find any information on how to do it.

Signature · 6 lines
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.
#5 lore raw

Resuming from software suspend [was: Re: How does one get paid to work on the kernel?]

Quoted 5 lines · Nigel Cunningham

Yes, provided as you say that you don't mount the file systems involved; mounting them will make journalling filesystems run their recoveries, which will in turn make the suspend image inconsistent. It's only really viable if the filesystems were mounted read only to start with... I've just added functionality to the 2.4 version for such a case.

OK, is it possible with 2.6? The Kconfig help says you can. How is it done?

Signature · 2 lines
Måns Rullgård
[email protected]
#6 lore raw

Re: Resuming from software suspend [was: Re: How does one get paid to work on the kernel?]

If your filesystems were mounted readonly and the boot won't mount them writable, you should be fine with no special precautions. Last time I looked at 2.6 code, it didn't fix the suspend header when you use noresume. If that's still true, you should be able to boot with the noresume option, and then later normally.

(The 2.4 functionality I spoke of works differently, partly because it does fix the suspend header if you use the noresume option.)

Regards,

Nigel

Quoted 10 lines · Måns Rullgård
Quoted 5 lines · Nigel Cunningham

Yes, provided as you say that you don't mount the file systems involved; mounting them will make journalling filesystems run their recoveries, which will in turn make the suspend image inconsistent. It's only really viable if the filesystems were mounted read only to start with... I've just added functionality to the 2.4 version for such a case.

OK, is it possible with 2.6? The Kconfig help says you can. How is it done?

Signature · 6 lines
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.
#7 lore raw

Re: Resuming from software suspend

Quoted 5 lines · Nigel Cunningham

If your filesystems were mounted readonly and the boot won't mount them writable, you should be fine with no special precautions. Last time I looked at 2.6 code, it didn't fix the suspend header when you use noresume. If that's still true, you should be able to boot with the noresume option, and then later normally.

What I want to do is boot, do some things, and then resume the suspended state without rebooting between. Is that possible? I don't see any reason why it should be impossible to do, even if it's not currently supported.

Signature · 2 lines
Måns Rullgård
[email protected]
#8 lore raw

Re: Resuming from software suspend

Provided you're not making the data of the filesystem inconsistent with the state that the suspended image is expecting to see, you won't get any corruption. As to beginning a resume without rebooting, whether it would work would depend upon the size of the image, the amount of memory used when you start the resume and the degree of overlap between the two sets of memory.

Regards,

Nigel

Quoted 12 lines · Måns Rullgård
Quoted 5 lines · Nigel Cunningham

If your filesystems were mounted readonly and the boot won't mount them writable, you should be fine with no special precautions. Last time I looked at 2.6 code, it didn't fix the suspend header when you use noresume. If that's still true, you should be able to boot with the noresume option, and then later normally.

What I want to do is boot, do some things, and then resume the suspended state without rebooting between. Is that possible? I don't see any reason why it should be impossible to do, even if it's not currently supported.

Signature · 6 lines
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.
#9 lore raw

Re: Resuming from software suspend

Quoted 6 lines · Nigel Cunningham

Provided you're not making the data of the filesystem inconsistent with the state that the suspended image is expecting to see, you won't get any corruption. As to beginning a resume without rebooting, whether it would work would depend upon the size of the image, the amount of memory used when you start the resume and the degree of overlap between the two sets of memory.

If all processes are killed and all filesystem unmounted, there's not much left to use memory. Once you've decided to resume, there's not much point in keeping old processes running, is there?

Signature · 2 lines
Måns Rullgård
[email protected]
#10 lore raw

Re: Resuming from software suspend

In reply to Måns Rullgård
Quoted 5 lines · Måns Rullgård

What I want to do is boot, do some things, and then resume the suspended state without rebooting between. Is that possible? I don't see any reason why it should be impossible to do, even if it's not currently supported.

Just after booting, you know the state of the hardware (just initialised for most things that are not used to /boot/start resume/ from). You need to get the hardware in a sort of just-booted state before revering to the swsusp image you saved earlier because the drivers (might) expect the hardware to be in a certain state when they are started up by swsusp.

So you have to be carefull about the hardware (and not only the filesystem) state just before reverting to the swsusp image.

Bas.

#11 lore raw

Re: Resuming from software suspend

In reply to Måns Rullgård

Hi!

Quoted 4 lines

What I want to do is boot, do some things, and then resume the suspended state without rebooting between. Is that possible? I don't see any reason why it should be impossible to do, even if it's not currently supported.

Its not impossible, its just pretty tricky. You'd have to kill all userland and bring devices back to sane state.
(It is also going to be very tricky to *test*.)
Pavel

Signature · 2 lines
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
#12 lore raw
In reply to Måns Rullgård
Quoted 7 lines · Måns Rullgård

I see. BTW, is it possible to boot normally, and later resume from the saved state, provided you don't touch any filesystems or swap areas involved in the suspend? I seem to recall reading somewhere that it would be possible, but I can't find any information on how to do it.

Just wondering: what kind of use do you see for that?

ctually, I'm more thinking of a sort of freezing the state of processes rather then the kernel state. It would be nice to generalise this to be able to quick-(re)start applications (as long as their config file aren't changed).

Bas.

#13 lore raw
Quoted 8 lines · Bas Mevissen
Quoted 6 lines

I see. BTW, is it possible to boot normally, and later resume from the saved state, provided you don't touch any filesystems or swap areas involved in the suspend? I seem to recall reading somewhere that it would be possible, but I can't find any information on how to do it.

Just wondering: what kind of use do you see for that?

For instance, to load a module required to access the suspended image.

Signature · 2 lines
Måns Rullgård
[email protected]
#14 lore raw
Quoted 5 lines · Måns Rullgård
Quoted 2 lines

Just wondering: what kind of use do you see for that?

For instance, to load a module required to access the suspended image.

Why not loading it in the initrd image? Actually, the swsusp itself could (partly) be made a module if you load it in initrd :-)

Bas.

#15 lore raw
Quoted 7 lines · Bas Mevissen
Quoted 4 lines
Quoted 1 line

Just wondering: what kind of use do you see for that?

For instance, to load a module required to access the suspended image.

Why not loading it in the initrd image? Actually, the swsusp itself could (partly) be made a module if you load it in initrd :-)

You might want to do more than will fit in an initrd.

Signature · 2 lines
Måns Rullgård
[email protected]
#16 lore raw
In reply to Nigel Cunningham
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Nigel" == Nigel Cunningham <[email protected]> writes:

Nigel> There is support in the current kernel for Software Suspend, but Nigel> the 2.4 version contains a lot of extra functionality that isn't Nigel> present in 2.6 at the moment. (Support for HighMem, swap files, Nigel> asynchronous I/O, a nicer user interface, compression...).

Nigel is being modest and doesn't mention that the 2.4 version actually works, which is possibly its biggest advantage.

--J.

#17 lore raw

Hi!

Quoted 7 lines

Nigel> There is support in the current kernel for Software Suspend, but Nigel> the 2.4 version contains a lot of extra functionality that isn't Nigel> present in 2.6 at the moment. (Support for HighMem, swap files, Nigel> asynchronous I/O, a nicer user interface, compression...).

Nigel is being modest and doesn't mention that the 2.4 version actually works, which is possibly its biggest advantage.

2.6.0-test3 swsusp should work, too, unless you have driver problem. With ext2, ide and vesafb you should be able to suspend/resume correctly.
That might not be practical for you, but should be
good enough for fixing drivers.
Pavel

Signature · 2 lines
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...