All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat Campbell <plc@novell.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Dynamic modes support for xenfb (0 of 2)
Date: Thu, 13 Mar 2008 13:58:39 -0600	[thread overview]
Message-ID: <47D9876F.8060605@novell.com> (raw)

Patches 1of2 and 2of2 adds dynamic frame buffer resolution
support to the PV xenfb frame buffer driver and the PV xenfb
VNC server.

Don't know if you still need an API Changelog entry, included
it here just in case.

---------------------------------------------------------------
API Changelog entry:

 PV framebuffer dynamic resolution facility:

  Guest may send XENFB_TYPE_RESIZE if feature-resize = 1 in
  xenstore of the backend VNC server. VNC server code sets
  feature-resize if it can handle the resize request.

  VM kernel module parameter array, xenfb.video, is used to set
  the amount of frame buffer memory in MB allocated and the
  initial width and height.
 
  IE:  extra="xenfb.video=3,1024,768 "
   
  New xenstore virtual machine specific VNC attributes:
    videoram: Sets the maximum allowable frame buffer allocation
              size in MB.  Protects against a hostile frontend
              trying to run dom0 out of memory. Not set by defualt
 
  IE:  vfb=['type=vnc,vncunused=1,videoram=3']

 


---------------------------------------------------------------

Signed-off-by: Pat Campbell <plc@novell.com>

             reply	other threads:[~2008-03-13 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 19:58 Pat Campbell [this message]
2008-03-17 10:53 ` [PATCH] Dynamic modes support for xenfb (0 of 2) Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2008-03-25 20:10 Pat Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D9876F.8060605@novell.com \
    --to=plc@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.