> Am 28.08.2019 um 20:41 schrieb Suthikulpanit, Suravee
> :
>
> Alex,
>
>> On 8/27/19 3:20 AM, Alexander Graf wrote:
>>
>>
>>> On 26.08.19 21:41, Suthikulpanit, Suravee wrote:
>>> Alex,
>>>
On 8/19/2019 4:57 AM, Alexander Graf wrote:
> On 15.08.19 18:25, Suthikulpanit,
Alex,
On 8/27/19 3:20 AM, Alexander Graf wrote:
>
>
> On 26.08.19 21:41, Suthikulpanit, Suravee wrote:
>> Alex,
>>
>> On 8/19/2019 4:57 AM, Alexander Graf wrote:
>>>
>>>
>>> On 15.08.19 18:25, Suthikulpanit, Suravee wrote:
Currently, there is no way to tell whether APICv is active
on a
On 26.08.19 21:41, Suthikulpanit, Suravee wrote:
Alex,
On 8/19/2019 4:57 AM, Alexander Graf wrote:
On 15.08.19 18:25, Suthikulpanit, Suravee wrote:
Currently, there is no way to tell whether APICv is active
on a particular VM. This often cause confusion since APICv
can be deactivated at ru
Alex,
On 8/19/2019 4:57 AM, Alexander Graf wrote:
>
>
> On 15.08.19 18:25, Suthikulpanit, Suravee wrote:
>> Currently, there is no way to tell whether APICv is active
>> on a particular VM. This often cause confusion since APICv
>> can be deactivated at runtime.
>>
>> Introduce a debugfs entry t
On 15.08.19 18:25, Suthikulpanit, Suravee wrote:
Currently, there is no way to tell whether APICv is active
on a particular VM. This often cause confusion since APICv
can be deactivated at runtime.
Introduce a debugfs entry to report APICv state of a VM.
This creates a read-only file:
/s
Currently, there is no way to tell whether APICv is active
on a particular VM. This often cause confusion since APICv
can be deactivated at runtime.
Introduce a debugfs entry to report APICv state of a VM.
This creates a read-only file:
/sys/kernel/debug/kvm/70860-14/apicv-state
Signed-off-by
6 matches
Mail list logo