From: Paul Durrant <Paul.Durrant@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "annie.li@oracle.com" <annie.li@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Xen-devel] Regressions in v3.3-rc1 introduced by "xen/granttable: Grant tables V2 implementation"
Date: Wed, 25 Jan 2012 15:16:59 +0000 [thread overview]
Message-ID: <291EDFCB1E9E224A99088639C4762022C80E2F0F20@LONPMAILBOX01.citrite.net> (raw)
In-Reply-To: <1327485333.24561.232.camel@zakaz.uk.xensource.com>
> -----Original Message-----
>
> On HVM for gnttab_shared we make an add_to_physmap call with
> XENMAPSPACE_grant_table (in gnttab_map). I don't see any support call to
> do something similar for the status array though and I don't see a
> XENMAPSPACE_* specifically for that case either in the hypervisor either.
>
There is no map-space for the status pages. To map them you use the standard map space but OR a bit (top bit IIRC) into in the idx. It's a bit icky, but that's how it is.
Paul
next prev parent reply other threads:[~2012-01-25 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 4:49 Regressions in v3.3-rc1 introduced by "xen/granttable: Grant tables V2 implementation" Konrad Rzeszutek Wilk
2012-01-25 5:12 ` Konrad Rzeszutek Wilk
2012-01-25 9:55 ` Ian Campbell
2012-01-25 15:16 ` Paul Durrant [this message]
2012-01-25 15:47 ` [Xen-devel] " Ian Campbell
[not found] ` <45B8991A987A4149B40F1A061BF49097CBE27F2A88@LONPMAILBOX01.citrite.net>
2012-01-25 15:51 ` Ian Campbell
2012-01-25 15:23 ` Paul Durrant
2012-01-25 15:49 ` Ian Campbell
2012-01-25 20:50 ` Konrad Rzeszutek Wilk
2012-01-25 22:34 ` Ian Campbell
2012-01-25 20:46 ` Konrad Rzeszutek Wilk
2012-01-25 22:30 ` Ian 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=291EDFCB1E9E224A99088639C4762022C80E2F0F20@LONPMAILBOX01.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=annie.li@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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).