From: Paolo Bonzini <bonzini@gnu.org>
To: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [HACK] make vmmouse work with KVM
Date: Mon, 17 Aug 2009 19:16:49 +0200 [thread overview]
Message-ID: <4A899081.9010508@gnu.org> (raw)
In-Reply-To: <20090817170017.GB1835@1und1.de>
On 08/17/2009 07:00 PM, Reimar Döffinger wrote:
> On Mon, Aug 17, 2009 at 06:44:11PM +0200, Paolo Bonzini wrote:
>> On 08/17/2009 05:45 PM, Reimar Döffinger wrote:
>>> + cpu_synchronize_state(env, 0);
>>> env->regs[R_EAX] = vmport_ioport_read(opaque, addr);
>>> + cpu_synchronize_state(env, 1);
>>
>> This is not needed because the sync is done in vmport_ioport_read, isn't it?
>
> Well... The cpu_synchronize_state could be dropped you are right, but
> here we write R_EAX so the cpu_synchronize_state(env, 1) is necessary.
> It might be slightly cleaner to rename the vmport_ioport_read (any name
> suggestions?) and add a wrapper for register_ioport_read that does the
> cpu_synchronize_state (so it looks similar to vmport_ioport_write).
Yes, that would look best and wouldn't have fooled me. Could
vmport_ioport_trigger be a decent name?
Paolo
Paolo
next prev parent reply other threads:[~2009-08-17 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 14:47 [Qemu-devel] [HACK] make vmmouse work with KVM Reimar Döffinger
2009-08-17 15:11 ` Anthony Liguori
2009-08-17 15:45 ` Reimar Döffinger
2009-08-17 16:44 ` [Qemu-devel] " Paolo Bonzini
2009-08-17 17:00 ` Reimar Döffinger
[not found] ` <20090817170017.GB1835@1und1.de>
2009-08-17 17:16 ` Paolo Bonzini [this message]
2009-08-17 17:32 ` Reimar Döffinger
2009-08-28 15:53 ` Reimar Döffinger
2009-08-28 17:16 ` Anthony Liguori
2009-08-17 15:29 ` [Qemu-devel] " Reimar Döffinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A899081.9010508@gnu.org \
--to=bonzini@gnu.org \
--cc=Reimar.Doeffinger@gmx.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).