qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v2] qom: Document qom/device-list-properties implementation specific
Date: Tue, 15 May 2018 14:31:32 +0200	[thread overview]
Message-ID: <3fe400fe-5403-e414-1ce7-e49ac1e0ff2a@redhat.com> (raw)
In-Reply-To: <87h8n96s2e.fsf@dusky.pond.sub.org>

On 15/05/2018 14:07, Markus Armbruster wrote:
> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
> 
>> The recently introduced qom-list-properties QMP command raised
>> a question what properties it (and its cousin - device-list-properties)
>> can possibly print - only those defined by DeviceClass::props
>> or dynamically created in TypeInfo::instance_init() so properties created
>> elsewhere won't show up and this behaviour might confuse the user.
>> For example, PIIX4 does that from piix4_pm_realize():
>>
>> hw/acpi/piix4.c|477| object_property_add_uint8_ptr(OBJECT(s),
>> ACPI_PM_PROP_ACPI_ENABLE_CMD,
> 
> I'd like to tweak this to
> 
>   For example, PIIX4 does that from piix4_pm_realize() via
>   piix4_pm_add_propeties():
> 
>       object_property_add_uint8_ptr(OBJECT(s), ACPI_PM_PROP_ACPI_ENABLE_CMD,
>                                     &acpi_enable_cmd, NULL);
> 
> if you don't mind.
> 
>> This adds a note to the command descriptions about the limitation.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> 
> Thanks!
> 
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> 

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

      reply	other threads:[~2018-05-15 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  7:38 [Qemu-devel] [PATCH qemu v2] qom: Document qom/device-list-properties implementation specific Alexey Kardashevskiy
2018-05-15 12:07 ` Markus Armbruster
2018-05-15 12:31   ` Paolo Bonzini [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=3fe400fe-5403-e414-1ce7-e49ac1e0ff2a@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@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).