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

[Markus Armbruster <armbru@xxxxxxxxxx>]

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

Changes since last time:

* Minor cleanup of how Xen console detects presence of framebuffer.

* Fix config XEN_KEYBOARD dependencies.

* Fix misuse of __devexit.

* Fix crash when kthread_run() fails.

* Work around xenbus race condition.

* Get rid of xenstore key console/use_graphics.

* Supply missing patch to mm/memory.c

* Fix typo in XendDevices.py

* xm configuration magic for xenfb and xenkbd devices.

* vncfb listens on 127.0.0.1 instead of 0.0.0.0 by default.

* backends put error node into xenstore.

* Move write of hotplug-status to the correct place.

* Make backend reconnect even when status is Closing or Closed.

Diffs since last time follow in separate messages.

Not in this patch, but coming soon: make xend start the backend
automatically.  For now, you need to start it manually, like this:

    # sdlfb -d $(xm domid parafat)

You also have to put the following lines into /etc/xen/DOMNAME:

    vfb = 'yes'
    vkbd = 'yes'

The framebuffer remains inactive without them.  That means behavior of
existing domains should not be affected, which is nice.

If you do put them in, xend will wait for you to start the backend
before it unpauses the domain.  It would be nice if it just went
along, and connecting a backend later just worked, but that's left for
another day.

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