From: Roland Dreier <rdreier@cisco.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
general@lists.openfabrics.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [ofa-general] Re: [GIT PULL] please pull ummunotify
Date: Tue, 15 Sep 2009 07:57:56 -0700 [thread overview]
Message-ID: <ada7hw0gsqz.fsf@cisco.com> (raw)
In-Reply-To: <20090915113434.GF1328@ucw.cz> (Pavel Machek's message of "Tue, 15 Sep 2009 13:34:34 +0200")
> I don't remember seeing discussion of this on lkml. Yes it is in
> -next...
eg http://lkml.org/lkml/2009/7/31/197 and followups, or search for v2
and earlier patches.
> Basically it allows app to 'trace itself'? ...with interesting mmap()
> interface, exporting int to userspace, hoping it behaves atomically...?
Yes, it allows app to trace what the kernel does to memory mappings. I
don't believe there's any real issue to atomicity of mmap'ed memory,
since userspace really just tests whether read value is == to old read
value or not.
- R.
next prev parent reply other threads:[~2009-09-15 14:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 4:38 [GIT PULL] please pull ummunotify Roland Dreier
2009-09-11 5:56 ` KOSAKI Motohiro
2009-09-11 6:03 ` Roland Dreier
2009-09-11 6:11 ` KOSAKI Motohiro
2009-09-11 16:42 ` Gleb Natapov
2009-09-11 6:15 ` Brice Goglin
2009-09-11 6:21 ` KOSAKI Motohiro
2009-09-11 6:22 ` Roland Dreier
2009-09-11 6:40 ` [ofa-general] " Jason Gunthorpe
2009-09-11 16:58 ` Roland Dreier
2009-09-15 7:03 ` KOSAKI Motohiro
2009-09-15 8:27 ` Roland Dreier
2009-09-15 12:38 ` Jeff Squyres
2009-09-15 11:34 ` Pavel Machek
2009-09-15 14:57 ` Roland Dreier [this message]
2009-09-28 20:49 ` [ofa-general] " Pavel Machek
2009-09-28 21:40 ` Jason Gunthorpe
2009-09-16 16:30 ` Roland Dreier
2009-09-16 16:40 ` Linus Torvalds
2009-09-17 11:30 ` Peter Zijlstra
2009-09-17 14:24 ` [ofa-general] " Roland Dreier
2009-09-17 14:32 ` Roland Dreier
2009-09-17 14:49 ` Peter Zijlstra
2009-09-17 15:03 ` Roland Dreier
2009-09-17 15:22 ` Peter Zijlstra
2009-09-17 15:45 ` Roland Dreier
2009-09-18 11:50 ` Ingo Molnar
2009-09-29 17:13 ` Pavel Machek
2009-09-30 9:44 ` Ingo Molnar
2009-09-30 16:02 ` Jason Gunthorpe
2009-10-12 18:19 ` Ingo Molnar
2009-10-12 19:30 ` Jason Gunthorpe
2009-10-12 20:20 ` Ingo Molnar
2009-10-13 4:05 ` Jason Gunthorpe
2009-10-13 6:40 ` Ingo Molnar
2009-10-13 16:27 ` Jason Gunthorpe
2009-10-13 5:43 ` Brice Goglin
2009-10-13 6:38 ` Ingo Molnar
2009-09-30 17:06 ` Roland Dreier
2009-10-02 16:32 ` Roland Dreier
2009-10-02 20:45 ` Pavel Machek
2009-10-07 22:34 ` Roland Dreier
2009-10-12 17:33 ` Peter Zijlstra
2009-09-17 14:43 ` Peter Zijlstra
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=ada7hw0gsqz.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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