Re: VIMAGE status

2009-05-02 Thread Julian Elischer

Olivier SMEDTS wrote:

2009/5/2 Julian Elischer :





can you just put #ifdef INVARIANTS around that line and do the compile
again?



It now compiles without errors.


yeah my svn machine went back to Cisco when I left there, so I
don't have an svn tree at the moment. otherwise I'd just check it in..

Now you have a VIMAGE system, just use it as normal and let us know if
you see any unusual behaviour.

If you have anything you can benchmark you might try both kernels and 
see if there are any performance differences.



thanks


___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: VIMAGE status

2009-05-02 Thread Olivier SMEDTS
2009/5/2 Julian Elischer :
> Olivier SMEDTS wrote:
>>
>> 2009/5/2 Julian Elischer :
>>>
>>> The VIMAGE code is nearly all in the the kernel.
>>>
>>> One is now able to make VIMAGE kernels (add options VIMAGE)
>>> though they don't actually allow you to make multiple
>>> vimages instances yet..
>>>
>>> The VIMAGE option enables all the low level changes needed
>>> throughout the kernel.
>>>
>
>> Here is a warning I have when building kernel with options VIMAGE and
>> INET6 :
>>
>> cc -c -O2 -pipe -march=native -fno-strict-aliasing -std=c99 -g -Wall
>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
>> -Wno-pointer-sign -fformat-extensions -nostdinc  -I.  -I/work/src/sys
>> -I/work/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
>> -include opt_global.h -fno-common -finline-limit=8000 --param
>> inline-unit-growth=100 --param large-function-growth=1000
>> -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2
>> -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float
>> -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
>> -Werror  /work/src/sys/netinet6/mld6.c
>> cc1: warnings being treated as errors
>> /work/src/sys/netinet6/mld6.c: In function 'vnet_mld_idetach':
>> /work/src/sys/netinet6/mld6.c:3145: warning: unused variable 'vnet_inet6'
>> *** Error code 1
>>
>
>>
>>
>
> I assume you do not have INVARIANTS..

Right, here is my kernel config file's content (amd64) :

cpu HAMMER
ident QUAD
makeoptions DEBUG=-g
options SCHED_ULE
options PREEMPTION
options IPI_PREEMPTION
options INET
options INET6
options FFS
options SOFTUPDATES
options UFS_DIRHASH
options COMPAT_IA32
options KTRACE
options STACK
options SYSVSHM
options SYSVMSG
options SYSVSEM
options _KPOSIX_PRIORITY_SCHEDULING
options KBD_INSTALL_CDEV
options STOP_NMI
options AUDIT
options VIMAGE
options PRINTF_BUFR_SIZE=128
options SMP
device acpi
device pci
device atkbdc
device atkbd
device vga
device sc
device loop
device ether
device pty
device bpf

>
> can you just put #ifdef INVARIANTS around that line and do the compile
> again?
>

It now compiles without errors.

-- 
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org- against HTML email & vCards  X
www: http://www.gid0.org- against proprietary attachments / \

  "Il y a seulement 10 sortes de gens dans le monde :
  ceux qui comprennent le binaire,
  et ceux qui ne le comprennent pas."
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: VIMAGE status

2009-05-02 Thread Julian Elischer

Olivier SMEDTS wrote:

2009/5/2 Julian Elischer :

The VIMAGE code is nearly all in the the kernel.

One is now able to make VIMAGE kernels (add options VIMAGE)
though they don't actually allow you to make multiple
vimages instances yet..

The VIMAGE option enables all the low level changes needed
throughout the kernel.




Here is a warning I have when building kernel with options VIMAGE and INET6 :

cc -c -O2 -pipe -march=native -fno-strict-aliasing -std=c99 -g -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions -nostdinc  -I.  -I/work/src/sys
-I/work/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
-include opt_global.h -fno-common -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000
-mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2
-mno-sse3 -mno-mmx -mno-3dnow  -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /work/src/sys/netinet6/mld6.c
cc1: warnings being treated as errors
/work/src/sys/netinet6/mld6.c: In function 'vnet_mld_idetach':
/work/src/sys/netinet6/mld6.c:3145: warning: unused variable 'vnet_inet6'
*** Error code 1








I assume you do not have INVARIANTS..

can you just put #ifdef INVARIANTS around that line and do the compile 
again?


___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: VIMAGE status

2009-05-02 Thread Olivier SMEDTS
2009/5/2 Julian Elischer :
> The VIMAGE code is nearly all in the the kernel.
>
> One is now able to make VIMAGE kernels (add options VIMAGE)
> though they don't actually allow you to make multiple
> vimages instances yet..
>
> The VIMAGE option enables all the low level changes needed
> throughout the kernel.
>
> The VIMAGE_GLOBALS option basically sets thing sback to how they were
> before.
>
> Having neither (the default) gives a kernel that is a kind of hybrid.
>
> The Hybrid state is what will go forward as 'NON-VIMAGE' mode
> and the VIMAGE_GLOBALS mode will probably go away in time as
> it complicates the code.
>
> The aim of this mail is to ask people to try add the VIMAGE option
> to their regular kernels and try use them as you woudl normally.
> You will not yet be able to use any new VIMAGE features but we
> should be fully compatible with previous kernels.

Here is a warning I have when building kernel with options VIMAGE and INET6 :

cc -c -O2 -pipe -march=native -fno-strict-aliasing -std=c99 -g -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions -nostdinc  -I.  -I/work/src/sys
-I/work/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
-include opt_global.h -fno-common -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000
-mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2
-mno-sse3 -mno-mmx -mno-3dnow  -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /work/src/sys/netinet6/mld6.c
cc1: warnings being treated as errors
/work/src/sys/netinet6/mld6.c: In function 'vnet_mld_idetach':
/work/src/sys/netinet6/mld6.c:3145: warning: unused variable 'vnet_inet6'
*** Error code 1

>
> Please report any concerns to the freebsd-virtualization@ mailing list.
>
> THEORETICALLY you should not see any changes in behaviour, however we have
> the following issues:
>
> * SCTP is not fully converted yet. add 'nooptions SCTP' for now if you
>  are not using it yet.
>
> * An NFS (crash) issue was reported. This MAY have been fixed...
>
>
> Theory tells us that all three kernel options should behave about the same
> but if you do try this, and have any benchmarking facilities,
> it would be incredibly useful if you could let us know if you see any
> performance changes between the three.
>
>
> thanks,
>
> Julian (currently running a VIMAGE kernel myself)
> ___
> freebsd-curr...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>



-- 
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org- against HTML email & vCards  X
www: http://www.gid0.org- against proprietary attachments / \

  "Il y a seulement 10 sortes de gens dans le monde :
  ceux qui comprennent le binaire,
  et ceux qui ne le comprennent pas."
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"