From: Igor Mammedov <imammedo@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Greg Kurz" <groug@kaod.org>,
qemu-devel@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
"Richard Henderson" <rth@twiddle.net>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v2] accel: forbid early use of kvm_enabled() and friends
Date: Fri, 29 Jun 2018 17:18:21 +0200 [thread overview]
Message-ID: <20180629171821.5e379a31@redhat.com> (raw)
In-Reply-To: <20180629111405.GG27016@redhat.com>
On Fri, 29 Jun 2018 12:14:05 +0100
Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Fri, Jun 29, 2018 at 01:08:38PM +0200, Paolo Bonzini wrote:
> > On 29/06/2018 13:07, Greg Kurz wrote:
> > >>>> Also asserting current_machine != NULL is not necessary, since you're
> > >>>> immediately dereferencing it.
> > >>> Is there a practical way to simply initialize the accelerators earlier
> > >>> in startup sequence, so we just remove or at least reduce, the liklihood
> > >>> of accessing it too early ?
> > >> We can try, though not for 3.0 of course.
> > >>
> > > FWIW, the motivation for this patch was kvm_enabled() being called under
> > > the class_init function of the machine TypeInfo. This happens way earlier
> > > than accelerator init. Not sure this is doable, but I can have a look.
> > >
> >
> > Probably not, that's way too early indeed.
>
> Yeah, doing anything non-trivial in class_init is just asking for trouble,
> as conceivably nothing is initialized at that point.
isn't class_init called lazily? (so it might actually work as far as type
isn't touched before kvm is initialized)
>
> Regards,
> Daniel
next prev parent reply other threads:[~2018-06-29 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 10:29 [Qemu-devel] [PATCH v2] accel: forbid early use of kvm_enabled() and friends Greg Kurz
2018-06-29 10:35 ` Paolo Bonzini
2018-06-29 10:39 ` Daniel P. Berrangé
2018-06-29 10:40 ` Paolo Bonzini
2018-06-29 11:07 ` Greg Kurz
2018-06-29 11:08 ` Paolo Bonzini
2018-06-29 11:14 ` Daniel P. Berrangé
2018-06-29 11:42 ` Cédric Le Goater
2018-06-29 11:47 ` Paolo Bonzini
2018-06-29 20:09 ` Eduardo Habkost
2018-06-29 15:18 ` Igor Mammedov [this message]
2018-06-29 15:19 ` Daniel P. Berrangé
2018-06-29 20:16 ` Eduardo Habkost
2018-06-29 20:34 ` Eduardo Habkost
2018-07-02 13:44 ` Greg Kurz
2018-06-29 20:03 ` Eduardo Habkost
2018-06-29 10:48 ` Greg Kurz
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=20180629171821.5e379a31@redhat.com \
--to=imammedo@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).