[Qemu-devel] Re: [PATCH 1/2] qemu-accel: unbreak non-default accelerators

[Glauber Costa]

On Wed, Sep 10, 2008 at 09:21:39AM +0200, Jan Kiszka wrote:
> 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. ]

No. That was on list, triggered by Gerd. But right now I can't remember how it 
started.

> 
> > 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?
I plan to update it as soon as I finish the memory rework I'm doing, with a 
somewhat
broad definition of "finish" (they don't need to be accepted, just be in a more 
definitive
shape). I expect it to happen somewhere next week.