On 23/06/2015 05:24, Neel Natu wrote:
> Hi Andriy,
>
> On Mon, Jun 22, 2015 at 9:17 AM, Andriy Gapon 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 bl
Hi Andriy,
On Mon, Jun 22, 2015 at 9:17 AM, Andriy Gapon 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 blacklis
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
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 n
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, th
