From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Juan Quintela <quintela@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/4] fix/add CONFIG_* options for VMWare device emulation
Date: Wed, 02 Feb 2011 08:55:14 +0100 [thread overview]
Message-ID: <4D490DE2.6070806@redhat.com> (raw)
In-Reply-To: <AANLkTi=Yz2mc6CWQ4e_51KpgLWpx-21z6+RAhS8UvC5m@mail.gmail.com>
On 02/01/2011 07:10 PM, Blue Swirl wrote:
> One way to solve this which would preserve the device model would be
> to add stub devices. For example, hw/vmmouse-stub.c would be:
> void *vmmouse_init(void *m)
> {
> return NULL;
> }
This is the wrong direction, unless you can somehow automatically
generate the stub file.
The only other solution I can think of is weak symbols. There are
subtle differences between Windows and Linux weak symbols, but luckily
we do not care about it. See
http://cygwin.com/ml/cygwin/2010-04/msg00281.html
Paolo
next prev parent reply other threads:[~2011-02-02 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 16:53 [Qemu-devel] [PATCH 0/4] fix/add CONFIG_* options for VMWare device emulation Eduardo Habkost
2011-02-01 16:53 ` [Qemu-devel] [PATCH 1/4] Add config-devices.h again Eduardo Habkost
2011-02-01 18:14 ` Stefan Weil
2011-02-02 18:09 ` Eduardo Habkost
2011-02-04 14:48 ` [Qemu-devel] " Juan Quintela
2011-02-01 16:53 ` [Qemu-devel] [PATCH 2/4] skip pci_vmsvga_init() calls if CONFIG_VMWARE_VGA is disabled Eduardo Habkost
2011-02-01 16:53 ` [Qemu-devel] [PATCH 3/4] add CONFIG_VMMOUSE option Eduardo Habkost
2011-02-01 16:53 ` [Qemu-devel] [PATCH 4/4] add CONFIG_VMPORT option Eduardo Habkost
2011-02-01 18:10 ` [Qemu-devel] [PATCH 0/4] fix/add CONFIG_* options for VMWare device emulation Blue Swirl
2011-02-02 3:01 ` [Qemu-devel] " Juan Quintela
2011-02-02 5:07 ` David Ahern
2011-02-02 7:55 ` Paolo Bonzini [this message]
2011-02-02 17:16 ` Blue Swirl
2011-02-02 17:37 ` Eduardo Habkost
2011-02-02 18:30 ` 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=4D490DE2.6070806@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.