|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] Re: [PATCH 04/11] qemu_flush_work for remote vcpu execution |
Date: | Thu, 03 Dec 2009 14:35:39 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20090922 Fedora/3.0-3.9.b4.fc12 Thunderbird/3.0b4 |
On 12/03/2009 02:33 PM, Glauber Costa wrote:
On Thu, Dec 3, 2009 at 10:20 AM, Avi Kivity<address@hidden> wrote:On 12/02/2009 03:48 PM, Glauber Costa wrote:This function is similar to qemu-kvm's on_vcpu mechanism.Is similar? You're replacing on_vcpu().Yeah, it began similar, now it is pretty much the same thing, but using qemu-specific data structures
Keep the name then. The new name is misleading.
Totally synchronous, and guarantees that a given function will be executed at the specified vcpu. This patch also convert usage within the breakpoints system +void qemu_queue_work(CPUState *env, void (*func)(void *data), void *data);The name suggests that it is asynchronous. Why is this patch necessary?to keep gdbstub working.
"Because it fixes things". Please elaborate. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |