From owner-freebsd-virtualization@freebsd.org Mon Oct 15 17:25:45 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD34A10C2AB0 for ; Mon, 15 Oct 2018 17:25:45 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49CDD7CEC1 for ; Mon, 15 Oct 2018 17:25:45 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 053B310A87D; Mon, 15 Oct 2018 13:25:42 -0400 (EDT) Subject: Re: CFT: Reload LDTR after #VMEXIT on AMD-v in bhyve To: Mike Tancsa , freebsd-virtualization@freebsd.org References: <8282ebc8-7287-04fa-42d7-2c8501c4b979@sentex.net> <5a9c983c-3e10-58fd-be1f-bfffca2d9afd@sentex.net> From: John Baldwin Message-ID: Date: Mon, 15 Oct 2018 10:25:40 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <5a9c983c-3e10-58fd-be1f-bfffca2d9afd@sentex.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 15 Oct 2018 13:25:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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, 15 Oct 2018 17:25:45 -0000 On 10/15/18 10:11 AM, Mike Tancsa wrote: > On 10/15/2018 12:23 PM, John Baldwin wrote: >> >> That panic doesn't really make sense. :( The patch only changes behavior >> when you are actually running a guest, it doesn't affect anything in the >> vmm.ko initialization. > > I dont understand either. I have a few klds to load. Is it possible > something is getting initialized out of order at boot up time ?  r339355 > seems to have fixed it for me. But I suspect the real issue might come > back some other way > > https://lists.freebsd.org/pipermail/svn-src-head/2018-October/118820.html > > Regardless, I tested with your patch an amd64 and i386 vm and all seems > to work fine Ok, thanks! -- John Baldwin