All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: obtain a list of granttable PFNs from toolstack
Date: Wed, 28 Apr 2021 12:17:01 +0200	[thread overview]
Message-ID: <20210428121701.3272b369.olaf@aepfle.de> (raw)
In-Reply-To: <8427397f-0953-94df-04f6-8dfe2a4ceee8@suse.com>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

Am Wed, 28 Apr 2021 11:49:59 +0200
schrieb Jan Beulich <jbeulich@suse.com>:

> On 28.04.2021 09:50, Olaf Hering wrote:
> > Is there an API to get a list of PFNs which are currently being active in the grant table for a given domid?  
> Do you really mean PFNs?

The save/restore code uses the term "pfn" to refer to page indices from the domU point of view. Since I usually just follow the HVM code paths, the term might indeed be incorrect for PV.

> Also, what do you mean by "active in the grant table"?

I'm not familiar with grants. My guess is, a domU pro-actively shares some of its pages with someone else. These shared pages have to be tracked somewhere, and I guess Xen has to establish proper access permissions for such pages. I guess the "grant table" is the place where things are collected.

Looking through xen/grant_table.h, I see no API. But that might be the wrong place anyway.

Olaf

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-28 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  7:50 obtain a list of granttable PFNs from toolstack Olaf Hering
2021-04-28  9:49 ` Jan Beulich
2021-04-28 10:17   ` Olaf Hering [this message]
2021-04-28 10:42     ` Jan Beulich
2021-04-28 11:03       ` Olaf Hering
2021-04-28 11:43         ` Andrew Cooper
2021-04-28 12:50           ` Olaf Hering
2021-04-28 11:10     ` Andrew Cooper

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=20210428121701.3272b369.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=jbeulich@suse.com \
    --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 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.