[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141127120252.27021c54.cornelia.huck@de.ibm.com>
Date: Thu, 27 Nov 2014 12:02:52 +0100
From: Cornelia Huck <cornelia.huck@...ibm.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: linux-kernel@...r.kernel.org, David Miller <davem@...emloft.net>,
rusty@....ibm.com, nab@...ux-iscsi.org, pbonzini@...hat.com,
Rusty Russell <rusty@...tcorp.com.au>,
Christian Borntraeger <borntraeger@...ibm.com>,
linux390@...ibm.com, Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Pawel Moll <pawel.moll@....com>,
Ohad Ben-Cohen <ohad@...ery.com>,
Sudeep Dutt <sudeep.dutt@...el.com>,
Ashutosh Dixit <ashutosh.dixit@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nikhil Rao <nikhil.rao@...el.com>,
Siva Yerramreddy <yshivakrishna@...il.com>,
lguest@...ts.ozlabs.org, linux-s390@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH v4 04/42] virtio: disable virtio 1.0 in transports
On Thu, 27 Nov 2014 12:54:34 +0200
"Michael S. Tsirkin" <mst@...hat.com> wrote:
> On Wed, Nov 26, 2014 at 10:09:54AM +0100, Cornelia Huck wrote:
> > The old s390 virtio transport in kvm_virtio.c is not part of virtio 1.0.
>
> It might or might not be a good idea to add code in kvm_virtio.c
> blacklisting VIRTIO_F_VERSION_1, just in case there's a buggy device
> that sets it.
> As correct devices won't set it, I don't think we need to
> worry about it too much. We can make it a patch on top later
> if we want.
>
I'd want to blacklist it, just to make sure nothing weird happens. I
don't want to spend effort on the old transport beyond that :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists