From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: xentrace, arm, hvm Date: Tue, 04 Feb 2014 13:31:20 +0000 Message-ID: <52F0EBA8.3000206@linaro.org> References: <52EFFCF5.5070108@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Pavlo Suikov Cc: Stefano Stabellini , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 04/02/14 12:39, Pavlo Suikov wrote: > Well, Hello, Ian/Stefano may have a better answer than me on this part :). > > To support xentrace on ARM, we will need at least: > > I would readily do that if you give me some directions on where to look > at, or a high-level explanation of: > > > - to replace rcu_lock_domain_by_any_id() by a a similar function > > What semantics should this function have? I would copy in part get_pg_owner (arch/x86/mm/mm.c) in the ARM code. The check "unlikely(paging_mode_translate(curr))" will always fail on ARM. > > - to add stubs for trace in arm code > > Is there an example of what functionality should be stubbed in arm code? > You can look at __trace_hypercall_entry on x86, and x86/entry.S where the function is called. Sincerely yours, -- Julien Grall