From: "Waseem, Amna" <a.waseem@campus.tu-berlin.de>
To: Juergen Gross <jgross@suse.com>, Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Confused about mapped pages "struct page" updates
Date: Mon, 6 Nov 2017 10:29:14 +0000 [thread overview]
Message-ID: <1509964220546.75654@campus.tu-berlin.de> (raw)
In-Reply-To: <17526a11-7d00-c40e-3f8a-ecf810cdad23@suse.com>
Thanks a lot
I understood it now
________________________________________
From: Juergen Gross <jgross@suse.com>
Sent: Monday, November 6, 2017 11:24 AM
To: Waseem, Amna; Julien Grall
Cc: xen-devel; xen-devel@lists.xen.org
Subject: Re: [Xen-devel] Confused about mapped pages "struct page" updates
On 06/11/17 10:57, Waseem, Amna wrote:
> Hello All,
>
> I am a little confused about mapping mechanism in Xen for page from DomU to Dom0.
>
> When Dom0 maps DomU page to its applied host_addr, Page table entries are created by Xen hypervisor for mapping applied host_addr vritual address of Dom0 to DomU physical page. The result is host_addr maps to DomU phsyical page.
>
> Now in network backend driver, virt_to_page macro is called on this mapped host_addr. How does Dom0 gets struct page for the mapped DomU page in its domain? Is Xen also updates mem_map array of Dom0 to create struct page for the mapped page? Or Dom0 creates struct page for all the physical memory including provided to DomU during its creation ?
>
> Can anybody tell me how struct page for mapped pages from another domain gets updated or created in DOm0?
Dom0 requests the mapping for a specific Dom0 physical address
(normally this is a page from the balloon driver, but in case no
ballooned page is available a kernel page is being allocated for
that purpose). So there always is a struct page available in Dom0.
host_addr above is part of Dom0 physical addresses. And the hypervisor
either modifies the Dom0 page table entry (in case of a PV Dom0 on
X86) or it just modifies the p2m mapping of the Dom0 physical address
(in case of ARM).
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-11-06 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 13:47 Xen Grant table frames for granting access permissions Waseem, Amna
2017-11-06 9:57 ` Confused about mapped pages "struct page" updates Waseem, Amna
2017-11-06 10:24 ` Juergen Gross
2017-11-06 10:29 ` Waseem, Amna [this message]
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=1509964220546.75654@campus.tu-berlin.de \
--to=a.waseem@campus.tu-berlin.de \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xenproject.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).