* [Qemu-devel] virtio 1.0 state? @ 2015-05-22 13:56 Gerd Hoffmann 2015-05-26 9:10 ` Cornelia Huck 0 siblings, 1 reply; 6+ messages in thread From: Gerd Hoffmann @ 2015-05-22 13:56 UTC (permalink / raw) To: qemu-devel; +Cc: Michael S. Tsirkin Hi, Where we are in terms of virtio 1.0 support in qemu? There hasn't been much activity in mst's virtio-1.0 branch recently, at least not in the public version of it. And it doesn't rebase easily to latest master any more ;( What are the blocking issues? Anything I can do to speed up things? Any chance we can get the core changes merged (64bit features for example), even if virtio 1.0 support for virtio-pci is not ready yet? cheers, Gerd ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] virtio 1.0 state? 2015-05-22 13:56 [Qemu-devel] virtio 1.0 state? Gerd Hoffmann @ 2015-05-26 9:10 ` Cornelia Huck 2015-05-27 14:47 ` Gerd Hoffmann 2015-05-28 10:29 ` Gerd Hoffmann 0 siblings, 2 replies; 6+ messages in thread From: Cornelia Huck @ 2015-05-26 9:10 UTC (permalink / raw) To: Gerd Hoffmann; +Cc: qemu-devel, Michael S. Tsirkin On Fri, 22 May 2015 15:56:13 +0200 Gerd Hoffmann <kraxel@redhat.com> wrote: > Hi, > > Where we are in terms of virtio 1.0 support in qemu? > > There hasn't been much activity in mst's virtio-1.0 branch recently, at > least not in the public version of it. And it doesn't rebase easily to > latest master any more ;( FWIW, an untested branch with the virtio-1.0 patches + some of my virtio-1.0 stuff on top rebased against current master can be found here: git://github.com/cohuck/qemu virtio-1 > > What are the blocking issues? Anything I can do to speed up things? > Any chance we can get the core changes merged (64bit features for > example), even if virtio 1.0 support for virtio-pci is not ready yet? The main issues currently are feature bit handling (legacy vs. transitional vs. modern) and migration. A prereq for fixing the first is moving host feature bits out of the transport, for which I have a patch floating around. The rest needs more thought before we can proceed, I fear. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] virtio 1.0 state? 2015-05-26 9:10 ` Cornelia Huck @ 2015-05-27 14:47 ` Gerd Hoffmann 2015-05-28 10:29 ` Gerd Hoffmann 1 sibling, 0 replies; 6+ messages in thread From: Gerd Hoffmann @ 2015-05-27 14:47 UTC (permalink / raw) To: Cornelia Huck; +Cc: qemu-devel, Michael S. Tsirkin On Di, 2015-05-26 at 11:10 +0200, Cornelia Huck wrote: > On Fri, 22 May 2015 15:56:13 +0200 > Gerd Hoffmann <kraxel@redhat.com> wrote: > > > Hi, > > > > Where we are in terms of virtio 1.0 support in qemu? > > > > There hasn't been much activity in mst's virtio-1.0 branch recently, at > > least not in the public version of it. And it doesn't rebase easily to > > latest master any more ;( > > FWIW, an untested branch with the virtio-1.0 patches + some of my > virtio-1.0 stuff on top rebased against current master can be found > here: > > git://github.com/cohuck/qemu virtio-1 Thanks. > > > > What are the blocking issues? Anything I can do to speed up things? > > Any chance we can get the core changes merged (64bit features for > > example), even if virtio 1.0 support for virtio-pci is not ready yet? > > The main issues currently are feature bit handling (legacy vs. > transitional vs. modern) and migration. A prereq for fixing the first > is moving host feature bits out of the transport, for which I have a > patch floating around. The rest needs more thought before we can > proceed, I fear. So, with the 2.4 schedule just announced it doesn't sound like very realistic that we'll have virtio 1.0 support in qemu 2.4. That kind-of ruins my plans to have virtio-input and virtio-gpu as non-transitional devices in qemu 2.4 :( cheers, Gerd ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] virtio 1.0 state? 2015-05-26 9:10 ` Cornelia Huck 2015-05-27 14:47 ` Gerd Hoffmann @ 2015-05-28 10:29 ` Gerd Hoffmann 2015-05-28 11:06 ` Cornelia Huck 1 sibling, 1 reply; 6+ messages in thread From: Gerd Hoffmann @ 2015-05-28 10:29 UTC (permalink / raw) To: Cornelia Huck; +Cc: qemu-devel, Michael S. Tsirkin On Di, 2015-05-26 at 11:10 +0200, Cornelia Huck wrote: > On Fri, 22 May 2015 15:56:13 +0200 > Gerd Hoffmann <kraxel@redhat.com> wrote: > > > Hi, > > > > Where we are in terms of virtio 1.0 support in qemu? > > > > There hasn't been much activity in mst's virtio-1.0 branch recently, at > > least not in the public version of it. And it doesn't rebase easily to > > latest master any more ;( > > FWIW, an untested branch with the virtio-1.0 patches + some of my > virtio-1.0 stuff on top rebased against current master can be found > here: > > git://github.com/cohuck/qemu virtio-1 > > > > > What are the blocking issues? Anything I can do to speed up things? > > Any chance we can get the core changes merged (64bit features for > > example), even if virtio 1.0 support for virtio-pci is not ready yet? > > The main issues currently are feature bit handling (legacy vs. > transitional vs. modern) and migration. A prereq for fixing the first > is moving host feature bits out of the transport, for which I have a > patch floating around. Have a pointer to that patch? > The rest needs more thought before we can > proceed, I fear. Care to explain what the issues are in detail (mailing list pointers are fine) and where I could possibly help? I'm following virtio discussions very briefly only, so I'm not fully up-to-date ... I havn't really looked into any transport but pci, so I suspect /me helping with migration would be more effective than looking into the feature bit issues, especially as you started working on that already ... cheers, Gerd ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] virtio 1.0 state? 2015-05-28 10:29 ` Gerd Hoffmann @ 2015-05-28 11:06 ` Cornelia Huck 2015-05-28 12:11 ` Michael S. Tsirkin 0 siblings, 1 reply; 6+ messages in thread From: Cornelia Huck @ 2015-05-28 11:06 UTC (permalink / raw) To: Gerd Hoffmann; +Cc: qemu-devel, Michael S. Tsirkin On Thu, 28 May 2015 12:29:17 +0200 Gerd Hoffmann <kraxel@redhat.com> wrote: > On Di, 2015-05-26 at 11:10 +0200, Cornelia Huck wrote: > > On Fri, 22 May 2015 15:56:13 +0200 > > Gerd Hoffmann <kraxel@redhat.com> wrote: > > > > > Hi, > > > > > > Where we are in terms of virtio 1.0 support in qemu? > > > > > > There hasn't been much activity in mst's virtio-1.0 branch recently, at > > > least not in the public version of it. And it doesn't rebase easily to > > > latest master any more ;( > > > > FWIW, an untested branch with the virtio-1.0 patches + some of my > > virtio-1.0 stuff on top rebased against current master can be found > > here: > > > > git://github.com/cohuck/qemu virtio-1 > > > > > > > > What are the blocking issues? Anything I can do to speed up things? > > > Any chance we can get the core changes merged (64bit features for > > > example), even if virtio 1.0 support for virtio-pci is not ready yet? > > > > The main issues currently are feature bit handling (legacy vs. > > transitional vs. modern) and migration. A prereq for fixing the first > > is moving host feature bits out of the transport, for which I have a > > patch floating around. > > Have a pointer to that patch? See https://marc.info/?l=qemu-devel&m=143265090821145&w=2. > > > The rest needs more thought before we can > > proceed, I fear. > > Care to explain what the issues are in detail (mailing list pointers are > fine) and where I could possibly help? I'm following virtio discussions > very briefly only, so I'm not fully up-to-date ... See e.g. https://marc.info/?l=qemu-devel&m=143144377121085&w=2 and follow-on. The virtio-1 branch has some "XXX: migration|virtio-1" comments as well. > > I havn't really looked into any transport but pci, so I suspect /me > helping with migration would be more effective than looking into the > feature bit issues, especially as you started working on that > already ... Some of the migration issues are intertwined with the feature bit changes, but IIRC there was more. I don't know if there are pci-specific issues as well, as I mostly look at ccw. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] virtio 1.0 state? 2015-05-28 11:06 ` Cornelia Huck @ 2015-05-28 12:11 ` Michael S. Tsirkin 0 siblings, 0 replies; 6+ messages in thread From: Michael S. Tsirkin @ 2015-05-28 12:11 UTC (permalink / raw) To: Cornelia Huck; +Cc: Gerd Hoffmann, qemu-devel On Thu, May 28, 2015 at 01:06:14PM +0200, Cornelia Huck wrote: > On Thu, 28 May 2015 12:29:17 +0200 > Gerd Hoffmann <kraxel@redhat.com> wrote: > > > On Di, 2015-05-26 at 11:10 +0200, Cornelia Huck wrote: > > > On Fri, 22 May 2015 15:56:13 +0200 > > > Gerd Hoffmann <kraxel@redhat.com> wrote: > > > > > > > Hi, > > > > > > > > Where we are in terms of virtio 1.0 support in qemu? > > > > > > > > There hasn't been much activity in mst's virtio-1.0 branch recently, at > > > > least not in the public version of it. And it doesn't rebase easily to > > > > latest master any more ;( > > > > > > FWIW, an untested branch with the virtio-1.0 patches + some of my > > > virtio-1.0 stuff on top rebased against current master can be found > > > here: > > > > > > git://github.com/cohuck/qemu virtio-1 > > > > > > > > > > > What are the blocking issues? Anything I can do to speed up things? > > > > Any chance we can get the core changes merged (64bit features for > > > > example), even if virtio 1.0 support for virtio-pci is not ready yet? > > > > > > The main issues currently are feature bit handling (legacy vs. > > > transitional vs. modern) and migration. A prereq for fixing the first > > > is moving host feature bits out of the transport, for which I have a > > > patch floating around. > > > > Have a pointer to that patch? > > See https://marc.info/?l=qemu-devel&m=143265090821145&w=2. > > > > > > The rest needs more thought before we can > > > proceed, I fear. > > > > Care to explain what the issues are in detail (mailing list pointers are > > fine) and where I could possibly help? I'm following virtio discussions > > very briefly only, so I'm not fully up-to-date ... > > See e.g. https://marc.info/?l=qemu-devel&m=143144377121085&w=2 and > follow-on. The virtio-1 branch has some "XXX: migration|virtio-1" > comments as well. > > > > > I havn't really looked into any transport but pci, so I suspect /me > > helping with migration would be more effective than looking into the > > feature bit issues, especially as you started working on that > > already ... > > Some of the migration issues are intertwined with the feature bit > changes, but IIRC there was more. > > I don't know if there are pci-specific issues as well, as I mostly look > at ccw. I think the biggest issue for pci is the inter-play between DRIVER_OK and pci bus master. -- MST ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-05-28 12:11 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-05-22 13:56 [Qemu-devel] virtio 1.0 state? Gerd Hoffmann 2015-05-26 9:10 ` Cornelia Huck 2015-05-27 14:47 ` Gerd Hoffmann 2015-05-28 10:29 ` Gerd Hoffmann 2015-05-28 11:06 ` Cornelia Huck 2015-05-28 12:11 ` Michael S. Tsirkin
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).