On 20.12.2013, at 06:24, Aneesh Kumar K.V
wrote:
> Alexander Graf writes:
>
>> On 19.12.2013, at 07:55, Aneesh Kumar K.V
>> wrote:
>>
>>> Alexander Graf writes:
>>>
On 07.11.2013, at 15:31, Aneesh Kumar K.V
wrote:
> From: "Aneesh Kumar K.V"
>
> With kvm en
Alexander Graf writes:
> On 19.12.2013, at 07:55, Aneesh Kumar K.V
> wrote:
>
>> Alexander Graf writes:
>>
>>> On 07.11.2013, at 15:31, Aneesh Kumar K.V
>>> wrote:
>>>
From: "Aneesh Kumar K.V"
With kvm enabled, we store the hash page table information in the
hypervis
On 19.12.2013, at 07:55, Aneesh Kumar K.V
wrote:
> Alexander Graf writes:
>
>> On 07.11.2013, at 15:31, 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
On Thu, Dec 19, 2013 at 12:25:57PM +0530, Aneesh Kumar K.V wrote:
> Alexander Graf writes:
>
> > This breaks if you run a 64-bit guest on a 32-bit host trying to
> > access memory beyond 4GB. In that case htab_base is hwaddr (64bit)
> > while uint8_t is only 32bit wide.
>
> Wow!! didn't know tha
Alexander Graf writes:
> On 07.11.2013, at 15:31, 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 07.11.2013, at 15:31, 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
