From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <51320F98.7010900@xenomai.org> Date: Sat, 02 Mar 2013 15:41:28 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <1362151982.5735.YahooMailNeo@web171205.mail.ir2.yahoo.com> <5130E0C7.80709@siemens.com> <5130E6FE.2070905@siemens.com> <1362185238.64750.YahooMailNeo@web171203.mail.ir2.yahoo.com> <5131B5A2.6000501@web.de> <5131DC27.80909@xenomai.org> <5131DE8D.4070701@web.de> <51320ACA.4070101@xenomai.org> <51320EDF.2090104@web.de> In-Reply-To: <51320EDF.2090104@web.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] kvm freeze with ipipe patch for kernel 3.x List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: "xenomai@xenomai.org" On 03/02/2013 03:38 PM, Jan Kiszka wrote: > On 2013-03-02 15:20, Gilles Chanteperdrix wrote: >> On 03/02/2013 12:12 PM, Jan Kiszka wrote: >> >>> On 2013-03-02 12:01, Gilles Chanteperdrix wrote: >>>> On 03/02/2013 09:17 AM, Jan Kiszka wrote: >>>> >>>>> On 2013-03-02 01:47, Gabriele Moabiti wrote: >>>>>> >>>>>> >>>>>> ----- Messaggio originale ----- >>>>>> >>>>>> Da: Jan Kiszka >>>>>> On 2013-03-01 18:09, Jan Kiszka wrote: >>>>>>> There is more broken, even in latest stable 3.5.7. See the patche= s at >>>>>>> [1] for a tested version. Unfortunately, I cannot update my tree = for 3.8 >>>>>>> ATM as git services seem to be down on xenomai.org. >>>>>> >>>>>> Does this and other important patches will be backported to 3.2? >>>>> >>>>> I'm planning to get them merged into 3.8 first of all, maybe also i= nto >>>>> 3.5 (as this is our current production baseline). No plans exist be= yond >>>>> that. I'd rather like to leave older kernels alone to reduce mainte= nance >>>>> efforts (porting is simple, proper testing takes time). >>>>> >>>>> Also note that 3.2 is lacking much more critical fixes than those f= ew >>>>> 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. >> >> >> I can test 4 combinations at once: i686 UP, i686 SMP and x86_64 (UP or= >> SMP), this leaves only one combination to test. >=20 > That's a small subset of the relevant variation. They come with enablin= g > different config options or using certain features. Do you have a test > setup for KVM on I-pipe e.g.? I'm not saying we catch them all with the= > development head, but adding more versions to the test matrix doesn't > make it better. I man 3, not 4 combinations. Anyway, I na=C3=AFvely test with only one =2Econfig, which recently switched from embedded like minimal kernel to debian like config. Do you have a list of the options combinations which necessitate separate tests? --=20 Gilles.