From: "Michael R. Hines" <mhines@cs.binghamton.edu>
To: mhines@cs.binghamton.edu
Cc: xen-devel@lists.xensource.com
Subject: Re: update_va_mapping_otherdomain
Date: Sat, 08 Sep 2007 14:27:51 -0400 [thread overview]
Message-ID: <46E2E9A7.7020205@cs.binghamton.edu> (raw)
In-Reply-To: <46E2BCF4.3020309@cs.binghamton.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1535 bytes --]
So, if I would like to use dom0 to modify a specific L1 PTE belonging
to another unprivileged domain, what's the best way to go about it?
Grant references? (on L1 page tables?)
Might I be able to get a quick pointer on the right sequence of hypercalls?
Much appreciated,
- Michael
Michael R. Hines wrote:
> ooooh, ok. I understand now.
>
> Thank you very much for your response. =)
>
> - Michael
>
> Keir Fraser wrote:
>> On 8/9/07 02:29, "Michael R. Hines" <mhines@cs.binghamton.edu> wrote:
>>
>>> Upon successful return from update_va_mapping (i.e. return code == zero),
>>> my problem involves the last step mentioned above. The present bit still
>>> remains unchanged (is still one), although update_va_mapping return true.
>>>
>>> What might cause such a strange problem to occur?
>> That hypercall allows you to update a *local* va mapping to map *another*
>> domain's memory page. So you've mapped the guest's page somewhere random in
>> your own address space.
>>
>> -- Keir
>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
/*
Michael R. Hines
http://www.cs.binghamton.edu/~mhines/
Live long and prosper...
*/
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-09-08 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 1:29 update_va_mapping_otherdomain Michael R. Hines
2007-09-08 9:00 ` update_va_mapping_otherdomain Keir Fraser
2007-09-08 15:17 ` update_va_mapping_otherdomain Michael R. Hines
2007-09-08 18:27 ` Michael R. Hines [this message]
2007-09-09 8:17 ` update_va_mapping_otherdomain Keir Fraser
2007-09-09 18:24 ` update_va_mapping_otherdomain Michael R. Hines
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=46E2E9A7.7020205@cs.binghamton.edu \
--to=mhines@cs.binghamton.edu \
--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.