On 2018-05-03 17:17, Henning Schild wrote:
> Am Wed, 2 May 2018 08:43:10 +0200
> schrieb Jan Kiszka <[email protected]>:
> 
>> Hi all,
>>
>> there is currently a large set of almost 50 patches in next (I kept it
>> longer there to provide more time for reviews). Ralf just suggested
>> ~20 further patches for inmates refactorings. And there a couple of
>> smaller changes pending or promised.
>>
>> But then I'm hacking on almost 70 patches now that enable per-cpu page
>> tables and do a lot of refactoring around that, changes all across the
>> hypervisor. So I feel like we should set a tag before that starts to
>> hit the tree.
>>
>> IOW: v0.9 is upcoming. It's just about defining what we should put in
>> and what should be left for v0.10 (I'm not expecting to reach 1.0 with
>> the next-but-one step). IMHO:
>>
>> - next should go in (still time to review and test now!)
>> - from Ralf's work, at least some Communication Region revision field
>>   should be merged (to be written, still)
>> - maybe the rest of his patches as well, to be seen after round 2
>> - FF's man pages should go in (/me needs to look into installation if
>> no one else does that...)
>> - Peng's fix for parange (waiting for the patches, though)
>> - Henning's address prefix patch (once proven to work with all
>>   supported instructions)
>>
>> Anything I forgot? If all goes well, we could release somewhere mid of
>> next week.
> 
> I could have another go at the arm ivshmem example, if that sound like
> something for 0.9.

Ralf still faces troubles with cache coherence and MMU enabling which we
need for that. My feeling is that it could take longer.

Still, infrastructure work for it could be prepared and need not
necessarily wait.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to