Is there a plan to make the front-end frame buffer drivers be hostable on other legacy operating systems as we have done with other front-end drivers. Thanks, K. Y _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
The framebuffer device exported by qemu-dm seems to do the job perfectly well for HVM guests. -- Keir On 24/7/07 16:38, "Ky Srinivasan" <ksrinivasan@novell.com> wrote:> Is there a plan to make the front-end frame buffer drivers be hostable on > other legacy operating systems as we have done with other front-end drivers. > > Thanks, > > K. Y > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> On Tue, Jul 24, 2007 at 11:42 AM, in message<C2CBDC86.12F42%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote:> The framebuffer device exported by qemu- dm seems to do the job perfectly > well for HVM guests.True. However, I was looking at supporting fbfront for a para-virtualized sles9 kernel. K. Y> > -- Keir > > On 24/7/07 16:38, "Ky Srinivasan" <ksrinivasan@novell.com> wrote: > >> Is there a plan to make the front- end frame buffer drivers be hostable on >> other legacy operating systems as we have done with other front- end drivers. >> >> Thanks, >> >> K. Y >> >> >> >> _______________________________________________ >> Xen- devel mailing list >> Xen- devel@lists.xensource.com >> http://lists.xensource.com/xen- devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2007-07-24 at 16:42 +0100, Keir Fraser wrote:> The framebuffer device exported by qemu-dm seems to do the job perfectly > well for HVM guests.For PV guests the backport is hampered by zap_page_range() not being exported on any released kernels and being too big and complex for a sane compat layer. Someone from RH suggested ages ago that fbfront could be changed to use unmap_mapping_range() instead but I haven''t heard anything more since. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell <Ian.Campbell@XenSource.com> writes:> On Tue, 2007-07-24 at 16:42 +0100, Keir Fraser wrote: >> The framebuffer device exported by qemu-dm seems to do the job perfectly >> well for HVM guests. > > For PV guests the backport is hampered by zap_page_range() not being > exported on any released kernels and being too big and complex for a > sane compat layer. > > Someone from RH suggested ages ago that fbfront could be changed to use > unmap_mapping_range() instead but I haven''t heard anything more since.Yes. But it''s a hairy job, and nobody has gotten around to it so far. Quoting from the archive: We''d like to replace zap_page_range() with unmap_mapping_range(), for several good reasons: * it is already fully exported, * it deals with locking automatically via the address_space i_mmap_lock spinlock, * it automatically iterates over all the vmas on the address_space without us having to loop over them ourselves. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2007-07-24 at 09:53 -0600, Ky Srinivasan wrote:> > >>> On Tue, Jul 24, 2007 at 11:42 AM, in message > <C2CBDC86.12F42%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote: > > The framebuffer device exported by qemu- dm seems to do the job perfectly > > well for HVM guests. > > True. However, I was looking at supporting fbfront for a para-virtualized sles9 kernel.Take a look at the kernel at http://xenbits.xensource.com/kernels/sles9x.hg -- it contains the backport already. The driver itself is portable back to 2.6.5 (essentially for PV on HVM reasons) so all that is needed is to add some of the compatibility stuff to your kernel, somewhat like the PVM-on-HVM compat layer although in the kernel above I''ve just added the necessary functions directly instead of using the compat stuff itself. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks Ian. K. Y>>> On Thu, Jul 26, 2007 at 4:57 AM, in message<1185440254.3847.21.camel@localhost.localdomain>, Ian Campbell <Ian.Campbell@XenSource.com> wrote:> On Tue, 2007- 07- 24 at 09:53 - 0600, Ky Srinivasan wrote: >> >> >>> On Tue, Jul 24, 2007 at 11:42 AM, in message >> <C2CBDC86.12F42%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote: >> > The framebuffer device exported by qemu- dm seems to do the job perfectly >> > well for HVM guests. >> >> True. However, I was looking at supporting fbfront for a para- virtualized > sles9 kernel. > > Take a look at the kernel at > http://xenbits.xensource.com/kernels/sles9x.hg -- it contains the > backport already. > > The driver itself is portable back to 2.6.5 (essentially for PV on HVM > reasons) so all that is needed is to add some of the compatibility stuff > to your kernel, somewhat like the PVM- on- HVM compat layer although in > the kernel above I''ve just added the necessary functions directly > instead of using the compat stuff itself. > > Ian._______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> On Thu, Jul 26, 2007 at 4:57 AM, in message<1185440254.3847.21.camel@localhost.localdomain>, Ian Campbell <Ian.Campbell@XenSource.com> wrote:> On Tue, 2007- 07- 24 at 09:53 - 0600, Ky Srinivasan wrote: >> >> >>> On Tue, Jul 24, 2007 at 11:42 AM, in message >> <C2CBDC86.12F42%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote: >> > The framebuffer device exported by qemu- dm seems to do the job perfectly >> > well for HVM guests. >> >> True. However, I was looking at supporting fbfront for a para- virtualized > sles9 kernel. > > Take a look at the kernel at > http://xenbits.xensource.com/kernels/sles9x.hg -- it contains the > backport already. > > The driver itself is portable back to 2.6.5 (essentially for PV on HVM > reasons) so all that is needed is to add some of the compatibility stuff > to your kernel, somewhat like the PVM- on- HVM compat layer although in > the kernel above I''ve just added the necessary functions directly > instead of using the compat stuff itself.This is what I did over the last couple of days - I put some of the needed stuff (input_allocate_device() etc) in the platform-compat.c file. I have not tested the code yet. Regards, K. Y> > Ian. > > > > _______________________________________________ > Xen- devel mailing list > Xen- devel@lists.xensource.com > http://lists.xensource.com/xen- devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> On Thu, Jul 26, 2007 at 4:57 AM, in message<1185440254.3847.21.camel@localhost.localdomain>, Ian Campbell <Ian.Campbell@XenSource.com> wrote:> On Tue, 2007- 07- 24 at 09:53 - 0600, Ky Srinivasan wrote: >> >> >>> On Tue, Jul 24, 2007 at 11:42 AM, in message >> <C2CBDC86.12F42%keir@xensource.com>, Keir Fraser <keir@xensource.com> wrote: >> > The framebuffer device exported by qemu- dm seems to do the job perfectly >> > well for HVM guests. >> >> True. However, I was looking at supporting fbfront for a para- virtualized > sles9 kernel. > > Take a look at the kernel at > http://xenbits.xensource.com/kernels/sles9x.hg -- it contains the > backport already. > > The driver itself is portable back to 2.6.5 (essentially for PV on HVM > reasons) so all that is needed is to add some of the compatibility stuff > to your kernel, somewhat like the PVM- on- HVM compat layer although in > the kernel above I''ve just added the necessary functions directly > instead of using the compat stuff itself.This is what I did over the last couple of days - I put some of the needed stuff (input_allocate_device() etc) in the platform-compat.c file. I have not tested the code yet. Regards, K. Y> > Ian. > > > > _______________________________________________ > Xen- devel mailing list > Xen- devel@lists.xensource.com > http://lists.xensource.com/xen- devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel