From: Ben Guthro <ben@guthro.net>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Robert Phillips <robert.phillips@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Provide support for multiple frame buffers in Xen
Date: Thu, 10 Oct 2013 10:58:12 -0400 [thread overview]
Message-ID: <CAOvdn6WSqbD34eTRAMv8mHsA+8bM5hPdYW=14txcT9b5YdS8zA@mail.gmail.com> (raw)
In-Reply-To: <20131010144815.GA15556@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]
On Thu, Oct 10, 2013 at 10:48 AM, Wei Liu <wei.liu2@citrix.com> wrote:
> On Fri, Mar 01, 2013 at 08:48:57PM +0000, Robert Phillips wrote:
> > Support is provided for both shadow and hardware assisted paging (HAP)
> > modes. This code bookkeeps the set of video frame buffers (vram),
> > detects when the guest has modified any of those buffers and, upon
> request,
> > returns a bitmap of the modified pages.
> > This lets other software components re-paint the portions of the monitor
> > (or monitors) that have changed.
> > Each monitor has a frame buffer of some size at some position
> > in guest physical memory.
> > The set of frame buffers being tracked can change over time as monitors
> > are plugged and unplugged.
> >
> > This is the 9th version of this patch.
>
> Hi Robert, any news for v10 of this patch?
>
Robert has been asked to stop work on this, after so many submissions.
He has since been focusing on other projects - I don't think there has been
any additional effort put forth to get this upstream.
We (XenClient) maintain a patch queue, and will continue to carry this
patch, for now.
Ben
[-- Attachment #1.2: Type: text/html, Size: 1610 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-10-10 14:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 20:48 [PATCH] Provide support for multiple frame buffers in Xen Robert Phillips
2013-03-02 11:20 ` Pasi Kärkkäinen
2013-03-07 12:05 ` Tim Deegan
2013-10-10 14:48 ` Wei Liu
2013-10-10 14:58 ` Ben Guthro [this message]
2013-10-10 15:07 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 19:28 Robert Phillips
2013-01-22 7:31 ` Pasi Kärkkäinen
2013-01-24 11:25 ` Tim Deegan
2013-02-05 11:38 ` Robert Phillips
2013-02-07 11:04 ` Tim Deegan
2013-03-01 20:52 ` Robert Phillips
2013-01-16 15:11 Robert Phillips
2013-01-17 11:54 ` Tim Deegan
2013-01-02 14:47 Robert Phillips
2013-01-10 12:29 ` Tim Deegan
2013-01-16 15:10 ` Robert Phillips
2012-11-27 15:52 Robert Phillips
2012-11-15 15:38 Fabio Fantoni
2012-11-20 1:23 ` Ben Guthro
2012-11-12 21:31 Robert Phillips
2012-11-15 13:22 ` Tim Deegan
2012-11-27 15:58 ` Robert Phillips
2012-11-07 20:36 Robert Phillips
2012-10-16 18:15 Robert Phillips
2012-10-16 18:21 ` Robert Phillips
2012-10-22 16:10 ` Tim Deegan
2012-10-22 17:45 ` Robert Phillips
2012-11-01 11:03 ` Tim Deegan
2012-11-01 11:07 ` Robert Phillips
2012-11-01 11:43 ` Ian Campbell
2012-11-01 14:24 ` Tim Deegan
2012-11-07 20:36 ` Robert Phillips
2012-11-08 13:25 ` Tim Deegan
2012-11-12 21:31 ` Robert Phillips
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='CAOvdn6WSqbD34eTRAMv8mHsA+8bM5hPdYW=14txcT9b5YdS8zA@mail.gmail.com' \
--to=ben@guthro.net \
--cc=robert.phillips@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).