Skip to contentSkip to conversation

Contribution to Linux Kernel.

DISCUSSION Javier Romero 3 participants 6 messages Sep 25, 2017 – Nov 15, 2017 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi,

Last question, it will be the same to do Kernel testing on a virtual machine, or it will be better to do kernel testing over a no virtual machine?

Regards,

Javi

Quoted 49 lines · Ken Moffat
Quoted 8 lines · Javier Romero

Hi Ken,

Thank you for your answer.

Will it be better to work with linux-next Kernel for testing?

Regards.

Yes, no, maybe. I can't say what will work (process) for you, it depends in part on what you want to test, and how flakey that is at any particular time.

The -next kernels are transient - what is there today might be removed tomorrow, what is in linus's -rc kernels (and in point releases of stable kernels) usually remains unless somebody finds a showstopper bug.

If you are testing -next, expect to find more problems : in theory everything which gets to Linus's tree has been through an amount of testing before he applies it.

Most people have limited time to test kernels. Build farms usually run boot tests on all of these kernels, but do very little testing of whether or not any particular use is worse than before.

For any of these, expect problems to arise when least convenient to you. I try to test linus's -rc kernels on my own hardware, typically not until at least -rc2, and then once or twice after that.

On occasion I test patchsets which look interesting, usually I end up wishing I had not bothered (they claim to help things, but do little or nothing for my machines).

The other problem with testing, when you do find a real issue, is making sure it is repeatable so that you can bisect reliably.

In short, test what interests you. It's like writing or fixing code for the kernel as a hobby - work on what matters to you. Getting enough experience and visibility to become paid to code is a different thing entirely, I can't advise on that.

So, for me it is just a hobby (with a side order of "hope this new release doesn't break anything for me").

If you are not being paid for it, try to enjoy it.

ĸen

#3 lore raw
Quoted 15 lines · Javier Romero

Hi,

Last question, it will be the same to do Kernel testing on a virtual machine, or it will be better to do kernel testing over a no virtual machine?

Quoted 9 lines · Ken Moffat
Quoted 4 lines · Javier Romero

Hi Ken,

Will it be better to work with linux-next Kernel for testing?

Yes, no, maybe.  I can't say what will work (process) for you, it depends in part on what you want to test, and how flakey that is at any particular time.
[...]

both tests will be different, because VM is not bare metal machine and both will be valueable

Regards,
Kamil

#4 lore raw

Ken / Kamil,

Thank you very much for your time to answer.
Will create a VM and install all the enviroment needed to start testing. Again, thanks for your suggestions!
Regards,

Javi

Quoted 22 lines · Kamil Konieczny
Quoted 15 lines · Javier Romero

Hi,

Last question, it will be the same to do Kernel testing on a virtual machine, or it will be better to do kernel testing over a no virtual machine?

Quoted 9 lines · Ken Moffat
Quoted 4 lines · Javier Romero

Hi Ken,

Will it be better to work with linux-next Kernel for testing?

Yes, no, maybe. I can't say what will work (process) for you, it depends in part on what you want to test, and how flakey that is at any particular time.
[...]

both tests will be different, because VM is not bare metal machine and both will be valueable

Regards,
Kamil

#5 lore raw

Hi!

Quoted 4 lines

Thank you very much for your time to answer.
Will create a VM and install all the enviroment needed to start testing. Again, thanks for your suggestions!

Using linux-next on some older (32-bit) machine for daily use would be very valuable. As most people went 64-bit these days, there are errors introduced there.

I'm trying to do that on thinkpad x60, but more help would be welcome.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#6 lore raw

Hi Pavel,

Thank you for your answer.

I've a Raspberry PI 3 and read that this device use it's own fork of the Linux Kernel.

But do you think it would be useful to test linux-next on this device?

Regards

2017-10-23 6:29 GMT-03:00 Pavel Machek <[email protected]>:

Quoted 15 lines

Hi!

Quoted 4 lines

Thank you very much for your time to answer.
Will create a VM and install all the enviroment needed to start testing. Again, thanks for your suggestions!

Using linux-next on some older (32-bit) machine for daily use would be very valuable. As most people went 64-bit these days, there are errors introduced there.

I'm trying to do that on thinkpad x60, but more help would be welcome.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

A message that is not in the archive (sent off-list or not yet received): CAEH__nEMvScfyOanMUKrrQgq5PSueFhRoWM3YUd+3d2TSWyHWA@mail.gmail.com

#8 lore raw

Hi!

Quoted 6 lines

Thank you for your answer.

I've a Raspberry PI 3 and read that this device use it's own fork of the Linux Kernel.

But do you think it would be useful to test linux-next on this device?

Well, if you can get linux-next working there, yes, that would be nice. But this may be a bit too big task to start with.

But what I meant was running 32-bit linux-next on some spare computer. Not enough people test that version...
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html