All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] arm: Late delivery of pending Linux signals?
Date: Wed, 18 Feb 2015 21:49:56 +0100	[thread overview]
Message-ID: <54E4FAF4.7050004@siemens.com> (raw)
In-Reply-To: <20150218192712.GJ30317@hermes.click-hack.org>

On 2015-02-18 20:27, Gilles Chanteperdrix wrote:
> On Wed, Feb 18, 2015 at 08:17:26PM +0100, Jan Kiszka wrote:
>> The Versatile Express is the ARM reference board, not something
>> arbitrary virtual. It's also what you get when you obtain the Fast Model
>> (CPU and system emulator) from ARM.
> 
> Nevertheless, it is a board that nobody uses for real projects,
> so adding support for it is still a waste of resources.

No need to worry, it mostly just works. Apparently, I-pipe already
covers the whole Cortex-A series with its unified timers, clocks, and
interrupt controllers. Well, with the exception of SoCs that have
additional interrupt controllers - like the NVIDIA Tegra124, which I'm
currently looking at for other purposes.

"Mostly" because sshd is dying for unknown reasons. Same rootfs, same
emulator but newer kernel without I-pipe, and it works fine. One after
the other.

BTW, I noticed that LPAE build is broken. Trivial to fix (missing
argument to cpu_switch_mm), but maybe there is more behind it as it was
not used so far. Anything mm-related that one has to look at carefully
on ARM(v7)?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  parent reply	other threads:[~2015-02-18 20:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 17:52 [Xenomai] arm: Late delivery of pending Linux signals? Jan Kiszka
2015-02-18 17:55 ` Gilles Chanteperdrix
2015-02-18 18:12   ` Jan Kiszka
2015-02-18 18:13     ` Gilles Chanteperdrix
2015-02-18 18:21       ` Jan Kiszka
2015-02-18 18:23         ` Gilles Chanteperdrix
2015-02-18 18:26         ` Gilles Chanteperdrix
2015-02-18 18:46           ` Jan Kiszka
2015-02-18 18:49             ` Gilles Chanteperdrix
2015-02-18 19:00               ` Jan Kiszka
2015-02-18 19:05                 ` Gilles Chanteperdrix
2015-02-18 19:17                   ` Jan Kiszka
2015-02-18 19:27                     ` Gilles Chanteperdrix
2015-02-18 19:39                       ` Gilles Chanteperdrix
2015-02-18 20:49                       ` Jan Kiszka [this message]
2015-02-18 20:56                         ` Gilles Chanteperdrix
2015-02-18 21:00                         ` Gilles Chanteperdrix
2015-02-18 21:28                           ` Jan Kiszka
2015-02-19 14:32                             ` [Xenomai] [PATCH] arm/ipipe: Fix logical inversion in ret_from_exception Jan Kiszka
2015-02-19 14:40                               ` Gilles Chanteperdrix
2015-02-19 14:43                                 ` Jan Kiszka
2015-02-19 14:46                                   ` Gilles Chanteperdrix
2015-02-19 15:13                         ` [Xenomai] arm: Late delivery of pending Linux signals? Lennart Sorensen
2015-02-19 15:16                           ` Lennart Sorensen
2015-02-19 17:13                           ` Philippe Gerum
2015-02-19 17:25                             ` Lennart Sorensen

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=54E4FAF4.7050004@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@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.