From: Anthony Liguori <aliguori@us.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] sysbus: add no_user for devices using mmio or IRQ or GPIO
Date: Thu, 07 Mar 2013 11:17:36 -0600 [thread overview]
Message-ID: <87d2vbuo27.fsf@codemonkey.ws> (raw)
In-Reply-To: <87zjyf3zqv.fsf@blackfin.pond.sub.org>
Markus Armbruster <armbru@redhat.com> writes:
> Anthony Liguori <aliguori@us.ibm.com> writes:
>
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> Peter Maydell <peter.maydell@linaro.org> writes:
>>>>>> [and I don't think "this device
>>>>>> can be added via the monitor but not the command line"
>>>>>> counts as consistent or coherent...]
>>>>>
>>>>> no_user applies equally to -device and device_add.
>>>>
>>>> In the codebase as it stands, it applies only to -device.
>>>> I agree that we should be consistent here, which we could do
>>>> by applying Christian's patch or some variation to make device_add
>>>> honour no_user. (Or by removing no_user altogether :-))
>>>
>>> Actually, it appears to apply only to help now!
>>>
>>> git-bisect blames this one:
>>
>> Let's step back and try to figure out the problem we're trying to solve.
>>
>> What is -devices help trying to show? Devices that are valid to for a
>> user to pass? Hint: on a PC, the only thing that's valid to add are
>> devices that implement a certain bus type. In fact, it depends on the
>> bus model.
>>
>> So if you want to make -device help prettier, we should add a filter
>> that looks at the busses available and filters anything that isn't an
>> instance of the appropriate bus types.
>
> Necessary, but not sufficient; see the two examples I posted upstream.
> Both devices would pass a "appropriate bus is available" filter. Both
> devices cannot possibly work. One of them starts up fine (mayhem at
> guest runtime expected),
Note that what you've done with the first one is 100% representative of
real hardware. ISA bus conflicts are part of the nature of ISA and
why it was such an awful bus.
> the other makes qemu crash & burn immediately.
This is a modeling problem. It doesn't make sense for q35-pcihost
to be a PCIDevice. It's not a PCI device.
But even so, segv'ing is always a bug and we ought to prevent it from
seg faulting. no_user to hide a SEGV is just using a bandaid.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2013-03-07 17:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 17:32 [Qemu-devel] [PATCH] sysbus: add no_user for devices using mmio or IRQ or GPIO Paolo Bonzini
2013-03-04 17:58 ` Peter Maydell
2013-03-04 20:16 ` Paolo Bonzini
2013-03-04 23:22 ` Peter Maydell
2013-03-05 10:58 ` Paolo Bonzini
2013-03-05 11:25 ` Gerd Hoffmann
2013-03-07 8:48 ` Markus Armbruster
2013-03-07 10:00 ` Peter Maydell
2013-03-07 12:36 ` Markus Armbruster
2013-03-07 16:09 ` Anthony Liguori
2013-03-07 16:22 ` Peter Maydell
2013-03-07 17:07 ` Markus Armbruster
2013-03-07 17:17 ` Anthony Liguori [this message]
2013-03-07 17:45 ` Markus Armbruster
2013-03-07 12:45 ` Peter Crosthwaite
2013-03-07 15:41 ` Peter Maydell
2013-03-07 23:37 ` Peter Crosthwaite
2013-03-07 23:53 ` Peter Maydell
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=87d2vbuo27.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.