From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:32882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eJgDx-00083H-5v for qemu-devel@nongnu.org; Tue, 28 Nov 2017 08:47:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eJgDs-0003B4-NE for qemu-devel@nongnu.org; Tue, 28 Nov 2017 08:46:57 -0500 From: Cornelia Huck Date: Tue, 28 Nov 2017 14:46:46 +0100 Message-Id: <20171128134648.21530-1-cohuck@redhat.com> Subject: [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org Cc: borntraeger@de.ibm.com, pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com, Cornelia Huck info qom-tree shows several devices under unattached that probably should go somewhere. The css bridge should attach to the machine, as it has a similar purpose as e.g. a pci host bridge. The autogenerated network devices should be in the same bucket as any other device; I'm just not sure about the way I went about it. The zpci devices are still problematic: I don't have a good idea where they should show up. Remaining in the unattached container are the sysbus, memory regions and cpus. Cornelia Huck (2): s390x/css: attach css bridge s390x: attach autogenerated nics hw/s390x/css-bridge.c | 2 ++ hw/s390x/s390-virtio-ccw.c | 2 ++ 2 files changed, 4 insertions(+) -- 2.13.6