From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Krempa" <pkrempa@redhat.com>,
Richard@redhat.com, "Eduardo Habkost" <ehabkost@redhat.com>,
libvir-list@redhat.com, Claudio@redhat.com,
Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Fontana <cfontana@suse.de>, "Paolo Bonzini" <pbonzini@redhat.com>,
Markus@redhat.com, "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH for-6.0] accel: Wire accel to /machine
Date: Mon, 7 Dec 2020 17:44:19 +0000 [thread overview]
Message-ID: <20201207174419.GP3102898@redhat.com> (raw)
In-Reply-To: <20201207084621.23876-1-r.bolshakov@yadro.com>
On Mon, Dec 07, 2020 at 11:46:22AM +0300, Roman Bolshakov wrote:
> There's no generic way to query current accel and its properties via QOM
> because there's no link between an accel and current machine.
>
> The change adds the link, i.e. if HVF is enabled the following will be
> available in QOM:
>
> (qemu) qom-get /machine/accel type
> "hvf-accel"
>
> Suggested-by: Markus Armbruster <armbru@redhat.com>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com>
> ---
>
> Hi,
>
> this is a follow up patch that deprecates earlier series [1].
>
> An outstanding issue is whether management applications can rely on the
> value of /machine/accel/type and output of qom-list-types command [2][3]
> to get current and present accels?
>
> i.e. would it be ok if libvirt assumes that everything up to the first
> dash in the accel type is the name of the accel (as specified via -M
> accel=ACCEL flag) when it performs QEMU probing?
Hmm, I think it is not nice - we shouldn't have to parse the
accel type names - IMHO typenames should be considered arbitrary
opaque strings, even if they'll not be expected to change.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-12-07 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 8:46 [PATCH for-6.0] accel: Wire accel to /machine Roman Bolshakov
2020-12-07 17:38 ` Eduardo Habkost
2020-12-07 17:50 ` Peter Krempa
2020-12-08 8:13 ` Roman Bolshakov
2020-12-08 8:19 ` Peter Krempa
2020-12-08 8:11 ` Roman Bolshakov
2020-12-07 17:44 ` Daniel P. Berrangé [this message]
2020-12-08 7:40 ` Roman Bolshakov
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=20201207174419.GP3102898@redhat.com \
--to=berrange@redhat.com \
--cc=Claudio@redhat.com \
--cc=Markus@redhat.com \
--cc=Richard@redhat.com \
--cc=cfontana@suse.de \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=richard.henderson@linaro.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 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.