All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Paul Janzen <pcj@xenomai.sez.to>,
	Philippe Gerum <rpm@xenomai.org>,
	xenomai@xenomai.org
Subject: Re: [Xenomai] real-time guarantee issues on xenomai 2.6.2.1
Date: Sun, 10 Aug 2014 17:56:59 +0200	[thread overview]
Message-ID: <53E7964B.6080200@xenomai.org> (raw)
In-Reply-To: <oqiom2n8ex.fsf@merlin.sez.to>

On 08/08/2014 08:27 PM, Paul Janzen wrote:
> Philippe Gerum <rpm@xenomai.org> writes:
> 
>> This option is for 3.8 which Ludovic runs. Do you still see the issue
>> with the one-liner patch I sent lately?
> 
> No, the one-liner successfully suppresses the problem on 3.4.

Without this one-liner, does one of the following patches help?

diff --git a/ksrc/nucleus/vfile.c b/ksrc/nucleus/vfile.c
index c8e0363..ff99536 100644
--- a/ksrc/nucleus/vfile.c
+++ b/ksrc/nucleus/vfile.c
@@ -278,7 +278,8 @@ redo:
 		if (ret != VFILE_SEQ_SKIP) {
 			data += vfile->datasz;
 			it->nrdata++;
-		}
+		} else
+			cpu_relax();
 	}

 	if (ret < 0) {


diff --git a/ksrc/nucleus/vfile.c b/ksrc/nucleus/vfile.c
index c8e0363..1702f08 100644
--- a/ksrc/nucleus/vfile.c
+++ b/ksrc/nucleus/vfile.c
@@ -278,7 +278,8 @@ redo:
 		if (ret != VFILE_SEQ_SKIP) {
 			data += vfile->datasz;
 			it->nrdata++;
-		}
+		} else
+			xnarch_memory_barrier();
 	}

 	if (ret < 0) {


-- 
                                                                Gilles.


  reply	other threads:[~2014-08-10 15:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AE39D2A4-ECC3-481B-AF3B-8A67FA23D2BF@tuebingen.mpg.de>
     [not found] ` <44BE6908-E639-421F-B556-E7B3871402CF@gmail.com>
2014-08-07 16:57   ` [Xenomai] real-time guarantee issues on xenomai 2.6.2.1 Alexander Herzog
2014-08-07 17:22     ` Gilles Chanteperdrix
2014-08-07 18:25       ` Philippe Gerum
2014-08-07 18:28         ` Gilles Chanteperdrix
2014-08-07 18:45           ` Philippe Gerum
2014-08-07 18:47       ` Paul Janzen
2014-08-07 19:01         ` Philippe Gerum
2014-08-07 19:16           ` Ludovic Righetti
2014-08-07 19:26             ` Philippe Gerum
2014-08-07 19:35               ` Ludovic Righetti
2014-08-07 19:44                 ` Philippe Gerum
2014-08-07 19:56                   ` Gilles Chanteperdrix
2014-08-08  6:59                     ` Philippe Gerum
2014-08-08 12:05                       ` Gilles Chanteperdrix
2014-08-07 20:47                   ` Ludovic Righetti
2014-08-08  7:15                     ` Philippe Gerum
2014-08-08 17:21                       ` Paul Janzen
2014-08-08 17:25                         ` Philippe Gerum
2014-08-08 18:27                           ` Paul Janzen
2014-08-10 15:56                             ` Gilles Chanteperdrix [this message]
2014-08-11 16:54                               ` Paul Janzen
2014-08-11 17:25                                 ` Gilles Chanteperdrix
2014-08-11 17:43                                   ` Paul Janzen
2014-09-09 21:05                                     ` Gilles Chanteperdrix
2014-09-10 17:12                                       ` Nicholas Rotella
2014-08-11 23:25                       ` Ludovic Righetti
2014-08-07 19:26         ` Gilles Chanteperdrix
2014-03-04 19:55 Alexander Herzog
2014-03-05  8:02 ` 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=53E7964B.6080200@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=pcj@xenomai.sez.to \
    --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.