From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] 3.14 hangs with ipipe patch applied
Date: Thu, 21 May 2015 19:10:18 +0200 [thread overview]
Message-ID: <20150521171018.GO10686@hermes.click-hack.org> (raw)
In-Reply-To: <20150521170716.GO6169@csclub.uwaterloo.ca>
On Thu, May 21, 2015 at 01:07:16PM -0400, Lennart Sorensen wrote:
> On Thu, May 21, 2015 at 01:04:32PM -0400, Lennart Sorensen wrote:
> > OK, I was not sure, hence why I wanted to ask.
> >
> > Let me fix that up and try that. Then I should do a build with
> > CONFIG_IPIPE=y and see if that then starts to work.
> >
> > At least this is progress.
>
> So this perhaps:
>
> --- debian/patches/ipipe-core-3.14.39.diff.original 2015-05-21 12:32:53.669255161 -0400
> +++ debian/patches/ipipe-core-3.14.39.diff 2015-05-21 13:06:12.075112664 -0400
> @@ -24605,7 +24605,7 @@
> static void gic_mask_irq(struct irq_data *d)
> {
> - u32 mask = 1 << (gic_irq(d) % 32);
> -+ u32 mask = 1 << (d->irq % 32);
> ++ u32 mask = 1 << (gic_irq(d) % 32);
> + unsigned long flags;
>
> - raw_spin_lock(&irq_controller_lock);
> @@ -24621,7 +24621,7 @@
> static void gic_unmask_irq(struct irq_data *d)
> {
> - u32 mask = 1 << (gic_irq(d) % 32);
> -+ u32 mask = 1 << (d->irq % 32);
> ++ u32 mask = 1 << (gic_irq(d) % 32);
> + unsigned long flags;
>
> - raw_spin_lock(&irq_controller_lock);
> @@ -24652,7 +24652,7 @@
> +
> +static void gic_hold_irq(struct irq_data *d)
> +{
> -+ u32 mask = 1 << (d->irq % 32);
> ++ u32 mask = 1 << (gic_irq(d) % 32);
> + unsigned long flags;
> +
> + raw_spin_lock_irqsave_cond(&irq_controller_lock, flags);
> @@ -24668,7 +24668,7 @@
> +
> +static void gic_release_irq(struct irq_data *d)
> +{
> -+ u32 mask = 1 << (d->irq % 32);
> ++ u32 mask = 1 << (gic_irq(d) % 32);
> + unsigned long flags;
> +
> + raw_spin_lock_irqsave_cond(&irq_controller_lock, flags);
Actually, gic_mask_irq and gic_unmask_irq should be identical to the
unpatched kernel with regard to registers reads and writes. And
gic_hold_irq/gic_release_irq should be identical to gic_mask/unmask.
--
Gilles.
next prev parent reply other threads:[~2015-05-21 17:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:33 [Xenomai] 3.14 hangs with ipipe patch applied Lennart Sorensen
2015-05-13 20:37 ` Gilles Chanteperdrix
2015-05-13 20:38 ` Lennart Sorensen
2015-05-14 16:23 ` Lennart Sorensen
2015-05-14 16:28 ` Gilles Chanteperdrix
2015-05-14 16:47 ` Lennart Sorensen
2015-05-14 19:34 ` Lennart Sorensen
2015-05-21 16:32 ` Lennart Sorensen
2015-05-21 16:34 ` Gilles Chanteperdrix
2015-05-21 16:59 ` Lennart Sorensen
2015-05-21 17:03 ` Gilles Chanteperdrix
2015-05-21 17:04 ` Lennart Sorensen
2015-05-21 17:07 ` Lennart Sorensen
2015-05-21 17:10 ` Gilles Chanteperdrix [this message]
2015-05-21 17:13 ` Lennart Sorensen
2015-05-21 17:16 ` Lennart Sorensen
2015-05-21 17:20 ` Gilles Chanteperdrix
2015-05-21 17:26 ` Lennart Sorensen
2015-05-21 17:29 ` 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=20150521171018.GO10686@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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.