From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>, KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Avi Kivity <avi.kivity@gmail.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>
Subject: Re: [PATCH 5/5] KVM: s390: Split out early console code.
Date: Tue, 11 Dec 2012 13:36:11 +0100 [thread overview]
Message-ID: <20121211133611.57193191@BR9GNB5Z> (raw)
In-Reply-To: <DC2767EE-52E6-4BF4-9F79-0603BBE87A77@suse.de>
On Tue, 11 Dec 2012 11:10:39 +0100
Alexander Graf <agraf@suse.de> wrote:
>
> On 10.12.2012, at 10:06, Cornelia Huck wrote:
>
> > On Sun, 9 Dec 2012 13:45:47 +0100
> > Alexander Graf <agraf@suse.de> wrote:
> >
> >>
> >> On 07.12.2012, at 13:29, Cornelia Huck wrote:
> >>
> >>> This code is transport agnostic and can be used by both the legacy
> >>> virtio code and virtio_ccw.
> >>
> >> This code should die. It's a nightmare to implement in QEMU, because it ends up being a separate char device. I'd prefer if we don't carry it over to the virtio-ccw world :).
> >
> > I don't really want to kill an interface in a patchset adding a new
> > transport. We may kill this later on, though...
>
> I fully agree :). What I was trying to say is "leave this to die in the old code and don't bother about it in the new world order". Removing support for the old kvm virtio machine is nothing for today.
Ah, OK. I'll merge the return -ENODEV into the first patch then and
drop this one.
next prev parent reply other threads:[~2012-12-11 12:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 12:29 [PATCH v3 0/5] s390: Guest support for virtio-ccw Cornelia Huck
2012-12-07 12:29 ` [PATCH 1/5] KVM: s390: Handle hosts not supporting s390-virtio Cornelia Huck
2012-12-07 12:29 ` [PATCH 2/5] s390: Move css limits from drivers/s390/cio/ to include/asm/ Cornelia Huck
2012-12-07 12:29 ` [PATCH 3/5] s390: Add a mechanism to get the subchannel id Cornelia Huck
2012-12-09 12:12 ` Alexander Graf
2012-12-10 9:03 ` Cornelia Huck
2012-12-11 10:09 ` Alexander Graf
2012-12-11 12:34 ` Cornelia Huck
2012-12-12 0:33 ` Alexander Graf
2012-12-12 16:36 ` Cornelia Huck
2012-12-07 12:29 ` [PATCH 4/5] KVM: s390: Add a channel I/O based virtio transport driver Cornelia Huck
2012-12-07 12:29 ` [PATCH 5/5] KVM: s390: Split out early console code Cornelia Huck
2012-12-09 12:45 ` Alexander Graf
2012-12-10 9:06 ` Cornelia Huck
2012-12-11 10:10 ` Alexander Graf
2012-12-11 12:36 ` Cornelia Huck [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 13:07 [PATCH 0/5] s390: Guest support for virtio-ccw Cornelia Huck
2012-10-29 13:07 ` [PATCH 5/5] KVM: s390: Split out early console code Cornelia Huck
2012-10-29 18:14 ` Alexander Graf
2012-10-30 12:59 ` Cornelia Huck
2012-10-30 13:43 ` Alexander Graf
2012-10-30 14:29 ` Cornelia Huck
2012-10-30 15:12 ` Alexander Graf
2012-10-30 15:35 ` Cornelia Huck
2012-10-30 15:42 ` Alexander Graf
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=20121211133611.57193191@BR9GNB5Z \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=avi.kivity@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=gleb@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.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).