Date: Tue, 23 Jun 2015 09:47:09 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Neel Natu <neelnatu@gmail.com> Cc: Peter Grehan <grehan@FreeBSD.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@FreeBSD.org> Subject: Re: dtrace fbt vs vmm Message-ID: <558900ED.8060804@FreeBSD.org> In-Reply-To: <CAFgRE9Gr_fxK1_hLp9h_v6VHJG8B_a_hdwF1N1X6-ceRzYGV8g@mail.gmail.com> References: <5588317C.8020203@FreeBSD.org> <558832E8.9080407@freebsd.org> <55883537.3030400@FreeBSD.org> <CAFgRE9Gr_fxK1_hLp9h_v6VHJG8B_a_hdwF1N1X6-ceRzYGV8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23/06/2015 05:24, Neel Natu wrote: > Hi Andriy, > > On Mon, Jun 22, 2015 at 9:17 AM, Andriy Gapon <avg@freebsd.org> wrote: >> On 22/06/2015 19:08, Peter Grehan wrote: >>> Hi Andriy, >>> >>>> 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. >>> >>> Intel or AMD ? We've been able to run dtrace on Intel; less (to no) coverage on >>> AMD so there's quite possibly bugs there. >> >> Peter, >> >> it's AMD again. >> Thanks! >> > > This was an issue with 'svm_launch()' FBT tracing and is fixed in r284712. > > Details are in the commit message: > https://svnweb.freebsd.org/base?view=revision&revision=284712 Thank you! -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?558900ED.8060804>