Hi Keir, Please pull the ia64 trees: http://xenbits.xensource.com/ext/ia64/xen-unstable.hg http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg The bulk of the changesets here are Isaku''s initial implementation of HVM domain save/restore on ia64. More patches will follow for this to add robustness and work out the kinks. This also includes Tristan''s patches to support mixed mode dt/it guests. Also included is console time stamp support, MCA fixes from the kexec changes, a couple more kexec patches, and fixes for dom0 softlockup on guest domain shutdown. Numerous other bug fixes and cleanups also included. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Hi Keir, Please pull the ia64 trees: http://xenbits.xensource.com/ext/ia64/xen-unstable.hg http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg Most of these are bug fixes and small enhancements. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Hi Keir, Please pull the ia64 trees: http://xenbits.xensource.com/ext/ia64/xen-unstable.hg http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg This includes a small series of patches from Yamahata-san that fixes optimization feature save/restore for VTi domains. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Hi, At http://wiki.xensource.com/xenwiki/VirtualFramebuffer in Stage 2 adding dynamic modes to the Xen VirtualFramebuffer is mentioned. Does not appear this was ever done. Is there a technical reason this has not been implemented or just a case of not enough time or interest? If it is technically feasible do you have any pointers or examples on how to go about implementing this feature? Thanks in advance. Pat _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
"Pat Campbell" <plc@novell.com> writes:> Hi, > > At http://wiki.xensource.com/xenwiki/VirtualFramebuffer in Stage 2 adding > dynamic modes to the Xen VirtualFramebuffer is mentioned. > > Does not appear this was ever done. Is there a technical reason this has not > been implemented or just a case of not enough time or interest? > > If it is technically feasible do you have any pointers or examples on how to > go about implementing this feature? > > Thanks in advance. > > PatThe protocol between frontend and backend is easy enough to extend in a backward compatible manner, so negotiating resolution changes shouldn''t be hard. Guard the extension with suitable flags in xenstore (feature-FOO to offer FOO, request-FOO to take it, see source code for examples). The frontend exposes the framebuffer to the backend in a rather archaic manner. The size of the page directory artificially limits the framebuffer to 4M. Fixable, but I''d rather see this converted to grant tables (assuming they can support large grants now).>From a usability point of view, you should be able to resize the pvfbwindow like any other window. But then the backend initiates the resize. I don''t know whether software running in the frontend is fine with framebuffers initiating resolutions changes. Please let me know if you tackle this feature. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel