All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Richard Cochran <richardcochran@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] arm ixp: more trouble with recent xenomai
Date: Thu, 12 May 2011 02:03:34 +0200	[thread overview]
Message-ID: <4DCB23D6.9010706@domain.hid> (raw)
In-Reply-To: <20110414164248.GA4725@domain.hid>

On 04/14/2011 06:42 PM, Richard Cochran wrote:
> On Sun, Apr 10, 2011 at 01:22:08PM +0200, Gilles Chanteperdrix wrote:
>> To help debugging this, please run the kernel which crashes with I-pipe
>> enabled, without Xenomai, and the attached test, in order to see if the
>> tsc behaves correctly.
> 
> Getting back to this, I did try the test program with ipipe 2.6.35 but
> without xenomai. It seems to run fine. But I only ran it for a few
> minutes.  The exact version was ipipe-2.6.35.9-arm-1.18-01 plus endian
> fix, and I attached the config.

Hi Richard,

the issue on ixp looks like the last one to be fixed on arm. If you have
time, could you try the following program? It makes a very basic test,
but not having a big-endian ixp at end, I am wondering about very basic
assumptions...:

#include <stdio.h>

__attribute__((naked)) unsigned long long f(unsigned long long *x)
{
	asm("ldrd r0, [r0]\n\t"
	    "mov pc, lr");
}

__attribute__((naked)) unsigned long long g(unsigned long long *x)
{
	asm("ldm r0, {r0, r1}\n\t"
	    "mov pc, lr");
}

int main(void)
{
	unsigned long long x = 0xffffffffULL;

	printf("f: %Lx\n", f(&x));
	printf("g: %Lx\n", g(&x));
	return 0;
}

If you do not have time, do you agree for a revert of the KUSER_TSC code
to the one we had before, and which is working for you?

Regards.

-- 
                                                                Gilles.


  parent reply	other threads:[~2011-05-12  0:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 18:41 [Xenomai-core] arm ixp: more trouble with recent xenomai Richard Cochran
2011-04-09 18:55 ` Richard Cochran
2011-04-09 19:37   ` Gilles Chanteperdrix
2011-04-09 19:50     ` Gilles Chanteperdrix
2011-04-10  5:22       ` Richard Cochran
2011-04-10  6:52       ` Richard Cochran
2011-04-10  9:34         ` Gilles Chanteperdrix
2011-04-11 17:14           ` Richard Cochran
2011-04-11 21:26             ` Gilles Chanteperdrix
2011-04-12  5:43               ` Richard Cochran
2011-04-12  7:17                 ` Gilles Chanteperdrix
2011-04-12  9:42                   ` Richard Cochran
2011-04-12 10:00                     ` Gilles Chanteperdrix
2011-04-14 16:49                   ` Richard Cochran
2011-04-15 13:18                     ` Gilles Chanteperdrix
2011-04-10 11:22         ` Gilles Chanteperdrix
2011-04-11  5:53           ` Richard Cochran
2011-04-11  7:24             ` Gilles Chanteperdrix
2011-04-14 16:42           ` Richard Cochran
2011-04-15 13:24             ` Gilles Chanteperdrix
2011-04-22  5:55               ` Gilles Chanteperdrix
2011-04-22  6:16                 ` Gilles Chanteperdrix
2011-04-23 14:21                 ` Richard Cochran
2011-04-23 15:22                   ` Gilles Chanteperdrix
2011-04-24 20:15                 ` Gilles Chanteperdrix
2011-04-25  6:48                   ` Richard Cochran
2011-04-25  7:29                     ` Gilles Chanteperdrix
2011-04-26 11:25                       ` Gilles Chanteperdrix
2011-05-12  0:03             ` Gilles Chanteperdrix [this message]
2011-05-12 17:04               ` Richard Cochran
2011-04-09 19:43 ` Gilles Chanteperdrix

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=4DCB23D6.9010706@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=richardcochran@domain.hid \
    --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.