From: Nicholas Mc Guire <der.herr@hofr.at>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users@vger.kernel.org,
Sami Pietikainen <Sami.Pietikainen@wapice.com>,
Jouko Haapaluoma <jouko.haapaluoma@wapice.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH RT] add missing local serialization in ip_output.c
Date: Fri, 17 Jan 2014 20:40:58 +0100 [thread overview]
Message-ID: <20140117194058.GA20157@opentech.at> (raw)
In-Reply-To: <20140117113218.7392363d@gandalf.local.home>
On Fri, 17 Jan 2014, Steven Rostedt wrote:
> On Fri, 17 Jan 2014 16:33:23 +0100
> Nicholas Mc Guire <der.herr@hofr.at> wrote:
>
> > On Fri, 17 Jan 2014, Sebastian Andrzej Siewior wrote:
> >
> > > On 01/17/2014 03:59 PM, Nicholas Mc Guire wrote:
> > > > On Fri, 17 Jan 2014, Sebastian Andrzej Siewior wrote:
> > > >
> > > >> This is what I am going to apply. It also dropped the get_cpu_light()
> > > >> call which was added in a patch to remove the get_cpu_var() and is now
> > > >> no longer required since we have the get_locked_var() thingy now.
> > > >>
> > > >
> > > > I do not think you can drop that - what is preventing migration now ?
> > >
> > > Nothing but I do not see the need for it.
> > >
> > > >
> > > > #define get_locked_var(lvar, var) \
> > > > (*({ \
> > > > local_lock(lvar); \
> > > > &__get_cpu_var(var); \
> > > > }))
> > > >
> > q> > No migrate_disable here - so how is this protected against migration ?
>
> I was just about to reply to this, that local_lock() grabs a spinlock
> which does do a migrate disable. But you also noticed that the
> get_local_var() does a migrate disable too. We now have double the
> protection, so we are safe as Sebastion has done it.
>
...well that motivates a further migration cleanup patch replacing
the spin_*lock* by spin_*lock*_local variants to drop that recursive call
and while checking call paths - do a little API cleanup for softirq_lock
thx!
hofrat
next prev parent reply other threads:[~2014-01-17 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 17:11 [PATCH RT] add missing local serialization in ip_output.c Nicholas Mc Guire
2013-12-31 7:36 ` Jouko Haapaluoma
2014-01-08 7:11 ` Sami Pietikäinen
2014-01-17 14:47 ` Sebastian Andrzej Siewior
2014-01-17 14:59 ` Nicholas Mc Guire
2014-01-17 15:13 ` Sebastian Andrzej Siewior
2014-01-17 15:33 ` Nicholas Mc Guire
2014-01-17 16:32 ` Steven Rostedt
2014-01-17 19:40 ` Nicholas Mc Guire [this message]
2014-01-17 19:41 ` [PATCH RT] use local spin_locks in local_lock Nicholas Mc Guire
2014-01-31 20:24 ` Sebastian Andrzej Siewior
2014-01-17 19:44 ` [PATCH] API cleanup - use local_lock not __local_lock for soft Nicholas Mc Guire
2014-01-31 20:28 ` Sebastian Andrzej Siewior
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=20140117194058.GA20157@opentech.at \
--to=der.herr@hofr.at \
--cc=Sami.Pietikainen@wapice.com \
--cc=bigeasy@linutronix.de \
--cc=jouko.haapaluoma@wapice.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.