From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: borntraeger@de.ibm.com, pmorel@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices
Date: Tue, 28 Nov 2017 15:17:38 +0100 [thread overview]
Message-ID: <6513d1c5-032e-b9d0-3dab-f2d0bd337ae2@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171128134648.21530-1-cohuck@redhat.com>
On 11/28/2017 02:46 PM, Cornelia Huck wrote:
> info qom-tree shows several devices under unattached that probably
> should go somewhere.
I think this was reported by me. See
MID: <76f95c6f-641e-2fe0-73b4-3ab24fc1a93f@linux.vnet.ibm.com>
I would not mind a Reported-by: Halil Pasic <pasic@linux.vnet.ibm.com>.
Or do you see this differently?
If these are bugs. I would prefer commit messages and titles reflecting
this fact.
Otherwise at first glance both patches seem sane.
Regards,
Halil
>
> 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(+)
>
next prev parent reply other threads:[~2017-11-28 14:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 13:46 [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices Cornelia Huck
2017-11-28 13:46 ` [Qemu-devel] [PATCH RFC 1/2] s390x/css: attach css bridge Cornelia Huck
2017-11-28 14:02 ` Christian Borntraeger
2017-12-08 11:43 ` Cornelia Huck
2017-11-28 13:46 ` [Qemu-devel] [PATCH RFC 2/2] s390x: attach autogenerated nics Cornelia Huck
2017-12-04 11:17 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2017-12-04 16:40 ` Cornelia Huck
2017-12-04 17:33 ` Halil Pasic
2017-12-04 17:51 ` Cornelia Huck
2017-11-28 14:17 ` Halil Pasic [this message]
2017-11-28 14:27 ` [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices Cornelia Huck
2017-11-28 15:21 ` Halil Pasic
2017-12-01 14:41 ` Halil Pasic
2017-12-04 9:22 ` Cornelia Huck
2017-12-04 14:47 ` Halil Pasic
2017-12-04 16:51 ` Cornelia Huck
2017-12-04 11:47 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2017-12-05 8:59 ` [Qemu-devel] " Bjoern Walk
2017-12-07 16:34 ` Cornelia Huck
2017-12-07 17:01 ` Halil Pasic
2017-12-07 17:06 ` Cornelia Huck
2017-12-07 17:15 ` Halil Pasic
2017-12-08 11:42 ` Cornelia Huck
2017-12-08 12:14 ` Halil Pasic
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=6513d1c5-032e-b9d0-3dab-f2d0bd337ae2@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).