All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>, adeos-main <adeos-main@gna.org>
Subject: Re: [Xenomai-help] [Adeos-main] [RFT] ipipe patch for 2.6.35.3-x86
Date: Tue, 24 Aug 2010 18:44:37 +0200	[thread overview]
Message-ID: <1282668277.1961.139.camel@domain.hid> (raw)
In-Reply-To: <1282667450.1961.132.camel@domain.hid>

On Tue, 2010-08-24 at 18:30 +0200, Philippe Gerum wrote:
> On Tue, 2010-08-24 at 17:59 +0200, Jan Kiszka wrote:
> > Hi,
> > 
> > just uploaded a forward port of the 2.6.34 ipipe patch for x86 to latest
> > stable 2.6.35.3. It boots and runs fine here in 64-bit mode with Xenomai
> > head, but I only ran light tests so far. Anyone interested in upgrading
> > the host kernel (I think I read some request recently) is welcome to
> > give it a try and report results back (specifically on 32 bit as that is
> > a bit out of focus for me ATM). You can download the full git tree from
> > 
> > 	git://git.kiszka.org/ipipe-2.6.git queues/2.6.35-x86
> > 	(alternatively also via http://)
> > 
> > Looking forward to feedback,
> 
> The comment and the relevant code for 82a7dd3df needs fixing: all
> pipeline ports should expose 4 IPIs, named IPIPE_SERVICE_IPI[0-3].
> powerpc/SMP has one more up to 2.6.34, but IPI4 will disappear in
> 2.6.35. The upcoming arm/SMP port conforms to this requirement as well.
> Those are merely pipelined IPI channels, the way the arch-dep section
> manages to multiplex them (or not) over the available hw channel(s) is
> of course unspecified. The virtual IPI numbers are also unspecified.

Actually, the more I think of it, the less I see the value of checking
the parameter passed to such an internal call like __ipipe_send_ipi().
There is no user interaction with this code. So removing the test is
indeed better.

> 
> Nitpicking: if you intend to push this material to me at some point,
> please make sure to prefix commit subject lines with 'ipipe:' for the
> -noarch section, and 'x86/ipipe:' for the rest. I'm a grep fanboy, and
> this 'tends' to conform to linux mainline as well.
> 
> > Jan
> > 
> 

-- 
Philippe.




  parent reply	other threads:[~2010-08-24 16:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 15:59 [Xenomai-help] [RFT] ipipe patch for 2.6.35.3-x86 Jan Kiszka
2010-08-24 16:30 ` [Xenomai-help] [Adeos-main] " Philippe Gerum
2010-08-24 16:37   ` Jan Kiszka
2010-08-24 16:44   ` Philippe Gerum [this message]
2010-08-24 16:46     ` Jan Kiszka
2010-08-24 17:11       ` Philippe Gerum
2010-08-24 17:14         ` Jan Kiszka
2010-08-24 18:02           ` Philippe Gerum
2010-08-24 16:59 ` Philippe Gerum
2010-08-24 17:05   ` Jan Kiszka
2010-08-24 17:31     ` [Adeos-main] hostrt patches (was: [RFT] ipipe patch for 2.6.35.3-x86) Jan Kiszka
2010-08-24 21:01       ` [Adeos-main] hostrt patches Gilles Chanteperdrix
2010-08-25  8:31       ` [Adeos-main] hostrt patches (was: [RFT] ipipe patch for 2.6.35.3-x86) Philippe Gerum
2010-08-25  2:36 ` [Xenomai-help] [RFT] ipipe patch for 2.6.35.3-x86 Edward Hoffman
2010-08-25  7:03   ` Jan Kiszka
2010-08-25 14:53     ` Edward Hoffman
2010-08-25 14:59       ` Edward Hoffman
2010-08-25 18:00         ` Edward Hoffman
2010-08-26 10:55           ` Jan Kiszka
2010-08-26 14:16             ` Jan Kiszka

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=1282668277.1961.139.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=jan.kiszka@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.