All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: 梁权 <liang_1911@163.com>
Cc: xenomai@xenomai.org
Subject: Re: every millicsecond interrupt in xenomai domain on a am355x board can cause something wrong?
Date: Sun, 2 Dec 2018 11:00:44 +0100	[thread overview]
Message-ID: <889b8735-6c75-fd3a-ef82-616bdd4b74a4@xenomai.org> (raw)
In-Reply-To: <29ea1621.1e55.1676dbe7a00.Coremail.liang_1911@163.com>

On 12/2/18 8:07 AM, 梁权 wrote:
> To simplify the problem, i do a test without QT like the following program:
> #define MALLOC_SIZE 8*1024*1024
> int main()
> {
> int err;
> char *addr=(char *)0;
> time_t now;
> struct tm *timenow;
> time(&now);
> timenow = localtime(&now);
> printf("%s\n", asctime(timenow));
> addr = (char *)malloc(MALLOC_SIZE);
> if (addr)
> printf("malloc ok\n");
> do
> {
> if (addr){
> memset(addr, 0x12, MALLOC_SIZE/2);
>                         memset(addr + MALLOC_SIZE/2, 0x34, MALLOC_SIZE/2);
> }
> usleep(1000);
> }while(1);
> return 0;
> }
> After i enable the interrupt for several minutes,  the error occur:
> root@am335x-evm:~/tmp# ./testMemset

Ok, thanks for investing time in creating this test snippet. I'll divert
some cycles in a few days to look into this.

-- 
Philippe.


  reply	other threads:[~2018-12-02 10:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29  8:03 every millicsecond interrupt in xenomai domain on a am355x board can cause something wrong? 梁权
2018-11-29 11:14 ` Jan Kiszka
2018-11-29 15:15   ` 梁权
2018-11-29 15:25     ` Jan Kiszka
2018-11-29 15:58       ` 梁权
2018-11-29 14:34 ` Philippe Gerum
2018-11-29 15:27   ` 梁权
2018-11-29 15:39     ` Greg Gallagher
2018-11-29 15:50       ` 梁权
2018-11-29 16:40 ` Philippe Gerum
2018-11-30 16:44   ` 梁权
2018-12-02  7:07     ` 梁权
2018-12-02 10:00       ` Philippe Gerum [this message]
2018-12-05  4:17         ` 梁权

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=889b8735-6c75-fd3a-ef82-616bdd4b74a4@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=liang_1911@163.com \
    --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.