avadh patel wrote:
> Hi Avi,
>
> Sorry for the wrong question. My revised question is as follows:
> How can I find the time spent between vm-enter and vm-exit ?
> In other words, How can I find the number of clock ticks spent in
> execution of VM's code between vm-enter and vm-exit ?
Linux 2.6.24
On Sun, Dec 23, 2007 at 07:37:40PM +0200, Avi Kivity wrote:
> The sched_in notifier needs to enable interrupts (but it must disable
> preemption to avoid recursion).
Ok this update fixes the smp_call_function deadlock.
Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
diff --git a/kernel/hack
Hi Avi,
Sorry for the wrong question. My revised question is as follows:
How can I find the time spent between vm-enter and vm-exit ?
In other words, How can I find the number of clock ticks spent in execution
of VM's code between vm-enter and vm-exit ?
Thanks,
Avadh
On Dec 24, 2007 2:05 AM, Av
Marcelo Tosatti wrote:
>
>> I believe that a new get_users_pages_inatomic() is more suitable;
>> Andrew, I'll write it if you agree. Alternatively, walk_page_range()
>> should take the lock itself, otherwise it is only usable if you don't
>> care about correctness?
>>
>
> Why not just expo
Marcelo Tosatti wrote:
btw, the call to gfn_to_page() can happen in page_fault() instead of
walk_addr(); that will reduce the amount of error handling, and will
simplify the callers to walk_addr() that don't need the page.
>>> But the gfn in question is
On Mon, Dec 24, 2007 at 08:50:13AM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >On Sun, Dec 23, 2007 at 10:41:07AM +0200, Avi Kivity wrote:
> >
> >>Avi Kivity wrote:
> >>
> >>>Exactly. But it is better to be explicit about it and pass the page
> >>>directly like you did before. I ha
Increase your size and confidence today with the #1 herbal
enlargement product on the market! http://rooterple.com/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http
On Mon, Dec 24, 2007 at 08:56:01AM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >It can acquire the pagetablelock in the callback handler. But then,
> >vm_normal_page() must also be exported.
> >
> >Are you guys OK with this ?
> >
> >
>
> Seems to me that requires fairly detailed mucking