From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] qerror: Add QERR_PROPERTY_SET_AFTER_REALIZE
Date: Wed, 18 Jul 2012 11:35:55 +0100 [thread overview]
Message-ID: <CAFEAcA_pyg_ThD8FrTE4Hc_TtqSpeaouMVB=De0B-SbHP4ThNA@mail.gmail.com> (raw)
In-Reply-To: <50068DF9.4010408@suse.de>
n 18 July 2012 11:20, Andreas Färber <afaerber@suse.de> wrote:
> Am 16.07.2012 17:25, schrieb Peter Maydell:
>> Add a new QError QERR_PROPERTY_SET_AFTER_REALIZE for attempts
>> to set a QOM or qdev property after the object/device has been
>> realized. This allows a slightly more informative diagnostic
>> than the previous "permission denied" message.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> Changes since the v1 (which was sent way back in March...):
>> * rebased on master now a pile of qdev/qom changesd have landed
>> * fixed some overlong lines
>> * avoid gcc '?:' extension
>> * a couple of set_ functions in qdev-properties.c are new since v1
>> and needed their QERR_PERMISSION_DENIED checks changing
>
> This does not yet seem to take into account the discussion with libvirt
> and Anthony on what parameters to pass. The ID generalization was
> nack'ed by Anthony and a QOM path was suggested as alternative. Could
> you please look into that?
I'm afraid I'm not really sure what you're referring to here --
do you have a link to a discussion?
All I want is for errors printed to the user to be a bit more
helpful; the whole qerror infrastructure seems to make it
somewhere between difficult and impossible to do that :-(
-- PMM
next prev parent reply other threads:[~2012-07-18 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 15:25 [Qemu-devel] [PATCH v2] qerror: Add QERR_PROPERTY_SET_AFTER_REALIZE Peter Maydell
2012-07-18 10:20 ` Andreas Färber
2012-07-18 10:35 ` Peter Maydell [this message]
2012-07-18 11:19 ` Markus Armbruster
2012-07-18 11:36 ` Peter Maydell
2012-07-18 11:36 ` Peter Maydell
2012-07-18 11:59 ` Markus Armbruster
2012-07-18 13:03 ` Luiz Capitulino
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='CAFEAcA_pyg_ThD8FrTE4Hc_TtqSpeaouMVB=De0B-SbHP4ThNA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=patches@linaro.org \
--cc=pbonzini@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).