* [PATCH] KVM: x86: explain 'no-kvmclock' kernel parameter
@ 2010-08-16 15:51 Jiri Kosina
2010-08-17 9:08 ` Avi Kivity
0 siblings, 1 reply; 2+ messages in thread
From: Jiri Kosina @ 2010-08-16 15:51 UTC (permalink / raw)
To: Avi Kivity, Marcelo Tosatti; +Cc: linux-kernel, kvm
no-kvmclock kernel parameter is missing its explanation in
Documentation/kernel-parameters.txt. Add it.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
---
Documentation/kernel-parameters.txt | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 2c85c06..0f9e299 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1693,6 +1693,8 @@ and is between 256 and 4096 characters. It is defined in the file
nojitter [IA64] Disables jitter checking for ITC timers.
+ no-kvmclock [X86,KVM] Disable paravirtualized KVM clock driver
+
nolapic [X86-32,APIC] Do not enable or use the local APIC.
nolapic_timer [X86-32,APIC] Do not use the local APIC timer.
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] KVM: x86: explain 'no-kvmclock' kernel parameter
2010-08-16 15:51 [PATCH] KVM: x86: explain 'no-kvmclock' kernel parameter Jiri Kosina
@ 2010-08-17 9:08 ` Avi Kivity
0 siblings, 0 replies; 2+ messages in thread
From: Avi Kivity @ 2010-08-17 9:08 UTC (permalink / raw)
To: Jiri Kosina; +Cc: Marcelo Tosatti, linux-kernel, kvm
On 08/16/2010 06:51 PM, Jiri Kosina wrote:
> no-kvmclock kernel parameter is missing its explanation in
> Documentation/kernel-parameters.txt. Add it.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-08-17 9:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-16 15:51 [PATCH] KVM: x86: explain 'no-kvmclock' kernel parameter Jiri Kosina
2010-08-17 9:08 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox