Il 09/12/2013 07:55, Gleb Natapov ha scritto:
> On Sun, Dec 08, 2013 at 02:00:11PM +0100, Jan Kiszka wrote:
>> On 2013-11-27 17:58, Paolo Bonzini wrote:
>>> Il 25/11/2013 14:37, Gleb Natapov ha scritto:
VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
entry but most tim
On 2013-12-09 07:55, Gleb Natapov wrote:
> On Sun, Dec 08, 2013 at 02:00:11PM +0100, Jan Kiszka wrote:
>> On 2013-11-27 17:58, Paolo Bonzini wrote:
>>> Il 25/11/2013 14:37, Gleb Natapov ha scritto:
VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
entry but most times it
On Sun, Dec 08, 2013 at 02:00:11PM +0100, Jan Kiszka wrote:
> On 2013-11-27 17:58, Paolo Bonzini wrote:
> > Il 25/11/2013 14:37, Gleb Natapov ha scritto:
> >> VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
> >> entry but most times it can be avoided since values do not changes.
On 2013-11-27 17:58, Paolo Bonzini wrote:
> Il 25/11/2013 14:37, Gleb Natapov ha scritto:
>> VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
>> entry but most times it can be avoided since values do not changes.
>> Keep fields copy in memory to avoid unnecessary reads from vmcs.
Il 25/11/2013 14:37, Gleb Natapov ha scritto:
> VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
> entry but most times it can be avoided since values do not changes.
> Keep fields copy in memory to avoid unnecessary reads from vmcs.
>
> Signed-off-by: Gleb Natapov
> diff --git
VM_(ENTRY|EXIT)_CONTROLS vmcs fields are read/written on each guest
entry but most times it can be avoided since values do not changes.
Keep fields copy in memory to avoid unnecessary reads from vmcs.
Signed-off-by: Gleb Natapov
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index b2fe1c2..