El 21/01/16 a les 21.38, Devin Teske ha escrit:
> 
>> On Jan 20, 2016, at 5:23 AM, Roger Pau Monné <roy...@freebsd.org> wrote:
>>
>> Author: royger
>> Date: Wed Jan 20 13:23:02 2016
>> New Revision: 294417
>> URL: https://svnweb.freebsd.org/changeset/base/294417
>>
>> Log:
>>  MFC r277215, r277291, r277418, r280953 and r280954:
>>
>>  loader: implement multiboot support for Xen Dom0
>>
>>  Note that only the subset of the multiboot specification needed in order to
>>  boot a Xen Dom0 is implemented.
>>
>>  Sponsored by: Citrix Systems R&D
>>
> 
> 
> Two issues with this merge.
> 
> First, this port now needs to be re-educated:
> https://svnweb.freebsd.org/ports/head/emulators/xen-kernel/Makefile?view=markup
>  
> <https://svnweb.freebsd.org/ports/head/emulators/xen-kernel/Makefile?view=markup>
> 
> 46 
> <https://svnweb.freebsd.org/ports/head/emulators/xen-kernel/Makefile?view=markup#l46>
>       .if ${OSVERSION} < 1100055
> 47 
> <https://svnweb.freebsd.org/ports/head/emulators/xen-kernel/Makefile?view=markup#l47>
>       IGNORE=         Only supported on recent FreeBSD 11
> 48 
> <https://svnweb.freebsd.org/ports/head/emulators/xen-kernel/Makefile?view=markup#l48>
>       .endif
> 
> Looking at your MFC, it looks like the OSVERSION check should allow some 
> version of 10.
> 
> Unfortunately (second issue), this patch doesn't touch 
> stable/10/sys/sys/param.h so the port has no clear way of accurately making 
> sure you're on a 10.x release that supports Xen.

Hm, no. This is a backport of the loader changes only, in order to make
it possible to boot a HEAD kernel plus Xen on a 10 world (and to make it
easier to MFC other loader changes to 10). The stable/10 kernel is still
not able to run as Xen Dom0, so the port is correct.

That's why I haven't added 'Relnotes: yes' to the commit message :).

Roger.
_______________________________________________
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Reply via email to