qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qdev: obey no_user
Date: Mon, 07 Jan 2013 16:48:22 -0600	[thread overview]
Message-ID: <87txqs1ufd.fsf@codemonkey.ws> (raw)
In-Reply-To: <50EB4DF4.6060308@suse.de>

Andreas Färber <afaerber@suse.de> writes:

> Am 07.01.2013 23:20, schrieb Peter Maydell:
>> On 7 January 2013 22:10, Andreas Färber <afaerber@suse.de> wrote:
>>> Am 07.01.2013 21:16, schrieb Peter Maydell:
>>>> On 7 January 2013 20:12, Anthony Liguori <aliguori@us.ibm.com> wrote:
>>>>> Peter Maydell <peter.maydell@linaro.org> writes:
>>>>>> It seems to me like arbitrarily allowing the monitor to construct
>>>>>> no-user devices isn't really the right way to attack the problem
>>>>>> of "allow complete machine construction by management tools"...
>>>>>
>>>>> There is no such thing as a 'no-user' device.  It's a silly distinction
>>>>> that has never had a consistent meaning.
>>>>
>>>> Then let's just rip that flag out completely.
>>>
>>> That's a bad idea, given that we are about to make the CPU a device.
>> 
>> We already have a pile of devices which the user can't usefully
>> use -device on...CPUs would be just another one, right?
>
> Not sure what you're arguing for here? The CPU is the worst example of a
> device I know in that it is not limited to a particular bus and messes
> with global state and threads.
>
> Also, I'm sure that there will be objects/devices that a management tool
> is not supposed to mess with either, once we start using
> object_initialize() more.
>
> If we agree that "no_user = 1" is not ideal or used inconsistently, then
> we should IMO talk about how to replace/amend it and not conclude to
> just rip it out and leave users without sensible error messages while
> praying for The Omnipotent Management Tool that AFAICS we don't have
> today...

If you want to replace 'no_user' with
'cannot_instantiate_with_device_add_yet_due_to_internal_bugs' I'm okay
with that.

I'm all for having friendly errors for users.  But no_user doesn't just
serve a 'broken' flag today.  Random devices are marked as no_user that
really shouldn't be like isa-fdc.

Regards,

Anthony Liguori

>
> Andreas
>
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-01-07 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 16:00 [Qemu-devel] [PATCH] qdev: obey no_user Christian Borntraeger
2013-01-07 14:05 ` Christian Borntraeger
2013-01-07 14:20 ` Andreas Färber
2013-01-07 15:24   ` Luiz Capitulino
2013-01-07 19:32 ` Anthony Liguori
2013-01-07 19:40   ` Peter Maydell
2013-01-07 20:12     ` Anthony Liguori
2013-01-07 20:16       ` Peter Maydell
2013-01-07 20:48         ` Anthony Liguori
2013-01-07 22:10         ` Andreas Färber
2013-01-07 22:20           ` Peter Maydell
2013-01-07 22:36             ` Andreas Färber
2013-01-07 22:48               ` Anthony Liguori [this message]
2013-01-07 20:40   ` Christian Borntraeger
2013-01-07 21:43     ` Anthony Liguori

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=87txqs1ufd.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=peter.maydell@linaro.org \
    --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).