On 06.11.2013, at 18:08, Aneesh Kumar K.V
wrote:
> Alexander Graf writes:
>
>> On 11.10.2013, at 09:58, Aneesh Kumar K.V
>> wrote:
>>
>>> Alexander Graf writes:
>>>
On 11.10.2013, at 13:13, Aneesh Kumar K.V
wrote:
> From: "Aneesh Kumar K.V"
>
> With kvm en
Alexander Graf writes:
> On 11.10.2013, at 09:58, Aneesh Kumar K.V
> wrote:
>
>> Alexander Graf writes:
>>
>>> On 11.10.2013, at 13:13, Aneesh Kumar K.V
>>> wrote:
>>>
From: "Aneesh Kumar K.V"
With kvm enabled, we store the hash page table information in the
hypervis
On 11.10.2013, at 09:58, Aneesh Kumar K.V
wrote:
> Alexander Graf writes:
>
>> On 11.10.2013, at 13:13, Aneesh Kumar K.V
>> wrote:
>>
>>> From: "Aneesh Kumar K.V"
>>>
>>> With kvm enabled, we store the hash page table information in the
>>> hypervisor.
>>> Use ioctl to read the htab con
Alexander Graf writes:
> On 11.10.2013, at 13:13, Aneesh Kumar K.V
> wrote:
>
>> From: "Aneesh Kumar K.V"
>>
>> With kvm enabled, we store the hash page table information in the hypervisor.
>> Use ioctl to read the htab contents. Without this we get the below error when
>> trying to read the
On 11.10.2013, at 13:13, Aneesh Kumar K.V
wrote:
> From: "Aneesh Kumar K.V"
>
> With kvm enabled, we store the hash page table information in the hypervisor.
> Use ioctl to read the htab contents. Without this we get the below error when
> trying to read the guest address
>
> (gdb) x/10 do_f
From: "Aneesh Kumar K.V"
With kvm enabled, we store the hash page table information in the hypervisor.
Use ioctl to read the htab contents. Without this we get the below error when
trying to read the guest address
(gdb) x/10 do_fork
0xc0098660 : Cannot access memory at address
0xc00
