|
From: | Avi Kivity |
Subject: | [Qemu-devel] Re: [PATCH 15/15] kvm: x86: Introduce kvmclock device to save/restore its state |
Date: | Mon, 07 Feb 2011 14:44:17 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7 |
On 02/07/2011 02:27 PM, Glauber Costa wrote:
> What exactly is your motivation to that ? I think mid/long-term we should be making machine initialization more common among architectures, not introducing more arch specific, or even worse, kvm specific parameters here.
A general note: there are several ways of being "kvm specific"; one of them is being tied to the implementation of kvm as the implementation of a virtual cpu in qemu. Another, with an example here, is a cpu feature that is only (or at first) present in kvm, but in principle may be supported by any cpu implementation, like tcg or a real cpu. It's important not to confuse the two; only the first needs all those hooks tied into the -accel infrastructure.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |