On Tue, 23 Jun 2015 19:19:39 +0200 Cornelia Huck <cornelia.h...@de.ibm.com> wrote:
> On Tue, 23 Jun 2015 18:36:34 +0200 > Thomas Huth <th...@redhat.com> wrote: > > > On Tue, 23 Jun 2015 13:17:32 +0200 > > Cornelia Huck <cornelia.h...@de.ibm.com> wrote: > > > > > Michael, > > > > > > here's the virtio-ccw patches that Gerd had dropped due to conflicts > > > during his virtio-1 rebase. Patch 2 has been updated with my changes > > > to ensure big endian accesses (which was a separate patch before). > > > > > > There might be more patches that were in my tree but are not yet upstream, > > > but I'm still digging myself out from under the post-vacation email pile. > > > > > > I think these can still go into 2.4. > > > > Is it safe enough to enable them by default already? If I've got > > the virtio-pci code right (see the patch description at > > https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01362.html), > > it is still disabled there by default - and "modern will be turned on by > > default once all remaining spec compilance issues are addressed". > > I was about to say "yes" when I noticed that we probably want to care > about migrating dev->revision as well... I'll drop patch 4 for now and > just send patches 1-3 from this series. On a second thought, I can simply include dev->revision, as we have the incompatible ->config_vector change for this release already. I'll include a new patch for this and patch 4 as well, as we only need to care about Linux guests on ccw for now and those are fine.
