Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1739225 > unrolled thread

Re: Contribution to Linux Kernel.

Started byJavier Romero <linux.kernel.programming@gmail.com>
First post2017-09-25 21:10 +0200
Last post2017-09-26 17:00 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Contribution to Linux Kernel. Javier Romero <linux.kernel.programming@gmail.com> - 2017-09-25 21:10 +0200
    Re: Contribution to Linux Kernel. Kamil Konieczny <k.konieczny@partner.samsung.com> - 2017-09-26 11:20 +0200
      Re: Contribution to Linux Kernel. Javier Romero <linux.kernel.programming@gmail.com> - 2017-09-26 17:00 +0200

#1739225 — Re: Contribution to Linux Kernel.

FromJavier Romero <linux.kernel.programming@gmail.com>
Date2017-09-25 21:10 +0200
SubjectRe: Contribution to Linux Kernel.
Message-ID<utGVr-27d-1@gated-at.bofh.it>
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


El 24/09/17 a las 17:25, Ken Moffat escribió:
> On Sun, Sep 24, 2017 at 12:52:08PM -0300, Javier Romero wrote:
>> 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

[toc] | [next] | [standalone]


#1739731

FromKamil Konieczny <k.konieczny@partner.samsung.com>
Date2017-09-26 11:20 +0200
Message-ID<utUc2-2OD-3@gated-at.bofh.it>
In reply to#1739225
On 25.09.2017 21:03, Javier Romero wrote:
> 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?
> 
> El 24/09/17 a las 17:25, Ken Moffat escribió:
>> On Sun, Sep 24, 2017 at 12:52:08PM -0300, Javier Romero wrote:
>>> 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

[toc] | [prev] | [next] | [standalone]


#1739955

FromJavier Romero <linux.kernel.programming@gmail.com>
Date2017-09-26 17:00 +0200
Message-ID<utZv3-66l-9@gated-at.bofh.it>
In reply to#1739731
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


El 26/09/17 a las 06:14, Kamil Konieczny escribió:
> On 25.09.2017 21:03, Javier Romero wrote:
>> 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?
>>
>> El 24/09/17 a las 17:25, Ken Moffat escribió:
>>> On Sun, Sep 24, 2017 at 12:52:08PM -0300, Javier Romero wrote:
>>>> 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
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web