From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
devel@driverdev.osuosl.org, lttng-dev@lists.lttng.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Lameter <cl@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, David Howells <dhowells@redhat.com>,
David McCullough <davidm@snapgear.com>,
D Jeff Dionne <jeff@uClinux.org>,
Greg Ungerer <gerg@snapgear.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/11] mm: export vmalloc_sync_all symbol to GPL modules
Date: Thu, 1 Dec 2011 14:13:37 -0800 [thread overview]
Message-ID: <20111201221337.GB3365@kroah.com> (raw)
In-Reply-To: <20111201215700.GA16782@infradead.org>
On Thu, Dec 01, 2011 at 04:57:00PM -0500, Christoph Hellwig wrote:
> On Thu, Dec 01, 2011 at 04:41:13PM -0500, Mathieu Desnoyers wrote:
> > LTTng needs this symbol exported. It calls it to ensure its tracing
> > buffers and allocated data structures never trigger a page fault. This
> > is required to handle page fault handler tracing and NMI tracing
> > gracefully.
>
> We:
>
> a) don't export symbols unless they have an intree-user
lttng is now in-tree in the drivers/staging/ area. See linux-next for
details if you are curious.
> b) especially don't export something as lowlevel as this one.
Mathieu, there's nothing else you can do to get this information? Or
does lttng really want such lowlevel data?
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-01 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1322775683-8741-1-git-send-email-mathieu.desnoyers@efficios.com>
2011-12-01 21:41 ` Mathieu Desnoyers
2011-12-01 21:57 ` Christoph Hellwig
2011-12-01 22:13 ` Greg KH [this message]
2011-12-01 22:19 ` Mathieu Desnoyers
2011-12-01 22:41 ` Greg KH
2011-12-01 22:28 ` Christoph Hellwig
2011-12-01 23:00 ` Greg KH
2011-12-01 21:57 ` Christoph Hellwig
2011-12-01 21:57 ` Christoph Hellwig
2011-12-01 21:57 ` Christoph Hellwig
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=20111201221337.GB3365@kroah.com \
--to=greg@kroah.com \
--cc=cl@linux-foundation.org \
--cc=davidm@snapgear.com \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=gerg@snapgear.com \
--cc=hch@infradead.org \
--cc=jeff@uClinux.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=tj@kernel.org \
--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