From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Add grant references for fbfront/kbdfront
Date: Fri, 07 Jan 2011 14:32:13 -0500 [thread overview]
Message-ID: <4D276A3D.8040604@tycho.nsa.gov> (raw)
In-Reply-To: <20110107192115.GC27871@dumpdata.com>
On 01/07/2011 02:21 PM, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 07, 2011 at 12:55:24PM -0500, Daniel De Graaf wrote:
>> On 01/07/2011 11:51 AM, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Jan 07, 2011 at 11:12:56AM -0500, dgdegra@tycho.nsa.gov wrote:
>>>> This series fixes the interface for the fbfront and kbdfront devices,
>>>> which were storing MFNs in xenstore rather than creating grant table
>>>> entries. To maintain backwards compatibility, a different xenstore key
>>>> is used (page-gref instead of page-ref) and the use of grants must be
>>>> requested for fbfront (because two levels of page references are
>>>> embedded within the shared page). This makes it possible to move a
>>>> display server out of dom0 without giving the display domain full
>>>> access to other domain's memory.
>>>
>>> So these patches go on top of xen/stable-2.6.32 tree right?
>>>
>>
>> They apply to either 2.6.32 or 2.6.37; I have tested them on both.
>
> What is the 2.6.37 branch you applied it to? Can you point me to the
> git tree? Or a set of patches that need to be applied on top of ftp.kernel.org
> virgin 2.6.37?
>
It should apply on top of any 2.6.37 tree; I sent the patches from a
rebase on top of the v2.6.37 tag on ftp.kernel.org. They should apply
cleanly on any branch unless I missed other pending changes to fbfront.
--
Daniel De Graaf
National Security Agency
next prev parent reply other threads:[~2011-01-07 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 16:12 [PATCH] Add grant references for fbfront/kbdfront dgdegra
2011-01-07 16:12 ` [PATCH 1/3] xen-fbfront: Read width/height from backend dgdegra
2011-01-07 20:47 ` Ian Campbell
2011-01-07 21:30 ` Daniel De Graaf
2011-01-07 16:12 ` [PATCH 2/3] xen-fbfront: Use grant references when requested dgdegra
2011-01-07 20:44 ` Ian Campbell
2011-01-07 21:02 ` Daniel De Graaf
2011-01-07 21:41 ` Daniel De Graaf
2011-01-07 21:56 ` Ian Campbell
2011-01-07 16:12 ` [PATCH 3/3] xen-kbdfront: Add grant reference for shared page dgdegra
2011-01-07 16:51 ` [PATCH] Add grant references for fbfront/kbdfront Konrad Rzeszutek Wilk
2011-01-07 17:55 ` Daniel De Graaf
2011-01-07 18:28 ` Ian Campbell
2011-01-07 19:36 ` Daniel De Graaf
2011-01-07 20:44 ` Ian Campbell
2011-01-07 21:51 ` Daniel De Graaf
2011-01-07 22:09 ` [PATCH qemu] Support grant references in mapping Daniel De Graaf
2011-01-11 16:19 ` Ian Jackson
2011-02-25 15:01 ` Konrad Rzeszutek Wilk
2011-02-25 17:38 ` Stefano Stabellini
2011-01-07 19:21 ` [PATCH] Add grant references for fbfront/kbdfront Konrad Rzeszutek Wilk
2011-01-07 19:32 ` Daniel De Graaf [this message]
2011-01-07 19:51 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2011-03-15 14:11 Konrad Rzeszutek Wilk
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=4D276A3D.8040604@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=konrad.wilk@oracle.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 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).