On 2014-04-11 21:35, Marcelo Tosatti wrote:
> On Fri, Apr 11, 2014 at 08:53:09PM +0200, Jan Kiszka wrote:
>> On 2014-04-11 20:35, Bandan Das wrote:
>>> Jan Kiszka writes:
>>>
On 2014-04-11 19:26, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-04-11 02:27, Bandan Das wrote:
>
Jan Kiszka writes:
> On 2014-04-11 20:35, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-04-11 19:26, Bandan Das wrote:
Jan Kiszka writes:
> On 2014-04-11 02:27, Bandan Das wrote:
>> Marcelo Tosatti writes:
>>
>>> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Ban
On Fri, Apr 11, 2014 at 08:53:09PM +0200, Jan Kiszka wrote:
> On 2014-04-11 20:35, Bandan Das wrote:
> > Jan Kiszka writes:
> >
> >> On 2014-04-11 19:26, Bandan Das wrote:
> >>> Jan Kiszka writes:
> >>>
> On 2014-04-11 02:27, Bandan Das wrote:
> > Marcelo Tosatti writes:
> >
>
Marcelo Tosatti writes:
> On Fri, Apr 11, 2014 at 08:22:13AM +0200, Jan Kiszka wrote:
>> On 2014-04-11 02:27, Bandan Das wrote:
>> > Marcelo Tosatti writes:
>> >
>> >> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
>> >>> For single context invalidation, we fall through to global
>
On Fri, Apr 11, 2014 at 08:22:13AM +0200, Jan Kiszka wrote:
> On 2014-04-11 02:27, Bandan Das wrote:
> > Marcelo Tosatti writes:
> >
> >> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
> >>> For single context invalidation, we fall through to global
> >>> invalidation in handle_invep
On Fri, Apr 11, 2014 at 08:22:13AM +0200, Jan Kiszka wrote:
> > But rethinking this again, I agree with you. If there's a hypervisor
> > with a single context invept implmentation that does not fallback,
> > this will unfortunately not work. Jan, do you agree with this ?
>
> A hypervisor that doe
On 2014-04-11 20:35, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-04-11 19:26, Bandan Das wrote:
>>> Jan Kiszka writes:
>>>
On 2014-04-11 02:27, Bandan Das wrote:
> Marcelo Tosatti writes:
>
>> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
>>> For singl
Jan Kiszka writes:
> On 2014-04-11 19:26, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-04-11 02:27, Bandan Das wrote:
Marcelo Tosatti writes:
> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
>> For single context invalidation, we fall through to global
On 2014-04-11 19:26, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-04-11 02:27, Bandan Das wrote:
>>> Marcelo Tosatti writes:
>>>
On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
> For single context invalidation, we fall through to global
> invalidation in handle_i
Jan Kiszka writes:
> On 2014-04-11 02:27, Bandan Das wrote:
>> Marcelo Tosatti writes:
>>
>>> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
For single context invalidation, we fall through to global
invalidation in handle_invept() except for one case - when
the oper
On 2014-04-11 02:27, Bandan Das wrote:
> Marcelo Tosatti writes:
>
>> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
>>> For single context invalidation, we fall through to global
>>> invalidation in handle_invept() except for one case - when
>>> the operand supplied by L1 is differe
Marcelo Tosatti writes:
> On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
>> For single context invalidation, we fall through to global
>> invalidation in handle_invept() except for one case - when
>> the operand supplied by L1 is different from what we have in
>> vmcs12. However, typ
On Mon, Mar 31, 2014 at 05:00:23PM -0400, Bandan Das wrote:
> For single context invalidation, we fall through to global
> invalidation in handle_invept() except for one case - when
> the operand supplied by L1 is different from what we have in
> vmcs12. However, typically hypervisors will only cal
For single context invalidation, we fall through to global
invalidation in handle_invept() except for one case - when
the operand supplied by L1 is different from what we have in
vmcs12. However, typically hypervisors will only call invept
for the currently loaded eptp, so the condition will
never
14 matches
Mail list logo