From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
nfont@linux.vnet.ibm.com, mwb@linux.vnet.ibm.com,
imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] spapr: Support ibm, dynamic-memory-v2 property
Date: Wed, 18 Apr 2018 13:33:44 +1000 [thread overview]
Message-ID: <20180418033344.GF2317@umbus.fritz.box> (raw)
In-Reply-To: <20180417090909.GB3942@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On Tue, Apr 17, 2018 at 02:39:09PM +0530, Bharata B Rao wrote:
> On Tue, Apr 17, 2018 at 11:14:27AM +1000, David Gibson wrote:
> > > static void spapr_machine_2_12_class_options(MachineClass *mc)
> > > diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> > > index d60b7c6d7a..5e044c44af 100644
> > > --- a/include/hw/ppc/spapr.h
> > > +++ b/include/hw/ppc/spapr.h
> > > @@ -149,6 +149,7 @@ struct sPAPRMachineState {
> > > sPAPROptionVector *ov5; /* QEMU-supported option vectors */
> > > sPAPROptionVector *ov5_cas; /* negotiated (via CAS) option vectors */
> > > uint32_t max_compat_pvr;
> > > + bool use_ibm_dynamic_memory_v2;
> >
> > TBH, I'm not really sure we even need to adjust this by machine type.
>
> There are other similar features controlled by ov5 bits that
> are also determined by machine type version:
>
> Memory hotplug support -- sPAPRMachineClass.dr_lmb_enabled
> Dedicated HP event support -- sPAPRMachineState.use_hotplug_event_source
As for user settability the issue isn't that it's set by ov5, but what
the effect of the feature is. Those other features alter runtime
hypervisor behaviour and that behaviour has to remain the same across
a migration. Therefore we have to keep the behaviour consistent for
old machine types.
This feature affects only boot time behaviour. It has a similar
effect to what a firmware update might, on real hardware. Furthermore
the way CAS and the device tree work, this is vanishingly unlikely to
break existing guests.
> Are you saying that presence of ibm,dynamic-memory-v2 probably shouldn't
> be dependent on machine type ?
Yes, I am.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-18 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 8:55 [Qemu-devel] [PATCH v3] spapr: Support ibm, dynamic-memory-v2 property Bharata B Rao
2018-04-17 1:14 ` David Gibson
2018-04-17 9:09 ` Bharata B Rao
2018-04-18 3:33 ` David Gibson [this message]
2018-05-03 12:34 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-05-04 0:15 ` David Gibson
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=20180418033344.GF2317@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=imammedo@redhat.com \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).