Re: [Qemu-devel] q35 and sysbus devices

2017-03-27 Thread Eduardo Habkost
On Fri, Mar 24, 2017 at 05:58:43PM +0100, Markus Armbruster wrote: > Eduardo Habkost writes: > > > On Fri, Mar 24, 2017 at 01:49:16PM +0300, Marcel Apfelbaum wrote: > >> On 03/22/2017 10:46 PM, Laszlo Ersek wrote: > >> > On 03/22/17 21:31, Eduardo Habkost wrote: > >> > > Hi, > >> > > > >> > > I

Re: [Qemu-devel] q35 and sysbus devices

2017-03-27 Thread Peter Maydell
On 27 March 2017 at 09:44, Cornelia Huck wrote: > ISTR some surprises that reset (or some other) callbacks were not > called as expected if there wasn't a sysbus device among the ancestors. > Don't know if that's still true. Yes -- if you're a sysbus device then your reset method is called. If yo

Re: [Qemu-devel] q35 and sysbus devices

2017-03-27 Thread Cornelia Huck
On Fri, 24 Mar 2017 16:23:18 -0300 Eduardo Habkost wrote: > On Fri, Mar 24, 2017 at 05:08:56PM +, Peter Maydell wrote: > > On 24 March 2017 at 16:58, Markus Armbruster wrote: > > > "Sysbus" isn't a bus. In qdev's original design, every device had to > > > plug into a bus, period. The ones

Re: [Qemu-devel] q35 and sysbus devices

2017-03-27 Thread Thomas Huth
On 24.03.2017 18:59, Markus Armbruster wrote: > Peter Maydell writes: > >> On 24 March 2017 at 16:58, Markus Armbruster wrote: >>> "Sysbus" isn't a bus. In qdev's original design, every device had to >>> plug into a bus, period. The ones that really didn't were made to plug >>> into "sysbus".

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Eduardo Habkost
On Fri, Mar 24, 2017 at 05:08:56PM +, Peter Maydell wrote: > On 24 March 2017 at 16:58, Markus Armbruster wrote: > > "Sysbus" isn't a bus. In qdev's original design, every device had to > > plug into a bus, period. The ones that really didn't were made to plug > > into "sysbus". > > > > Pret

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Eduardo Habkost
On Fri, Mar 24, 2017 at 02:13:48PM +, Peter Maydell wrote: > On 24 March 2017 at 13:48, Eduardo Habkost wrote: > > The problem with today's mechanism is that we have no way to make > > a machine accept one type of sysbus device without making it > > start accepting every other sysbus devices.

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Peter Maydell
On 24 March 2017 at 17:59, Markus Armbruster wrote: > Peter Maydell writes: >> This isn't really true. Sysbus devices support having MMIO regions >> and IRQ lines and GPIO lines. If you need those you're a >> sysbus device; otherwise you can probably just be a plain old Device. > > Well, "device

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Markus Armbruster
Peter Maydell writes: > On 24 March 2017 at 16:58, Markus Armbruster wrote: >> "Sysbus" isn't a bus. In qdev's original design, every device had to >> plug into a bus, period. The ones that really didn't were made to plug >> into "sysbus". >> >> Pretty much the only thing "sysbus" devices had

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Peter Maydell
On 24 March 2017 at 16:58, Markus Armbruster wrote: > "Sysbus" isn't a bus. In qdev's original design, every device had to > plug into a bus, period. The ones that really didn't were made to plug > into "sysbus". > > Pretty much the only thing "sysbus" devices had in common was that they > could

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Markus Armbruster
Eduardo Habkost writes: > On Fri, Mar 24, 2017 at 01:49:16PM +0300, Marcel Apfelbaum wrote: >> On 03/22/2017 10:46 PM, Laszlo Ersek wrote: >> > On 03/22/17 21:31, Eduardo Habkost wrote: >> > > Hi, >> > > >> > > I am investigating the current status of has_dynamic_sysbus and >> > > sysbus device

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Peter Maydell
On 24 March 2017 at 13:48, Eduardo Habkost wrote: > The problem with today's mechanism is that we have no way to make > a machine accept one type of sysbus device without making it > start accepting every other sysbus devices. If we thought all > !cannot_instantiate_with_device_add_yet sysbus devi

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Eduardo Habkost
On Fri, Mar 24, 2017 at 01:49:16PM +0300, Marcel Apfelbaum wrote: > On 03/22/2017 10:46 PM, Laszlo Ersek wrote: > > On 03/22/17 21:31, Eduardo Habkost wrote: > > > Hi, > > > > > > I am investigating the current status of has_dynamic_sysbus and > > > sysbus device support on each of QEMU's machine

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Thomas Huth
On 22.03.2017 21:31, Eduardo Habkost wrote: > Hi, > > I am investigating the current status of has_dynamic_sysbus and > sysbus device support on each of QEMU's machine types. The good > news is that almost all has_dynamic_sysbus=1 machines have their > own internal (often short) whitelist of suppo

Re: [Qemu-devel] q35 and sysbus devices

2017-03-24 Thread Marcel Apfelbaum
On 03/22/2017 10:46 PM, Laszlo Ersek wrote: On 03/22/17 21:31, Eduardo Habkost wrote: Hi, I am investigating the current status of has_dynamic_sysbus and sysbus device support on each of QEMU's machine types. The good news is that almost all has_dynamic_sysbus=1 machines have their own internal

Re: [Qemu-devel] q35 and sysbus devices

2017-03-22 Thread Laszlo Ersek
On 03/22/17 21:31, Eduardo Habkost wrote: > Hi, > > I am investigating the current status of has_dynamic_sysbus and > sysbus device support on each of QEMU's machine types. The good > news is that almost all has_dynamic_sysbus=1 machines have their > own internal (often short) whitelist of support

[Qemu-devel] q35 and sysbus devices

2017-03-22 Thread Eduardo Habkost
Hi, I am investigating the current status of has_dynamic_sysbus and sysbus device support on each of QEMU's machine types. The good news is that almost all has_dynamic_sysbus=1 machines have their own internal (often short) whitelist of supported sysbus device types, and automatically reject unsup