All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tamas K Lengyel <tklengyel@sec.in.tum.de>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
	julien.grall@linaro.org, tim@xen.org,
	stefano.stabellini@citrix.com, keir@xen.org
Subject: [PATCH V15 6/9] xen/arm: Implement domain_get_maximum_gpfn
Date: Mon, 20 Apr 2015 17:06:21 +0200	[thread overview]
Message-ID: <1429542384-23905-7-git-send-email-tklengyel@sec.in.tum.de> (raw)
In-Reply-To: <1429542384-23905-1-git-send-email-tklengyel@sec.in.tum.de>

From: Julien Grall <julien.grall@linaro.org>

The function domain_get_maximum_gpfn is returning the maximum gpfn ever
mapped in the guest. We can use d->arch.p2m.max_mapped_gfn for this purpose.

We use this in xenaccess as to avoid the user attempting to set page
permissions on pages which don't exist for the domain, as a non-arch specific
sanity check.

Signed-off-by: Julien Grall <julien.grall@linaro.org>
---
 xen/arch/arm/mm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xen/arch/arm/mm.c b/xen/arch/arm/mm.c
index 11a0be8..a91ea77 100644
--- a/xen/arch/arm/mm.c
+++ b/xen/arch/arm/mm.c
@@ -996,7 +996,7 @@ int page_is_ram_type(unsigned long mfn, unsigned long mem_type)
 
 unsigned long domain_get_maximum_gpfn(struct domain *d)
 {
-    return -ENOSYS;
+    return d->arch.p2m.max_mapped_gfn;
 }
 
 void share_xen_page_with_guest(struct page_info *page,
-- 
2.1.4

  parent reply	other threads:[~2015-04-20 15:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 15:06 [PATCH V15 0/9] Mem_access for ARM Tamas K Lengyel
2015-04-20 15:06 ` [PATCH V15 1/9] xen/arm: groundwork for mem_access support on ARM Tamas K Lengyel
2015-04-20 15:06 ` [PATCH V15 2/9] xen/arm: Allow hypervisor access to mem_access protected pages Tamas K Lengyel
2015-04-21 13:14   ` Ian Campbell
2015-04-21 14:10     ` Tamas K Lengyel
2015-04-21 14:22       ` Ian Campbell
2015-04-20 15:06 ` [PATCH V15 3/9] xen/arm: Data abort exception (R/W) mem_access events Tamas K Lengyel
2015-04-21 13:16   ` Ian Campbell
2015-04-20 15:06 ` [PATCH V15 4/9] xen/arm: Instruction prefetch abort (X) mem_access event handling Tamas K Lengyel
2015-04-21 13:19   ` Ian Campbell
2015-04-20 15:06 ` [PATCH V15 5/9] xen: Make gpfn related memops compatible with wider return values Tamas K Lengyel
2015-04-20 15:22   ` Andrew Cooper
2015-04-20 15:25     ` Tamas K Lengyel
2015-04-21 13:23     ` Ian Campbell
2015-04-21 14:14       ` Jan Beulich
2015-04-21 14:24         ` Ian Campbell
2015-04-21 14:29           ` Jan Beulich
2015-04-21 14:42             ` Tamas K Lengyel
2015-04-21 15:13               ` Jan Beulich
2015-04-21 15:21                 ` Tamas K Lengyel
2015-04-25 16:54                 ` Julien Grall
2015-04-27  7:02                   ` Jan Beulich
2015-04-27 10:18                     ` Julien Grall
2015-04-21 14:47             ` Ian Campbell
2015-04-21 14:33         ` Tamas K Lengyel
2015-04-21 14:41           ` Jan Beulich
2015-04-20 15:06 ` Tamas K Lengyel [this message]
2015-04-21 13:24   ` [PATCH V15 6/9] xen/arm: Implement domain_get_maximum_gpfn Ian Campbell
2015-04-20 15:06 ` [PATCH V15 7/9] tools/libxc: Allocate magic page for mem access on ARM Tamas K Lengyel
2015-04-20 15:06 ` [PATCH V15 8/9] tools/tests: Enable xen-access " Tamas K Lengyel
2015-04-21 13:28   ` Ian Campbell
2015-04-21 14:13     ` Tamas K Lengyel
2015-04-20 15:06 ` [PATCH V15 9/9] xen/arm: Enable mem_access " Tamas K Lengyel
2015-04-22 13:29 ` [PATCH V15 0/9] Mem_access for ARM 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=1429542384-23905-7-git-send-email-tklengyel@sec.in.tum.de \
    --to=tklengyel@sec.in.tum.de \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 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.