On Mon, Sep 17, 2012 at 01:51:03PM +0200, Robin Axelsson wrote: > Congratulations, it's always good to see the development moving forward! > > There is one thing I wonder though when it comes to PCI passthrough: > > Can Xen reset hardware through the d3d0 in the ACPI interface and/or > through a 'bus reset' or a 'link reset'? Or can it reset hardware > that is marked for passthrough only through FLR? It does it using whatever Linux does. Which means FLR, then for good measure also D3->D0. > > For details see e.g. > http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf > > Regards > > Robin. > > > On 2012-09-17 13:38, Pasi Kärkkäinen wrote: > >----- Forwarded message from Keir Fraser<keir@xxxxxxx> ----- > > > >From: Keir Fraser<keir@xxxxxxx> > >To: xen-devel@xxxxxxxxxxxxx > >Date: Mon, 17 Sep 2012 12:34:00 +0100 > >Subject: [Xen-devel] [ANNOUNCE] Xen 4.2 released! > > > >The Xen team is pleased to announce the release of Xen 4.2. > > > >The result of *18 months* of development, new features include: > > * Paging/sharing improvements for high-density VM environments (eg. VDI) > > * Enhancements to PV-HVM guest performance > > * Improved memaccess (guest introspection) support > > * EFI boot support, replacing the legacy BIOS boot environment > > * Improved RAS support > > * XL as the default toolstack; XEND officially deprecated > > * Upstream QEMU support, with its up-to-date feature list > > > >Detailed release notes, including a more extensive feature list: > > http://wiki.xen.org/wiki/Xen_4.2_Release_Notes > > > >To download tarballs: > > http://xen.org/download/index_4.2.0.html > >Or the Mercurial source repository (tag 'RELEASE-4.2.0'): > > http://xenbits.xen.org/hg/staging/xen-4.2-testing.hg > > > >And the announcement on the Xen blog: > > http://blog.xen.org/index.php/2012/09/17/xen-4-2-0-released/ > > > >Thanks to the many people who have contributed to this release! > > > > Regards, > > The Xen Team > > > > > > > >_______________________________________________ > >Xen-devel mailing list > >Xen-devel@xxxxxxxxxxxxx > >http://lists.xen.org/xen-devel > > > >----- End forwarded message ----- > >-- > >xen mailing list > >xen@xxxxxxxxxxxxxxxxxxxxxxx > >https://admin.fedoraproject.org/mailman/listinfo/xen > > > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
