From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 06/10] vmmouse: convert to qdev
Date: Fri, 18 Feb 2011 13:34:15 +0100 [thread overview]
Message-ID: <4D5E6747.6020603@redhat.com> (raw)
In-Reply-To: <AANLkTim5vB-O7a4qHO3pQCy57kuVh+S_hMG-BAg=D0+a@mail.gmail.com>
On 02/17/2011 08:52 PM, Blue Swirl wrote:
> On Wed, Feb 16, 2011 at 11:51 AM, Markus Armbruster<armbru@redhat.com> wrote:
>> Blue Swirl<blauwirbel@gmail.com> writes:
>>
>>> On Tue, Feb 15, 2011 at 12:07 PM, Markus Armbruster<armbru@redhat.com> wrote:
>>>> Anthony Liguori<anthony@codemonkey.ws> writes:
>>>>
>>>>> On 02/12/2011 11:03 AM, Markus Armbruster wrote:
>>>>>> Blue Swirl<blauwirbel@gmail.com> writes:
>>>>>>
>>>>>>
>>>>>>> Convert to qdev, also add a proper reset function.
>>>> [...]
>>>>>> Pointer properties are for dirty hacks only. Is there really no better
>>>>>> solution? Why does it have to be a property?
>>>>>>
>>>>>
>>>>> vmmouse is really just an extension to the PS2 Mouse. It's definitely
>>>>> not an ISA device.
>>>>>
>>>>> In terms of qdev enablement, I would just make it a boolean option to
>>>>> the PS2Mouse and not expose it as a top level device at all. It
>>>>> cannot exist without a PS2Mouse.
>>>>
>>>> Which means making it a separate qdev is wrong. That wrongness gave
>>>> rise to the dirty pointer property. Pointer property serves as canary
>>>> again.
>>>>
>>>> What now?
>>>
>>> I don't find pointer property use so dirty,
>>
>> See commit 036f7166.
>>
>>> but I'll try to combine
>>> the devices to see whether that makes sense.
>>
>> Appreciated.
>
> The attached patch would merge the devices, but I'm not so sure this
> is the right approach. Merging seems to be OK, the registration could
> be removed harder by adding a switch for known vmport values.
>
> But vmmouse couldn't be left out of the build anymore since it would
> be built per target (because of CPUState dependencies). That would be
> a step backwards. Perhaps the register access helpers should be pushed
> to board level.
Is there any fundamental reason why obj-i386-$(CONFIG_VMMOUSE) doesn't work?
Paolo
next prev parent reply other threads:[~2011-02-18 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 21:01 [Qemu-devel] [PATCH 06/10] vmmouse: convert to qdev Blue Swirl
2011-02-12 17:03 ` Markus Armbruster
2011-02-12 17:17 ` Blue Swirl
2011-02-13 15:42 ` Anthony Liguori
2011-02-15 10:07 ` Markus Armbruster
2011-02-15 17:22 ` Blue Swirl
2011-02-15 18:32 ` Blue Swirl
2011-02-16 9:51 ` Markus Armbruster
2011-02-17 19:52 ` Blue Swirl
2011-02-18 12:34 ` Paolo Bonzini [this message]
2011-02-18 18:04 ` [Qemu-devel] " Blue Swirl
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=4D5E6747.6020603@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--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).