Re: [Xenomai] kvm freeze with ipipe patch for kernel 3.x

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2013-03-03 22:15, Gabriele Moabiti wrote:
>>>>>>>>
> 
>>>>>>>> I'm planning to get them merged into 3.8 first of all, maybe also into
>>>>>>>> 3.5 (as this is our current production baseline). No plans exist beyond
>>>>>>>> that. I'd rather like to leave older kernels alone to reduce maintenance
>>>>>>>> efforts (porting is simple, proper testing takes time).
>>>>>>>>
>>>>>>>> Also note that 3.2 is lacking much more critical fixes than those few
>>>>>>>> around KVM. IOW: Don't use it for anything serious with x86.
>>>>>>>
>>>>>>>
>>>>>>> Maybe reverting the mprotect/ipipe_pin_vma patches in the 3.2 branch, so
>>>>>>> as to avoid the zero page corruption, but take some faults sometimes
>>>>>>> would be a simple, feasible solution? 3.2 seems to have been chosen as a
>>>>>>> long term stable branch.
>>>>>>
>>>>>> Again, the problem is not writing the patches
>>>>>
>>>>>
>>>>> It is easy to forget a patch when (back)porting patches from an I-pipe
>>>>> to the other.
>>>>>
>>>>>> but testing all the stuff
>>>>>> in all necessary combinations.
> 
> So.. does 3.2 or 3.4 (at least an LTS kernel) will be supported or it's better to use only the 3.5.7 (EOL)?

For the time being and as you depend on KVM, use my queues/core-3.5 branch.

> I think if a kernel patch has serious problems should be marked as broken or unstable.

I agree, and I already requested to remove patches from the Xenomai code
base at least that contain known bugs. Should improve over the next
releases.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux