From: Jan Kiszka <jan.kiszka@siemens.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: qemu-devel@nongnu.org, Dmitry Baryshkov <dmitry.baryshkov@siemens.com>
Subject: [Qemu-devel] Re: [PATCH 1/2] qemu-accel: unbreak non-default accelerators
Date: Wed, 10 Sep 2008 09:21:39 +0200 [thread overview]
Message-ID: <48C77583.5070003@siemens.com> (raw)
In-Reply-To: <20080909164955.GD7490@poweredge.glommer>
Glauber Costa wrote:
> On Tue, Sep 09, 2008 at 08:37:37PM +0400, Dmitry Baryshkov wrote:
>> Make noaccel accelerator "registered" early so that
>> kqemu has a change to be enabled (it's registered
>> via __constructor__ feature, so called before main()).
> fyi: we're probably changing that. There has been a lot of mail exchange
> this days about the general acceptability of this feature, and the overall
[ That was a private discussion, I guess. ]
> feeling is that it's a negative construct. So if the problem you hit happens because
> the constructor itself, it's probably worthy to drop it altogether, and invest time
> in a new method for registering the accelerators.
Do you plan to update/rebase QEMUAccel in the near future? Or what is
the short-term roadmap of this approach?
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-09-10 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 16:37 [Qemu-devel] [PATCH 1/2] qemu-accel: unbreak non-default accelerators Dmitry Baryshkov
2008-09-09 16:37 ` [Qemu-devel] [PATCH 2/2] qemu-accel: unbreak kqemu Dmitry Baryshkov
2008-09-09 16:49 ` [Qemu-devel] Re: [PATCH 1/2] qemu-accel: unbreak non-default accelerators Glauber Costa
2008-09-10 7:21 ` Jan Kiszka [this message]
2008-09-10 13:48 ` Glauber Costa
2008-09-10 14:15 ` Jan Kiszka
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=48C77583.5070003@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dmitry.baryshkov@siemens.com \
--cc=gcosta@redhat.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).