From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754628Ab3HVX5t (ORCPT ); Thu, 22 Aug 2013 19:57:49 -0400 Received: from szxga01-in.huawei.com ([119.145.14.64]:12893 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752848Ab3HVX5s (ORCPT ); Thu, 22 Aug 2013 19:57:48 -0400 Message-ID: <5216A55B.4030400@huawei.com> Date: Fri, 23 Aug 2013 07:57:15 +0800 From: "zhangwei(Jovi)" User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Steven Rostedt CC: Masami Hiramatsu , Namhyung Kim , Namhyung Kim , Hyeoncheol Lee , LKML , Srikar Dronamraju , Oleg Nesterov , Arnaldo Carvalho de Melo Subject: Re: [PATCH 10/13] tracing/uprobes: Fetch args before reserving a ring buffer References: <1376037909-17797-1-git-send-email-namhyung@kernel.org> <1376037909-17797-11-git-send-email-namhyung@kernel.org> <5204BCE6.2070102@hitachi.com> <20130822124212.328c09c7@gandalf.local.home> In-Reply-To: <20130822124212.328c09c7@gandalf.local.home> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.66.58.241] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2013/8/23 0:42, Steven Rostedt wrote: > On Fri, 09 Aug 2013 18:56:54 +0900 > Masami Hiramatsu wrote: > >> (2013/08/09 17:45), Namhyung Kim wrote: >>> From: Namhyung Kim >>> >>> Fetching from user space should be done in a non-atomic context. So >>> use a temporary buffer and copy its content to the ring buffer >>> atomically. >>> >>> While at it, use __get_data_size() and store_trace_args() to reduce >>> code duplication. >> >> I just concern using kmalloc() in the event handler. For fetching user >> memory which can be swapped out, that is true. But most of the cases, >> we can presume that it exists on the physical memory. >> > > > What about creating a per cpu buffer when uprobes are registered, and > delete them when they are finished? Basically what trace_printk() does > if it detects that there are users of trace_printk() in the kernel. > Note, it does not deallocate them when finished, as it is never > finished until reboot ;-) > > -- Steve > I also thought out this approach, but the issue is we cannot fetch user memory into per-cpu buffer, because use per-cpu buffer should under preempt disabled, and fetching user memory could sleep. jovi.