From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>,
"keir.xen@gmail.com" <keir.xen@gmail.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [V2 PATCH 6/8] PVH dom0: Introduce p2m_map_foreign
Date: Tue, 26 Nov 2013 17:35:27 +0000 [thread overview]
Message-ID: <5294DBDF.30900@eu.citrix.com> (raw)
In-Reply-To: <1385482298.23112.110.camel@kazak.uk.xensource.com>
On 11/26/2013 04:11 PM, Ian Campbell wrote:
> On Tue, 2013-11-26 at 16:00 +0000, George Dunlap wrote:
>> On Sat, Nov 23, 2013 at 12:03 AM, Mukesh Rathor
>> <mukesh.rathor@oracle.com> wrote:
>>> In this patch, a new type p2m_map_foreign is introduced for pages
>>> that toolstack on PVH dom0 maps from foreign domains that its creating
>>> or supporting during it's run time.
>>>
>>> Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
>>
>> Why is this needed? Does ARM have a concept of p2m_map_foreign? grep
>> doesn't turn it up... how does ARM dom0 deal with foreign mappings,
>> and is there a reason we can't copy their approach?
>
> The p2m types are currently per-arch. ARM doesn't currently have much in
> the way of the concept of such things, but it should eventually and
> foreign map seems likely to be one of them.
Oh, right -- I see now; the interface Mukesh is implementing --
XENMAPSPACE_gmfn_foreign and XENMEM_add_to_physmap_range -- is basically
the same as the ARM dom0 interface.
That's an important piece of information.
-George
next prev parent reply other threads:[~2013-11-26 17:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 0:03 [V2 PATCH 0/8]: PVH dom0 Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 1/8] PVH dom0: iommu related changes Mukesh Rathor
2013-11-25 1:19 ` Konrad Rzeszutek Wilk
2013-11-25 8:47 ` Jan Beulich
2013-11-25 8:35 ` Jan Beulich
2013-11-26 14:57 ` George Dunlap
2013-11-23 0:03 ` [V2 PATCH 2/8] PVH dom0: create update_memory_mapping() function Mukesh Rathor
2013-11-25 8:43 ` Jan Beulich
2013-11-25 23:20 ` Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 3/8] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 4/8] dom0: construct_dom0 changes Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 5/8] PVH dom0: implement XENMEM_add_to_physmap_range for x86 Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 6/8] PVH dom0: Introduce p2m_map_foreign Mukesh Rathor
2013-11-26 16:00 ` George Dunlap
2013-11-26 16:11 ` Ian Campbell
2013-11-26 17:35 ` George Dunlap [this message]
2013-11-23 0:03 ` [V2 PATCH 7/8] pvh dom0: Add and remove foreign pages Mukesh Rathor
2013-11-25 9:03 ` Jan Beulich
2013-11-25 19:00 ` Daniel De Graaf
2013-11-26 0:32 ` Mukesh Rathor
2013-11-26 15:03 ` Daniel De Graaf
2013-11-27 1:19 ` Mukesh Rathor
2013-11-23 0:03 ` [V2 PATCH 8/8] pvh dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2013-11-25 9:04 ` Jan Beulich
2013-11-26 1:18 ` Mukesh Rathor
2013-11-25 9:06 ` [V2 PATCH 0/8]: PVH dom0 Jan Beulich
2013-11-25 10:49 ` George Dunlap
2013-11-25 10:57 ` Roger Pau Monné
2013-11-25 11:02 ` Jan Beulich
2013-11-26 17:20 ` George Dunlap
2013-11-26 18:06 ` Jan Beulich
2013-11-27 1:32 ` Mukesh Rathor
2013-11-25 11:05 ` Jan Beulich
2013-11-25 11:02 ` Roger Pau Monné
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=5294DBDF.30900@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=tim@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 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).