Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1587043
| From | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch 2/3] KVM: x86: introduce ioctl to allow frequency hypercalls |
| Date | 2017-02-23 18:40 +0100 |
| Message-ID | <te5wZ-4t0-13@gated-at.bofh.it> (permalink) |
| References | <t6tPQ-77C-17@gated-at.bofh.it> <t6tPQ-77C-35@gated-at.bofh.it> <t6PwZ-4x4-1@gated-at.bofh.it> <tdMun-7Lo-43@gated-at.bofh.it> <te4Ui-3Wg-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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. However, changing KVM_CPUID_FEATURES should be handled by userspace (KVM doesn't know about 0x400000xx leaves at all).
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [patch 2/3] KVM: x86: introduce ioctl to allow frequency hypercalls Marcelo Tosatti <mtosatti@redhat.com> - 2017-02-22 22:20 +0100
Re: [patch 2/3] KVM: x86: introduce ioctl to allow frequency hypercalls Radim Krcmar <rkrcmar@redhat.com> - 2017-02-23 18:00 +0100
Re: [patch 2/3] KVM: x86: introduce ioctl to allow frequency hypercalls Paolo Bonzini <pbonzini@redhat.com> - 2017-02-23 18:40 +0100
csiph-web