[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDF7960.4080104@redhat.com>
Date: Wed, 07 Dec 2011 16:34:08 +0200
From: Avi Kivity <avi@...hat.com>
To: Eric B Munson <emunson@...bm.net>
CC: mingo@...hat.com, hpa@...or.com, arnd@...db.de,
ryanh@...ux.vnet.ibm.com, aliguori@...ibm.com, mtosatti@...hat.com,
jeremy.fitzhardinge@...rix.com, levinsasha928@...il.com,
Jan Kiszka <jan.kiszka@...mens.com>, kvm@...r.kernel.org,
linux-arch@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5 V5] Add ioctl for KVMCLOCK_GUEST_STOPPED
On 12/05/2011 10:19 PM, Eric B Munson wrote:
> Now that we have a flag that will tell the guest it was suspended, create an
> interface for that communication using a KVM ioctl.
>
> @@ -3295,6 +3295,10 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
>
> goto out;
> }
> + case KVMCLOCK_GUEST_PAUSED: {
> + r = kvm_set_guest_paused(vcpu);
> + break;
> + }
> default:
> r = -EINVAL;
> }
>
You could also do this purely from userspace by reading the kvmclock msr
and updating it. However, it's better to do this in the kernel to avoid
distributing responsibility for kvmclock across too many cooks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists