Prev: x86, trigger NMI return notifier soft_irq earlier
Next: pid_ns: move pid_ns_release_proc() from proc_flush_task() to zap_pid_ns_processes()
From: Gui Jianfeng on 16 Jul 2010 03:40 Arnaldo Carvalho de Melo wrote: > Em Thu, Jun 24, 2010 at 03:04:02PM +0800, Gui Jianfeng escreveu: >> When I ran "perf kvm ... top", I encountered the following error output. >> >> Error: perfcounter syscall returned with -1 (Too many open files) >> >> Fatal: No CONFIG_PERF_EVENTS=y kernel support configured? >> >> Looking into perf, I found perf opens too many direcotries at initialization >> time, but forgets to close them. Here is the fix. >> >> Signef-off-by: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com> > > Thanks, will apply. Hi Arnaldo, Would you pick up this fix? Thanks, Gui > > - Arnaldo > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Arnaldo Carvalho de Melo on 16 Jul 2010 11:50
Em Fri, Jul 16, 2010 at 03:37:07PM +0800, Gui Jianfeng escreveu: > Arnaldo Carvalho de Melo wrote: > > Em Thu, Jun 24, 2010 at 03:04:02PM +0800, Gui Jianfeng escreveu: > >> When I ran "perf kvm ... top", I encountered the following error output. > >> > >> Error: perfcounter syscall returned with -1 (Too many open files) > >> > >> Fatal: No CONFIG_PERF_EVENTS=y kernel support configured? > >> > >> Looking into perf, I found perf opens too many direcotries at initialization > >> time, but forgets to close them. Here is the fix. > >> > >> Signef-off-by: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com> > > > > Thanks, will apply. > > Hi Arnaldo, > > Would you pick up this fix? It was already, no? Nope, I thought about that other one about . and .., will apply. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |