Date: Sat, 26 Nov 2011 20:36:58 -0500
From: Michael Butler <imb@protected-networks.net>
To: Gleb Kurtsou <gleb.kurtsou@gmail.com>
Cc: FreeBSD current <freebsd-current@FreeBSD.org>, freebsd-emulation@FreeBSD.org, Andriy Gapon <avg@FreeBSD.org>
Subject: Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
Message-ID: <4ED1943A.90707@protected-networks.net>
In-Reply-To: <20111126163343.GA9150@reks>
References: <4ECF7440.4070300@entel.upc.edu> <4ECF8F05.8000007@protected-networks.net> <4ED0C40D.5010307@entel.upc.edu> <4ED0D963.1030702@entel.upc.edu> <4ED0DF1F.6090901@FreeBSD.org> <20111126163343.GA9150@reks>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/26/11 11:33, Gleb Kurtsou wrote: > On (26/11/2011 14:44), Andriy Gapon wrote: >> vm_phys_alloc_contig implementation has been recently changed and now it seems >> to require that vm_page_queue_free_mtx is held. > > Using new vm_page_alloc_contig() may be a better option here. Can't help > with patch, stuck with pre Nov 15 CURRENT myself. If I understand the change in locking semantics (post SVN r227568?), a good number of chunks of src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c need updating to follow this :-(. It is now insufficient to hold only the queue lock when calling vm_page_unwire or vm_page_free (and maybe others). The page itself must now also be locked, imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ED1943A.90707>