From: Tim Deegan <tim@xen.org>
To: ???? <327801865@qq.com>
Cc: Xen-devel <Xen-devel@lists.xensource.com>
Subject: Re: HVM (hypercall_grant_table_op) Problem
Date: Thu, 24 Nov 2011 11:58:16 +0000 [thread overview]
Message-ID: <20111124115816.GD77868@ocelot.phlegethon.org> (raw)
In-Reply-To: <tencent_1975194D595A261C1C28650E@qq.com>
Hi,
At 00:52 +0800 on 18 Nov (1321577533), ???? wrote:
> Hi:
> I modified the netfont.c of Linux HVM domU installed PVonHVM.In it, I call hypercall_grant_table_op
> (GNTTABOP_map_grant_ref...), then dom0 shutdown and restart at once.
Do you have a serial line attached to the machine to capture the console
output when this happens? Without that it's hard to knwo what the bug is.
> From above, I conclude that I can map a HVM's page to another HVM, just like two PVs.
> Am I wrong? Who can give me some suggestion?
Yes, HVM guests can now map granted frames, but not quite 'just like pv'.
The grant hypercall maps the granted frame into the HVM guest's p2m map,
instead of into the pagetables. That is, you pass in a PFN, and when
the grant succeeds, you still need to map that PFN in your pagetables to
access the page.
The checkin that added the feature came with this comment:
After some discussion, here's a second version of the patch I posted a
couple of weeks back to map grant references into HVM guests. As
before, this is done by modifying the P2M map, but this time there's
no new hypercall to do it. Instead, the existing GNTTABOP_map is
overloaded to perform a P2M mapping if called from a shadow mode
translate guest. This matches the IA64 API.
http://xenbits.xen.org/hg/xen-unstable.hg/rev/c0cb307d927f
Tim.
next prev parent reply other threads:[~2011-11-24 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 16:52 HVM (hypercall_grant_table_op) Problem 马耀
2011-11-24 11:58 ` Tim Deegan [this message]
2012-01-03 20:30 ` 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=20111124115816.GD77868@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=327801865@qq.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).