From: Peter Zijlstra <peterz@infradead.org>
To: Lin Ming <minggr@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
"; John Stultz" <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] seqlock: add lockdep support
Date: Wed, 18 Sep 2013 11:15:04 +0200 [thread overview]
Message-ID: <20130918091504.GM12926@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1379487433.19121.29.camel@minggr>
On Wed, Sep 18, 2013 at 02:57:13PM +0800, Lin Ming wrote:
> Hi,
>
> lockdep support for seqlock was discussed at:
> http://marc.info/?l=linux-kernel&m=137875860600648&w=2
>
> This is very draft patch to add lockdep support for seqlock.
> Actually, it doesn't work yet. I throw it out to get comments and help.
>
> TODO:
> - fix seqlock usage in vdso code
>
> I got below with this patch applied.
> There should be something wrong with this patch.
> Any idea?
You're aware of John Stultz's patches?
lkml.kernel.org/r/1379117948-7385-1-git-send-email-john.stultz@linaro.org
next prev parent reply other threads:[~2013-09-18 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 6:57 [RFC PATCH] seqlock: add lockdep support Lin Ming
2013-09-18 9:15 ` Peter Zijlstra [this message]
2013-09-18 9:29 ` Lin Ming
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=20130918091504.GM12926@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minggr@gmail.com \
--cc=mingo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox