[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [PATCH 0/2] PV framebuffer


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
  • Date: Fri, 24 Nov 2006 09:05:19 +0100
  • Delivery-date: Fri, 24 Nov 2006 00:05:25 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Next iteration.  If there's anything left in the way of getting this
merged, please let me know right away.

Changes since last time:

* Leave xen console defaulting to /dev/tty1.

* Start backend automatically.

* Fix kernel thread to call try_to_freeze().

* Recreate the image sub-object in XendDomainInfo.py on resume.

* Implement frontend resume methods; xm save and restore work now.

* Implement orderly backend shutdown.

To activate the framebuffer, you have to put the following lines into
/etc/xen/DOMNAME:

    vfb = 'yes'
    vkbd = 'yes'

and either

    sdl = 1

or

    vnc = 1

One last thing to consider: I'm not entirely happy with source file
names and locations.  It's now or never for renames.  Peeves:

* Frontend source usually lives in drivers/xen/<WHAT>front.  xenfb and
  xenkbd are exceptions.  Rename to fbfront and kbdfront?  Same for
  the .c files.  This would also fix the minor annoyance of having the
  same file name in frontend and backend.

* Given how closely related xenfb and xenkbd are, I'm not fond of
  having them in separate directories.  Move kbd into the fb
  directory?

Anything else?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.