All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Pat Campbell <plc@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Dynamic modes in PV xenfb?
Date: Thu, 22 Nov 2007 16:39:09 +0100	[thread overview]
Message-ID: <87tznez3vm.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <47440E7F.3E48.0018.0@novell.com> (Pat Campbell's message of "Wed\, 21 Nov 2007 10\:57\:50 -0700")

"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.
>
> Pat

The 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 pvfb
window 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.

      reply	other threads:[~2007-11-22 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 17:46 Please pull ia64 trees Alex Williamson
2007-11-21 17:57 ` Dynamic modes in PV xenfb? Pat Campbell
2007-11-22 15:39   ` Markus Armbruster [this message]

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=87tznez3vm.fsf@pike.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=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.