qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Daniil Tatianin" <d-tatianin@yandex-team.ru>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	afaerber@suse.de, ale@rev.ng, alistair.francis@wdc.com,
	"Anton Johansson" <anjo@rev.ng>,
	bbauman@redhat.com, bcain@quicinc.com,
	"Chao Peng" <chao.p.peng@linux.intel.com>,
	cjia@nvidia.com, clg@kaod.org, cw@f00f.org,
	"Damien Hedde" <dhedde@kalrayinc.com>,
	eblake@redhat.com, edgar.iglesias@gmail.com, eduardo@habkost.net,
	"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
	eric.auger@redhat.com, felipe@nutanix.com, iggy@theiggy.com,
	imp@bsdimp.com, jan.kiszka@web.de, jgg@nvidia.com,
	jidong.xiao@gmail.com, jim.shu@sifive.com,
	jjherne@linux.vnet.ibm.com,
	"Joao Martins" <joao.m.martins@oracle.com>,
	konrad.wilk@oracle.com, "Luc Michel" <luc@lmichel.fr>,
	mburton@qti.qualcomm.com, mdean@redhat.com,
	mimu@linux.vnet.ibm.com, paul.walmsley@sifive.com,
	pbonzini@redhat.com,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Shameerali Kolothum Thodi"
	<shameerali.kolothum.thodi@huawei.com>,
	shentey@gmail.com, stefanha@gmail.com, wei.w.wang@intel.com,
	z.huo@139.com, "LIU Zhiwei" <zhiwei_liu@linux.alibaba.com>,
	zwu.kernel@gmail.com, eblot@rivosinc.com, max.chou@sifive.com
Subject: Re: QEMU Community Call Agenda Items (April 30th, 2024)
Date: Tue, 30 Apr 2024 11:01:46 +0100	[thread overview]
Message-ID: <ZjDBihIw0-w2YXtD@redhat.com> (raw)
In-Reply-To: <CAFEAcA9P+axwCS+aaA1K2rVzBsNquRG0-pNTncZemaOsXi=GyA@mail.gmail.com>

On Tue, Apr 30, 2024 at 10:44:20AM +0100, Peter Maydell wrote:
> On Tue, 30 Apr 2024 at 08:36, Markus Armbruster <armbru@redhat.com> wrote:
> >
> > Daniel P. Berrangé <berrange@redhat.com> writes:
> > >  * /machine to get the rtc-time property value
> >
> > This is an alias to the RTC device's "rtc-time" property.  Only some
> > machines define it.  Useful because the actual property depends on
> > machine type and configuration.  For q35, it's
> > /machine/unattached/device[N]/rtc/date, where N can vary.
> >
> > If we moved the southbridge out of the /machine/unattached dump, we'd
> > have something like /machine/q35/ich9-lpc/rtc/date.  Stable, but you
> > have to know the machine type to find it.
> 
> Do we really want to call that stable, though? If we ever
> wanted to refactor the devices internally it might change.
> 
> My gut feeling is that exposing something we want to
> be stable as a specific "this is obviously an externally
> exposed identifier" (e.g. in the way we do by having an
> rtc-time property alias on the machine object) is more
> likely to be reliable than trusting that a QOM path all
> the way down to a specific device is never going to be
> rearranged.

Yes, the ideal would be that anything libvirt needs apriori knowledge
of should be accessible via an 'id' value assigned by libvirt. QOM
paths should only be used by libvirt if they're obtained dynamically
from a prior QMP query, not hardcoded in libvirt source. That would
avoid the QOM tree paths becoming API/ABI. The challenge is that it
is hard to predict what we might need to access, that does not yet
have an 'id' alias assigned, which is how we ended up using QOM
paths for a few things, where 99% of the timee we use 'id' aliases.


With 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 :|



      reply	other threads:[~2024-04-30 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28 22:25 QEMU Community Call Agenda Items (April 30th, 2024) Philippe Mathieu-Daudé
2024-04-29 15:06 ` Philippe Mathieu-Daudé
2024-04-29 15:55   ` Daniel P. Berrangé
2024-04-30  7:36     ` Markus Armbruster
2024-04-30  9:44       ` Peter Maydell
2024-04-30 10:01         ` Daniel P. Berrangé [this message]

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=ZjDBihIw0-w2YXtD@redhat.com \
    --to=berrange@redhat.com \
    --cc=afaerber@suse.de \
    --cc=ale@rev.ng \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=anjo@rev.ng \
    --cc=armbru@redhat.com \
    --cc=bbauman@redhat.com \
    --cc=bcain@quicinc.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cjia@nvidia.com \
    --cc=clg@kaod.org \
    --cc=cw@f00f.org \
    --cc=d-tatianin@yandex-team.ru \
    --cc=dhedde@kalrayinc.com \
    --cc=eblake@redhat.com \
    --cc=eblot@rivosinc.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=eduardo@habkost.net \
    --cc=elena.ufimtseva@oracle.com \
    --cc=eric.auger@redhat.com \
    --cc=felipe@nutanix.com \
    --cc=iggy@theiggy.com \
    --cc=imp@bsdimp.com \
    --cc=jan.kiszka@web.de \
    --cc=jgg@nvidia.com \
    --cc=jidong.xiao@gmail.com \
    --cc=jim.shu@sifive.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=joao.m.martins@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=luc@lmichel.fr \
    --cc=max.chou@sifive.com \
    --cc=mburton@qti.qualcomm.com \
    --cc=mdean@redhat.com \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shentey@gmail.com \
    --cc=stefanha@gmail.com \
    --cc=wei.w.wang@intel.com \
    --cc=z.huo@139.com \
    --cc=zhiwei_liu@linux.alibaba.com \
    --cc=zwu.kernel@gmail.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 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).