From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
qemu-s390x@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files
Date: Wed, 25 Jul 2018 19:20:59 +0200 [thread overview]
Message-ID: <d0deae36-1183-e3ef-764e-79b4b68f207e@redhat.com> (raw)
In-Reply-To: <20180725154837.5f9c6735.cohuck@redhat.com>
On 25.07.2018 15:48, Cornelia Huck wrote:
> On Wed, 25 Jul 2018 14:20:14 +0200
> Thomas Huth <thuth@redhat.com> wrote:
>
>> For more fine-grained control over the build process, it would be good
>> to have the possibility to disable single virtio devices, too. We already
>> have CONFIG_VIRTIO_* switches in the Makefiles, but currently all
>> virtio-ccw devices are compiled in anyway. Move them to separate files
>> so we can disable them in the Makefile more easily.
>>
>> NB: I did not move virtio-blk-ccw and virtio-net-ccw to a separate file
>> yet since they are essential for the s390x-virtio machine and thus it
>> does IMHO not make much sense to disable net and blk. But if somebody
>> needs that possibility, too, I can add two more patches on top...
>
> I understand virtio-net-ccw (autogenerated network devices), but why
> virtio-blk-ccw?
Because we set mc->block_default_type = IF_VIRTIO ==> if you disable
virtio-blk, the CLI options like -hda and -cdrom would not work anymore.
> Regardless, it might make sense to split them out so that we get a
> slimmed-down virtio-ccw.c.
OK.
Thomas
next prev parent reply other threads:[~2018-07-25 17:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 12:20 [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 01/10] hw/s390x/virtio-ccw: Consolidate calls to virtio_ccw_unrealize() Thomas Huth
2018-07-26 9:15 ` Cornelia Huck
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 02/10] hw/s390x: Move virtio-ccw-serial code to a separate file Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 03/10] hw/s390x: Move virtio-ccw-balloon " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 04/10] hw/s390x: Move virtio-ccw-scsi " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 05/10] hw/s390x: Move virtio-ccw-rng " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 06/10] hw/s390x: Move virtio-ccw-9p " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 07/10] hw/s390x: Move virtio-ccw-crypto " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 08/10] hw/s390x: Move vhost-vsock-ccw " Thomas Huth
2018-08-23 14:13 ` Cornelia Huck
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 09/10] hw/s390x: Move virtio-ccw-gpu " Thomas Huth
2018-07-25 12:20 ` [Qemu-devel] [PATCH for-3.1 10/10] hw/s390x: Move virtio-ccw-input " Thomas Huth
2018-07-25 13:48 ` [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files Cornelia Huck
2018-07-25 17:20 ` Thomas Huth [this message]
2018-07-26 9:07 ` Cornelia Huck
2018-07-25 13:52 ` Christian Borntraeger
2018-07-25 16:21 ` Juan Quintela
2018-07-25 17:15 ` Thomas Huth
2018-07-25 18:07 ` [Qemu-devel] [PATCH for-3.1 11/10] hw/s390x: Move virtio-ccw-net code to a separate file Thomas Huth
2018-07-25 18:08 ` [Qemu-devel] [PATCH for-3.1 12/10] hw/s390x: Move virtio-ccw-blk " Thomas Huth
2018-08-15 11:45 ` [Qemu-devel] [PATCH for-3.1 00/10] Move virtio-ccw devices to separate files Cornelia Huck
2018-08-23 14:25 ` Cornelia Huck
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=d0deae36-1183-e3ef-764e-79b4b68f207e@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=quintela@redhat.com \
/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).