Date: Thu, 20 Mar 2008 09:45:06 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, walt <w41ter@gmail.com> Subject: Re: vkernel & GSoC, some questions Message-ID: <200803201645.m2KGj6BP053980@apollo.backplane.com> References: <200803172158.m2HLwPSI021438@apollo.backplane.com> <frphq3$vce$1@ger.gmane.org> <200803192248.m2JMmkEn045986@apollo.backplane.com> <200803200854.26258.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:Except that you still need "real" hardware concurrency to see some races and
:that is important for testing. I'd worry about the overhead of any
:non-hardware assisted virtualization basically enforcing more serialization
:and coherency than is present in real-world systems meaning that code will
:work fine in the virtual environment and only break on real hardware. For
:example, when I worked on the rwlock implementation for FreeBSD 6/7, I wrote
:a custom kernel module that banged on the locks a lot and used KTR traces to
:verify that every single code path in the lock and unlock routines was
:exercised on a 4-way machine.
:
:I do think that vitualized environments can certainly be useful for many
:things (I used qemu for the recent GPT boot stuff and BTX changes and being
:able to single step in gdb for that was extremely useful and time-saving),
:but with concurrency races I think it is very important to make sure there is
:a lot of testing on full-speed, concurrent hardware.
:
:--
:John Baldwin
Hardware and vkernel/qemu environments exercise different code paths
and different timing mechanics. Certain bugs show up on vkernel's
more readily then on real hardware, while other bugs show up more
readily on real hardware then on vkernel's. I don't think one is
particularly better then another with regards to testing, they just
cover different continuums.
-Matt
Matthew Dillon
<dillon@backplane.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803201645.m2KGj6BP053980>