qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: P J P <ppandit@redhat.com>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] ppc: add host-serial and host-model machine attributes
Date: Fri, 15 Feb 2019 11:18:34 +1100	[thread overview]
Message-ID: <20190215001833.GA4573@umbus.fritz.box> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1902150047200.27283@xnncv>

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

On Fri, Feb 15, 2019 at 12:57:35AM +0530, P J P wrote:
> +-- On Wed, 13 Feb 2019, David Gibson wrote --+
> | > +
> | > +    object_class_property_add_str(oc, "host-serial",
> | > +        machine_get_host_serial, machine_set_host_serial,
> | > +        &error_abort);
> | > +    object_class_property_set_description(oc, "host-serial",
> | > +        "Set host's system-id to use", &error_abort);
> | > +
> | > +    object_class_property_add_str(oc, "host-model",
> | > +        machine_get_host_model, machine_set_host_model,
> | > +        &error_abort);
> | > +    object_class_property_set_description(oc, "host-model",
> | > +        "Set host's model-id to use", &error_abort);
> | 
> | You're adding properties to *all* machines, for something that's only
> | used on the PAPR machine.  That doesn't seem right.
> 
> I tried to figure out about adding these options to only spapr machine, but it 
> does not seem straight forward as above.

It really should be.  You can just put those
object_class_property_add()s into spapr_machine_class_init().

> | >      spapr_machine_4_0_class_options(mc);
> | >      compat_props_add(mc->compat_props, hw_compat_3_1, hw_compat_3_1_len);
> | > +    compat_props_add(mc->compat_props, compat, G_N_ELEMENTS(compat));
> | 
> | I'm still not convinced maintaining super-strict backwards compat at
> | the expense of security is a good tradeoff here, but since the code's
> | already written, let's run with it.
> 
> I think current patch will provide a way to help fix the security issue, we 
> can revise it further if required.

That's reasonable.

> 
> Thank you.

-- 
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 --]

      reply	other threads:[~2019-02-15  0:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 11:39 [Qemu-devel] [PATCH v2] ppc: add host-serial and host-model machine attributes P J P
2019-02-13  1:38 ` David Gibson
2019-02-14 19:27   ` P J P
2019-02-15  0:18     ` David Gibson [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=20190215001833.GA4573@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=berrange@redhat.com \
    --cc=ppandit@redhat.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).