From: Julien Grall <julien.grall@arm.com>
To: Ben Sanda <Ben.Sanda@dornerworks.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"sstabellini@kernel.org" <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 2/5] xentrace: Memory/Page Mapping support for DOMID_XEN on ARM
Date: Wed, 20 Apr 2016 13:48:27 +0100 [thread overview]
Message-ID: <57177A9B.3020604@arm.com> (raw)
In-Reply-To: <A2A949C387F3A54C9B4DAC2DCD2E9A85E333CDA3@Quimby.dw.local>
On 14/04/16 20:52, Ben Sanda wrote:
> Julien, George, Andrew, and Stefano,
Hello Ben,
Sorry for the late answer, we were at the Xen hackathon.
>
>> Thank you for the explanation.
>>
>> The ARM implementation of share_xen_page_with_guest is nearly the same
>> as the x86 one. However, the type is never used so far for the P2M
>> code.
>>
>> So far, all ARM domains have been auto-translated. DOMID_XEN is the
>> first non auto-translated domain.
>>
>> We could make DOMID_XEN an auto-translated domain by introducing page
>> table for dummy domain. This would make the code cleaner but use more
>> memory (allocation of 3 level of page tables).
>>
>> Stefano, do you have any opinions on this?
>
> How would you like to me proceed with this issue with regard to the
> patch set? It sounds like this is a more far reaching architecture
> design question for ARM. I have made the other changes to this version
> of the code requested, should I submit v4? Or wait for a further
> resolution to this discussion?
This patch is the meat of this series. The result of the discussion may
change drastically the way this series add support to map xenhap page in
the guest.
So I would wait until we agree on the solution.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-20 12:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 18:48 [PATCH v3 0/5] xentrace/xenalyze Support on ARM Benjamin Sanda
2016-04-04 18:48 ` [PATCH v3 1/5] xentrace: Common Support for get_pg_owner/put_pg_owner on ARM and x86 Benjamin Sanda
2016-04-04 23:05 ` Andrew Cooper
2016-04-05 8:12 ` Jan Beulich
2016-04-14 19:59 ` Ben Sanda
2016-04-17 7:58 ` Jan Beulich
2016-04-04 18:48 ` [PATCH v3 2/5] xentrace: Memory/Page Mapping support for DOMID_XEN on ARM Benjamin Sanda
2016-04-08 10:42 ` Julien Grall
2016-04-08 15:49 ` Jan Beulich
2016-04-08 17:58 ` Andrew Cooper
2016-04-11 9:52 ` George Dunlap
2016-04-12 15:53 ` Julien Grall
2016-04-14 19:52 ` Ben Sanda
2016-04-20 12:48 ` Julien Grall [this message]
2016-04-22 9:42 ` Stefano Stabellini
2016-04-22 17:01 ` Julien Grall
2016-04-04 18:48 ` [PATCH v3 3/5] xentrace: Timestamp support for ARM platform Benjamin Sanda
2016-04-08 10:50 ` Julien Grall
2016-04-11 14:56 ` Konrad Rzeszutek Wilk
2016-04-04 18:48 ` [PATCH v3 4/5] xentrace: Trace Buffer Initialization on ARM Benjamin Sanda
2016-04-08 10:53 ` Julien Grall
2016-04-04 18:48 ` [PATCH v3 5/5] xenalyze: Build for Both ARM and x86 Platforms Benjamin Sanda
2016-04-05 8:09 ` [PATCH v3 0/5] xentrace/xenalyze Support on ARM Jan Beulich
2016-04-06 16:51 ` Ben Sanda
2016-04-06 16:59 ` Andrew Cooper
2016-04-06 17:03 ` Ben Sanda
2016-04-08 14:44 ` George Dunlap
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=57177A9B.3020604@arm.com \
--to=julien.grall@arm.com \
--cc=Ben.Sanda@dornerworks.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=sstabellini@kernel.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).