All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Pavlo Suikov <pavlo.suikov@globallogic.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: xentrace, arm, hvm
Date: Tue, 04 Feb 2014 13:31:20 +0000	[thread overview]
Message-ID: <52F0EBA8.3000206@linaro.org> (raw)
In-Reply-To: <CAE4oM6ypZH_mgg7kuJJsKzPXRhy==HS2zw2pCx2VUHEP+i_D=w@mail.gmail.com>



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

  reply	other threads:[~2014-02-04 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 17:32 xentrace, arm, hvm Pavlo Suikov
2014-02-03 20:32 ` Julien Grall
2014-02-04 12:39   ` Pavlo Suikov
2014-02-04 13:31     ` Julien Grall [this message]
2014-02-04 13:57       ` Ian Campbell
2014-02-08 15:51         ` Pavlo Suikov
2014-02-08 16:53           ` Julien Grall
2014-02-08 21:04           ` Julien Grall

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=52F0EBA8.3000206@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=pavlo.suikov@globallogic.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.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 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.