From owner-freebsd-virtualization@FreeBSD.ORG Mon Jun 22 16:03:04 2015 Return-Path: Delivered-To: freebsd-virtualization@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 848842C5 for ; Mon, 22 Jun 2015 16:03:04 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BC5B3D14 for ; Mon, 22 Jun 2015 16:03:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA29361 for ; Mon, 22 Jun 2015 19:03:01 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Z74BY-0005Iu-Tt for freebsd-virtualization@freebsd.org; Mon, 22 Jun 2015 19:03:00 +0300 Message-ID: <5588317C.8020203@FreeBSD.org> Date: Mon, 22 Jun 2015 19:02:04 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: dtrace fbt vs vmm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 16:03:04 -0000 It seems that vmm contains functions for which it is not safe to enable fbt probes. At least, if I activate all fbt return probes with e.g. fbt:::return /self->trace && (int)arg1 == 28/ { printf("ret = %#x\n", arg0); stack(); (this is a part of larger script) while having an active bhyve VM, then I instantly get what looks like a possible triple-fault. I haven't investigated this issue further, but if there are any unsafe functions in vmm it would be nice to blacklist them in the fbt code. Perhaps blacklisting everything from vmm module could be a stopgap solution. -- Andriy Gapon