All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen developer discussion <xen-devel@lists.xenproject.org>,
	Juergen Gross <jgross@suse.com>
Subject: Re: Mapping memory into a domain
Date: Mon, 5 May 2025 16:20:40 +0200	[thread overview]
Message-ID: <aBjJOFnO-Er7jLvA@macbook.lan> (raw)
In-Reply-To: <be15867a-f612-4a55-9324-099cae3a1e24@gmail.com>

On Sun, May 04, 2025 at 07:24:46PM -0400, Demi Marie Obenour wrote:
> On 5/4/25 6:56 PM, Andrew Cooper wrote:
> > On 04/05/2025 11:51 pm, Demi Marie Obenour wrote:
> >> What are the appropriate Xen internal functions for:
> >>
> >> 1. Turning a PFN into an MFN?
> >> 2. Mapping an MFN into a guest?
> >> 3. Unmapping that MFN from a guest?
> >>
> >> The first patch I am going to send with this information is a documentation
> >> patch so that others do not need to figure this out for themselves.
> >> I remember being unsure even after looking through the source code, which
> >> is why I am asking here.
> > 
> > See the top of xen/include/xen/mm.h which has an overview of
> > terminology, including an explanation of why Xen doesn't know what the
> > guest thinks of as PFN.
> I read that and am still confused.  Are you specifically referring to PV
> guests?  For PVH and HVM guests, Xen needs to know what the guest’s PFNs
> are so that it can correctly set up its own page tables.

The term PFN on PVH and HVM is confusing, and IMO it shouldn't be used
in that context.  PFNs should only be used in PV domains context.

I'm afraid I cannot understand the question in your last sentence.
What's "its own page tables"?  Are you referring to the domain second
stage translation page-tables, iow: the p2m?  Or is it something
else?

Regards, Roger.


  reply	other threads:[~2025-05-05 14:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 22:51 Mapping memory into a domain Demi Marie Obenour
2025-05-04 22:56 ` Andrew Cooper
2025-05-04 23:24   ` Demi Marie Obenour
2025-05-05 14:20     ` Roger Pau Monné [this message]
2025-05-05 11:32 ` Alejandro Vallejo
2025-05-06  1:02   ` Demi Marie Obenour
2025-05-06 13:06     ` Alejandro Vallejo
2025-05-06 20:56       ` Demi Marie Obenour
2025-05-07 17:39         ` Roger Pau Monné
2025-05-08  0:36           ` Demi Marie Obenour
2025-05-08  7:52             ` Roger Pau Monné
2025-05-09  4:52               ` Demi Marie Obenour
2025-05-09  8:53                 ` Roger Pau Monné
2025-05-09  9:47                 ` Alejandro Vallejo
2025-05-09 10:50                   ` Roger Pau Monné
2025-05-09 18:21                     ` Demi Marie Obenour
2025-05-12  8:08                       ` Roger Pau Monné
2025-05-12 23:18                         ` Demi Marie Obenour
2025-05-09 18:14                   ` Demi Marie Obenour
2025-05-09 18:30                   ` Demi Marie Obenour

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=aBjJOFnO-Er7jLvA@macbook.lan \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=demiobenour@gmail.com \
    --cc=jgross@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.