Date: Thu, 20 Mar 2008 16:23:12 -0500 (CDT) From: Sergey Babkin <babkin@verizon.net> To: John Baldwin <jhb@freebsd.org>, Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-hackers@freebsd.org, walt <w41ter@gmail.com> Subject: Re: Re: vkernel & GSoC, some questions Message-ID: <12362883.2752181206048192946.JavaMail.root@vms071.mailsrvcs.net>
next in thread | raw e-mail | index | archive | help
>From: Matthew Dillon >To: John Baldwin <jhb@freebsd.org> >: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 > > 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 When testing multi-threaded code I sometimes insert artificial delays at different strategic locations. This widens any present race windows and makes the related bugs show up every time instead of once in a while. Of course, the resulting code works slower during the tests too :-) -SB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12362883.2752181206048192946.JavaMail.root>