On 23/02/2017 17:48, Radim Krcmar wrote:
> Doing it manually doesn't sound useful outside of testing ...
> is DPDK actually being used "dynamically"?
> (I thought that the setup is decided when the host boots.)
Or at the very least when the guest boots. I agree that KVM_ENABLE_CAP
is enough. H
2017-02-22 18:18-0300, Marcelo Tosatti:
> On Fri, Feb 03, 2017 at 06:03:37PM +0100, Radim Krcmar wrote:
>> 2017-02-02 15:47-0200, Marcelo Tosatti:
>> > For most VMs, modifying the host frequency is an undesired
>> > operation. Introduce ioctl to enable the guest to
>> > modify host CPU frequency.
On Fri, Feb 03, 2017 at 06:03:37PM +0100, Radim Krcmar wrote:
> 2017-02-02 15:47-0200, Marcelo Tosatti:
> > For most VMs, modifying the host frequency is an undesired
> > operation. Introduce ioctl to enable the guest to
> > modify host CPU frequency.
> >
> >
> > Signed-off-by: Marcelo Tosatti
2017-02-02 15:47-0200, Marcelo Tosatti:
> For most VMs, modifying the host frequency is an undesired
> operation. Introduce ioctl to enable the guest to
> modify host CPU frequency.
>
>
> Signed-off-by: Marcelo Tosatti
> ---
> arch/x86/include/asm/kvm_host.h |2 ++
> arch/x86/include/uapi
For most VMs, modifying the host frequency is an undesired
operation. Introduce ioctl to enable the guest to
modify host CPU frequency.
Signed-off-by: Marcelo Tosatti
---
arch/x86/include/asm/kvm_host.h |2 ++
arch/x86/include/uapi/asm/kvm.h |5 +
arch/x86/kvm/x86.c |
5 matches
Mail list logo