All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Marco Tessore <marco.tessore@axelsw.it>,
	Philippe Gerum <rpm@xenomai.org>,
	xenomai@xenomai.org
Subject: Re: [Xenomai] Kernel freezes in __ipipe_sync_stage
Date: Wed, 02 Jul 2014 19:41:05 +0200	[thread overview]
Message-ID: <53B44431.2050401@xenomai.org> (raw)
In-Reply-To: <53B434F4.6060203@axelsw.it>

On 07/02/2014 06:36 PM, Marco Tessore wrote:
> ipipe_mach_allow_hwtimer_uaccess(MX25_AIPS1_BASE_ADDR_VIRT,MX25_AIPS2_BASE_ADDR_VIRT);
>      return 0;
> }
> 
> postcore_initcall(post_cpu_init);
> #endif /* CONFIG_IPIPE */
> 
> 
> the question that I kindly ask is: what should do the function 
> ipipe_mach_allow_hwtimer_uaccess?

As the name suggests, this function allows access to the hardware timer
registers from user-space. Xenomai user-space libraries require this,
unless you compile xenomai with --disable-arm-tsc, but this will
increase (greatly) the latency of services such as rt_timer_tsc or
clock_gettime(CLOCK_MONOTONIC) by requiring a system call.

And it probably has nothing to do with your problem.


-- 
                                                                Gilles.


  reply	other threads:[~2014-07-02 17:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  9:11 [Xenomai] Kernel freezes in __ipipe_sync_stage Marco Tessore
2014-06-20 11:52 ` Gilles Chanteperdrix
2014-06-20 12:18   ` Marco Tessore
2014-06-20 12:25     ` Gilles Chanteperdrix
2014-06-24 16:41   ` Marco Tessore
2014-06-24 17:10     ` Philippe Gerum
2014-06-25  7:50       ` Marco Tessore
2014-06-25  8:39         ` Philippe Gerum
2014-07-02 16:36           ` Marco Tessore
2014-07-02 17:41             ` Gilles Chanteperdrix [this message]
2014-07-09 16:09           ` Marco Tessore

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=53B44431.2050401@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=marco.tessore@axelsw.it \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.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.