DOH. I had the 2 new ones backwards in the formats file.
thanks for pointing that out,
david
Liu, Eric E wrote:
>
> I mean the value of PTE_WRITE you write in the formats file ( 0x00020016
> )should be same with KVM_TRC_PTE_WRITE you define in kvm.h,
> but now it is 0x00020015. if not what yo
David S. Ahern wrote:
> inline.
>
> Liu, Eric E wrote:
>> David S. Ahern wrote:
>>> I am trying to add a trace marker and the data is coming out all
>>> 0's. e.g.,
>>>
>>> 0 (+ 0) PTE_WRITE vcpu = 0x0001 pid = 0x240d [
>>> gpa = 0x gpte = 0x
inline.
Liu, Eric E wrote:
> David S. Ahern wrote:
>> I am trying to add a trace marker and the data is coming out all 0's.
>> e.g.,
>>
>> 0 (+ 0) PTE_WRITE vcpu = 0x0001 pid = 0x240d [
>> gpa = 0x gpte = 0x ]
>>
>> Patch is attached. I know t
David S. Ahern wrote:
> I am trying to add a trace marker and the data is coming out all 0's.
> e.g.,
>
> 0 (+ 0) PTE_WRITE vcpu = 0x0001 pid = 0x240d [
> gpa = 0x gpte = 0x ]
>
> Patch is attached. I know the data is non-zero as I added an i
I am trying to add a trace marker and the data is coming out all 0's. e.g.,
0 (+ 0) PTE_WRITE vcpu = 0x0001 pid = 0x240d [ gpa =
0x gpte = 0x ]
Patch is attached. I know the data is non-zero as I added an if check before
calling the trace to o
