Marcelo Tosatti wrote:
Batch pte updates and tlb flushes in lazy MMU mode.
v1-v2:
- report individual hypercall error code, have multicall return number of
processed entries.
- cover entire multicall duration with slots_lock instead of
acquiring/reacquiring.
But not all hypercalls
On Thu, Feb 21, 2008 at 05:52:25PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
Batch pte updates and tlb flushes in lazy MMU mode.
v1-v2:
- report individual hypercall error code, have multicall return number of
processed entries.
- cover entire multicall duration with slots_lock
Marcelo Tosatti wrote:
On Thu, Feb 21, 2008 at 05:52:25PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
Batch pte updates and tlb flushes in lazy MMU mode.
v1-v2:
- report individual hypercall error code, have multicall return number of
processed entries.
- cover entire
On Thu, Feb 21, 2008 at 08:30:04PM +0200, Avi Kivity wrote:
Perhaps you want to move that enforcement to the host.
This allows batching of future hypercalls (if appropriate) to be easy.
I'm still uneasy about it, though I have no rational reasons left now.
Oh, there is one: with a
Marcelo Tosatti wrote:
On Thu, Feb 21, 2008 at 08:30:04PM +0200, Avi Kivity wrote:
Perhaps you want to move that enforcement to the host.
This allows batching of future hypercalls (if appropriate) to be easy.
I'm still uneasy about it, though I have no rational reasons left
Batch pte updates and tlb flushes in lazy MMU mode.
v1-v2:
- report individual hypercall error code, have multicall return number of
processed entries.
- cover entire multicall duration with slots_lock instead of
acquiring/reacquiring.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Cc:
