RE: [PATCH] sched: don't output cpu sched info by default

- From: Zhang, Yanmin Sent: Tuesday, April 26, 2016 9:04 AM To: Afzal Mohammed; Zhang, LongX Cc: mi...@redhat.com; pet...@infradead.org; linux-kernel@vger.kernel.org Subject: RE: [PATCH] sched: don't output cpu sched info by default Thanks for the pointer. We didn't notice that. That patch also

RE: [PATCH] sched: don't output cpu sched info by default

- From: Zhang, Yanmin Sent: Tuesday, April 26, 2016 9:04 AM To: Afzal Mohammed; Zhang, LongX Cc: mi...@redhat.com; pet...@infradead.org; linux-kernel@vger.kernel.org Subject: RE: [PATCH] sched: don't output cpu sched info by default Thanks for the pointer. We didn't notice that. That patch also

RE: [PATCH] sched: don't output cpu sched info by default

@vger.kernel.org; Zhang, Yanmin Subject: Re: [PATCH] sched: don't output cpu sched info by default Hi, On Mon, Apr 25, 2016 at 01:04:41PM +0800, Zhang Long wrote: > Android userspace debug prcoess might dump system info by sysrq. > One info is of cpu sched. Usually, one thread has one lin

RE: [PATCH] sched: don't output cpu sched info by default

@vger.kernel.org; Zhang, Yanmin Subject: Re: [PATCH] sched: don't output cpu sched info by default Hi, On Mon, Apr 25, 2016 at 01:04:41PM +0800, Zhang Long wrote: > Android userspace debug prcoess might dump system info by sysrq. > One info is of cpu sched. Usually, one thread has one lin

Re: [PATCH] trace: correct start_index in find_next

On 2016/1/7 11:50, Steven Rostedt wrote: > On Thu, 07 Jan 2016 10:56:56 +0800 > "Zhang, Yanmin" wrote: > >> How is this patch? It fixes a kernel panic. >> > Linus already pulled it. It's also marked for stable. See commit: > f36d1be2930ede0a1947686e1126ffda5d

Re: [PATCH] trace: correct start_index in find_next

On 2015/12/31 13:11, Qiu, PeiyangX wrote: > From: Qiu Peiyang > > When we do cat /sys/kernel/debug/tracing/printk_formats, we hit kernel > panic at t_show. > > general protection fault: [#1] PREEMPT SMP > CPU: 0 PID: 2957 Comm: sh Tainted: G W O 3.14.55-x86_64-01062-gd4acdc7 #2 > RIP:

Re: [PATCH] trace: correct start_index in find_next

On 2015/12/31 13:11, Qiu, PeiyangX wrote: > From: Qiu Peiyang > > When we do cat /sys/kernel/debug/tracing/printk_formats, we hit kernel > panic at t_show. > > general protection fault: [#1] PREEMPT SMP > CPU: 0 PID: 2957 Comm: sh Tainted: G W O

Re: [PATCH] trace: correct start_index in find_next

On 2016/1/7 11:50, Steven Rostedt wrote: > On Thu, 07 Jan 2016 10:56:56 +0800 > "Zhang, Yanmin" <yanmin_zh...@linux.intel.com> wrote: > >> How is this patch? It fixes a kernel panic. >> > Linus already pulled it. It's also marked for stable. See commit: &g

Re: [PATCH 2/2] module: deal with the failure of complete_formation

On 2016/1/6 9:29, Steven Rostedt wrote: > On Wed, 06 Jan 2016 09:14:42 +0800 > "Zhang, Yanmin" wrote: > > >> It's a good idea although ftrace_module_init_fail might be complicated. > How so? I posted the patch. All it does is to call > ftrace_release_m

Re: [PATCH 2/2] module: deal with the failure of complete_formation

gt; The patch fixes it by tuning the operation sequence in >> complete_formation. After complete_formation checks >> verify_export_symbols, call ftrace_module_init to init >> ftrace records. >> >> Signed-off-by: Qiu Peiyang >> Signed-off-by: Zhang Yanmin >> --- >> kern

Re: [PATCH 2/2] module: deal with the failure of complete_formation

gt; ftrace records of the module. >> >> The patch fixes it by tuning the operation sequence in >> complete_formation. After complete_formation checks >> verify_export_symbols, call ftrace_module_init to init >> ftrace records. >> >> Signed-off-by: Qiu Peiyang &

Re: [PATCH 2/2] module: deal with the failure of complete_formation

On 2016/1/6 9:29, Steven Rostedt wrote: > On Wed, 06 Jan 2016 09:14:42 +0800 > "Zhang, Yanmin" <yanmin_zh...@linux.intel.com> wrote: > > >> It's a good idea although ftrace_module_init_fail might be complicated. > How so? I posted the patch. All it does is

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 22:28, Steven Rostedt wrote: > On Wed, 16 Dec 2015 18:28:35 +0800 > "Zhang, Yanmin" wrote: > >>> + /* >>> +* If the tracing is enabled, go ahead and enable the record. >>> +* >>> +* The reason not to enable t

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 1:37, Steven Rostedt wrote: > On Tue, 15 Dec 2015 11:26:41 +0800 > "Zhang, Yanmin" wrote: > >>> This seems very hackish, although I can't think of a better way at the >>> moment. But I would like not to add more code into module.c if >>

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 22:28, Steven Rostedt wrote: > On Wed, 16 Dec 2015 18:28:35 +0800 > "Zhang, Yanmin" <yanmin_zh...@linux.intel.com> wrote: > >>> + /* >>> +* If the tracing is enabled, go ahead and enable the record. >>> +* >>

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 1:37, Steven Rostedt wrote: > On Tue, 15 Dec 2015 11:26:41 +0800 > "Zhang, Yanmin" <yanmin_zh...@linux.intel.com> wrote: > >>> This seems very hackish, although I can't think of a better way at the >>> moment. But I would like not to

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 1:37, Steven Rostedt wrote: > On Tue, 15 Dec 2015 11:26:41 +0800 > "Zhang, Yanmin" wrote: > >>> This seems very hackish, although I can't think of a better way at the >>> moment. But I would like not to add more code into module.c if >>

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/16 1:37, Steven Rostedt wrote: > On Tue, 15 Dec 2015 11:26:41 +0800 > "Zhang, Yanmin" <yanmin_zh...@linux.intel.com> wrote: > >>> This seems very hackish, although I can't think of a better way at the >>> moment. But I would like not to

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/15 9:05, Zhang, Yanmin wrote: > On 2015/12/14 23:51, Steven Rostedt wrote: >> On Mon, 14 Dec 2015 11:16:18 +0800 >> "Qiu, PeiyangX" wrote: >> >>> We hit ftrace_bug report when booting Android on a 64bit ATOM SOC chip. >&

Re: [PATCH] ftrace: fix race between ftrace and insmod

fully resolve the issue. >> >> THis patch holds ftrace_mutex across ftrace_module_init and >> complete_formation. >> >> Signed-off-by: Qiu Peiyang >> Signed-off-by: Zhang Yanmin > First, this patch has major whitespace damage. All tabs are now spaces! Sorry. T

Re: [PATCH] ftrace: fix race between ftrace and insmod

) call into load_module() >> >> But it can't fully resolve the issue. >> >> THis patch holds ftrace_mutex across ftrace_module_init and >> complete_formation. >> >> Signed-off-by: Qiu Peiyang <peiyangx@intel.com> >> Signed-off-by: Zhan

Re: [PATCH] ftrace: fix race between ftrace and insmod

On 2015/12/15 9:05, Zhang, Yanmin wrote: > On 2015/12/14 23:51, Steven Rostedt wrote: >> On Mon, 14 Dec 2015 11:16:18 +0800 >> "Qiu, PeiyangX" <peiyangx@intel.com> wrote: >> >>> We hit ftrace_bug report when booting Android on a 64bit ATOM SO

Re: [PATCH] smpboot.c: move setup_vector_irq after set_cpu_online

On 2015/7/2 15:02, Xiao, Jin wrote: > Hi Joerg, > > On 7/2/2015 2:52 PM, Joerg Roedel wrote: >> Hi Jin, >> >> On Thu, Jul 02, 2015 at 12:24:34PM +0800, xiao jin wrote: >>> [ 106.107851] BUG: unable to handle kernel NULL pointer dereference at >>> 0040 >>> [ 106.116702] IP: >>> [

Re: [PATCH] smpboot.c: move setup_vector_irq after set_cpu_online

On 2015/7/2 15:02, Xiao, Jin wrote: Hi Joerg, On 7/2/2015 2:52 PM, Joerg Roedel wrote: Hi Jin, On Thu, Jul 02, 2015 at 12:24:34PM +0800, xiao jin wrote: [ 106.107851] BUG: unable to handle kernel NULL pointer dereference at 0040 [ 106.116702] IP: [ 106.118490]

Re: [PATCH] slub/slab: fix kmemleak didn't work on some case

On 2015/6/9 23:03, Catalin Marinas wrote: > On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote: >> On 2015/6/8 18:13, Catalin Marinas wrote: >>> As I replied already, I don't think this is that bad, or at least not >>> worse than what kmemleak already does (

Re: [PATCH] slub/slab: fix kmemleak didn't work on some case

On 2015/6/9 23:03, Catalin Marinas wrote: On Tue, Jun 09, 2015 at 09:10:45AM +0100, Zhang, Yanmin wrote: On 2015/6/8 18:13, Catalin Marinas wrote: As I replied already, I don't think this is that bad, or at least not worse than what kmemleak already does (looking at all data whether it's

Re: [PATCH] slub/slab: fix kmemleak didn't work on some case

On 2015/6/8 18:13, Catalin Marinas wrote: > On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote: >> On Mon, 8 Jun 2015, Liu, XinwuX wrote: >> >>> when kernel uses kmalloc to allocate memory, slub/slab will find >>> a suitable kmem_cache. Ususally the cache's object size is often >>>

Re: [PATCH] slub/slab: fix kmemleak didn't work on some case

On 2015/6/8 18:13, Catalin Marinas wrote: On Mon, Jun 08, 2015 at 10:38:13AM +0100, Christoph Lameter wrote: On Mon, 8 Jun 2015, Liu, XinwuX wrote: when kernel uses kmalloc to allocate memory, slub/slab will find a suitable kmem_cache. Ususally the cache's object size is often greater than

Re: [PATCH V3 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

On 2015/5/27 12:13, Zhang, Yanmin wrote: > Resend as V1/V2 have email format issue. Sorry for bothering. Greg, We have to abandon this patchset. Zhuang Jin Can, a USB expert, reviewed the patches. He says acm_tty_write already considers it carefully. acm_tty_write puts the urb to a dela

[PATCH V3 1/3] usb: add function usb_autopm_get_interface_upgrade

From: Zhang Yanmin Some usb driver has a specific requirement. Their critical functions might be called under both atomic environment and non-atomic environment. If it's under atomic environment, the driver can wake up the device by calling pm_runtime_get_sync directly. If it's under non

[PATCH V3 3/3] n_gsm: wake up ldisc tty before using it

From: Zhang Yanmin Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c

[PATCH V3 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in acm_tty_write

From: Zhang Yanmin acm device might be used as ldisc device by n_gsm driver. gsmtty_write and other gsm functions calls acm_tty_write indirectly while they holds spinlocks. Meanwhile, application might access ACM tty device directly. Here we choose to call usb_autopm_get_interface_upgrade

[PATCH V3 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

Resend as V1/V2 have email format issue. Sorry for bothering. I use Thunderbird. It has no a button to enable LKML email simply. :) V3: Change email config to resend. Add a space in comment. --- There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty.

Re: [PATCH V2 3/3] n_gsm: wake up ldisc tty before using it

On 2015/5/27 11:02, Greg KH wrote: > On Wed, May 27, 2015 at 10:50:01AM +0800, Zhang, Yanmin wrote: >> Wake up ldisc device before calling its driver to access the device. >> >> Signed-off-by: Zhang Yanmin >> >> --- >> >> drivers/tty/n_gsm.c | 40 +

[PATCH V2 3/3] n_gsm: wake up ldisc tty before using it

Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 2c34c32

[PATCH V2 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in acm_tty_write

of usb_autopm_get_interface_async to make sure above 2 scenarios can work well. Signed-off-by: Zhang Yanmin --- drivers/usb/class/cdc-acm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c index 5c8f581..6ad85a3 100644

[PATCH V2 1/3] usb: add function usb_autopm_get_interface_upgrade

, the function's caller need wake up the device before the function accesses the device. The patch adds usb_autopm_get_interface_upgrade, a new function to support above capability. Signed-off-by: Zhang Yanmin --- drivers/usb/core/driver.c | 54 +++ include

[PATCH V2 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

Resend as V1 has email format issue. Sorry for bothering. --- There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty. cdc-acm tty connects to xhci device. The application configures cdc-adm tty to n_gsm tty as ldisc tty. n_gsm=>cdc-acm=>xhci driver

Re: [PATCH 1/3] usb: add function usb_autopm_get_interface_upgrade

On 2015/5/26 22:12, Greg Kroah-Hartman wrote: On Tue, May 26, 2015 at 10:19:57AM +0800, Zhang, Yanmin wrote: Some usb driver has a specific requirement. Their critical functions might be called under both atomic environment and non-atomic environment. If it's under atomic environment

Re: [PATCH 1/3] usb: add function usb_autopm_get_interface_upgrade

On 2015/5/26 22:12, Greg Kroah-Hartman wrote: On Tue, May 26, 2015 at 10:19:57AM +0800, Zhang, Yanmin wrote: Some usb driver has a specific requirement. Their critical functions might be called under both atomic environment and non-atomic environment. If it's under atomic environment

[PATCH V2 1/3] usb: add function usb_autopm_get_interface_upgrade

, the function's caller need wake up the device before the function accesses the device. The patch adds usb_autopm_get_interface_upgrade, a new function to support above capability. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/usb/core/driver.c | 54

[PATCH V2 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

Resend as V1 has email format issue. Sorry for bothering. --- There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty. cdc-acm tty connects to xhci device. The application configures cdc-adm tty to n_gsm tty as ldisc tty. n_gsm=cdc-acm=xhci driver

[PATCH V2 3/3] n_gsm: wake up ldisc tty before using it

Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c

[PATCH V2 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in acm_tty_write

of usb_autopm_get_interface_async to make sure above 2 scenarios can work well. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/usb/class/cdc-acm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c index

Re: [PATCH V2 3/3] n_gsm: wake up ldisc tty before using it

On 2015/5/27 11:02, Greg KH wrote: On Wed, May 27, 2015 at 10:50:01AM +0800, Zhang, Yanmin wrote: Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/tty/n_gsm.c | 40

[PATCH V3 1/3] usb: add function usb_autopm_get_interface_upgrade

From: Zhang Yanmin yanmin.zh...@intel.com Some usb driver has a specific requirement. Their critical functions might be called under both atomic environment and non-atomic environment. If it's under atomic environment, the driver can wake up the device by calling pm_runtime_get_sync directly

[PATCH V3 3/3] n_gsm: wake up ldisc tty before using it

From: Zhang Yanmin yanmin.zh...@intel.com Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git

[PATCH V3 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in acm_tty_write

From: Zhang Yanmin yanmin.zh...@intel.com acm device might be used as ldisc device by n_gsm driver. gsmtty_write and other gsm functions calls acm_tty_write indirectly while they holds spinlocks. Meanwhile, application might access ACM tty device directly. Here we choose to call

[PATCH V3 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

Resend as V1/V2 have email format issue. Sorry for bothering. I use Thunderbird. It has no a button to enable LKML email simply. :) V3: Change email config to resend. Add a space in comment. --- There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty.

Re: [PATCH V3 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

On 2015/5/27 12:13, Zhang, Yanmin wrote: Resend as V1/V2 have email format issue. Sorry for bothering. Greg, We have to abandon this patchset. Zhuang Jin Can, a USB expert, reviewed the patches. He says acm_tty_write already considers it carefully. acm_tty_write puts the urb to a delayed queue

[PATCH 3/3] n_gsm: wake up ldisc tty before using it

Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index 2c34c32

[PATCH 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in, acm_tty_write

of usb_autopm_get_interface_async to make sure above 2 scenarios can work well. Signed-off-by: Zhang Yanmin --- --- drivers/usb/class/cdc-acm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c index 5c8f581..6ad85a3

[PATCH 1/3] usb: add function usb_autopm_get_interface_upgrade

, the function's caller need wake up the device before the function accesses the device. The patch adds usb_autopm_get_interface_upgrade, a new function to support above capability. Signed-off-by: Zhang Yanmin --- drivers/usb/core/driver.c | 53

[PATCH 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty. cdc-acm tty connects to xhci device. The application configures cdc-adm tty to n_gsm tty as ldisc tty. n_gsm=>cdc-acm=>xhci driver acm_tty_write can be called from n_gsm driver by ldisc connection,

[PATCH 3/3] n_gsm: wake up ldisc tty before using it

Wake up ldisc device before calling its driver to access the device. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/tty/n_gsm.c | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/tty/n_gsm.c b/drivers/tty

[PATCH 2/3] cdc-acm: call usb_autopm_get_interface_upgrade in, acm_tty_write

of usb_autopm_get_interface_async to make sure above 2 scenarios can work well. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- --- drivers/usb/class/cdc-acm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c

[PATCH 1/3] usb: add function usb_autopm_get_interface_upgrade

, the function's caller need wake up the device before the function accesses the device. The patch adds usb_autopm_get_interface_upgrade, a new function to support above capability. Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com --- drivers/usb/core/driver.c | 53

[PATCH 0/3] cdc-acm: fix incorrect runtime wakeup in acm_tty_write

There is a scenario about cdc-acm utilization.Application opens n_gsm tty and cdc-acm tty. cdc-acm tty connects to xhci device. The application configures cdc-adm tty to n_gsm tty as ldisc tty. n_gsm=cdc-acm=xhci driver acm_tty_write can be called from n_gsm driver by ldisc connection,

Re: [PATCH] debugfs: keep the old valid mode value when no explicity specify it

On 2014/8/28 23:10, Greg KH wrote: On Thu, Aug 28, 2014 at 06:09:09PM +0800, Chen LinX wrote: From: "Chen, LinX" When mount debugfs with no mode specifed after it's mounted, the mount point mode will change to default mode(0700) even the mount operation was fail, this will cause some issues

Re: [PATCH] debugfs: keep the old valid mode value when no explicity specify it

On 2014/8/28 23:10, Greg KH wrote: On Thu, Aug 28, 2014 at 06:09:09PM +0800, Chen LinX wrote: From: Chen, LinX linx.z.c...@intel.com When mount debugfs with no mode specifed after it's mounted, the mount point mode will change to default mode(0700) even the mount operation was fail, this will

Re: [PATCH] export the function kmap_flush_unused.

On 2014/8/11 19:54, Peter Zijlstra wrote: On Mon, Aug 11, 2014 at 01:26:45AM +, Sha, Ruibin wrote: Hi Chintan, Thank you very much for your timely and kindly response and comments. Here is more detail about our Scenario: We have a big driver on Android product. The driver allocates

Re: [PATCH] export the function kmap_flush_unused.

On 2014/8/11 19:54, Peter Zijlstra wrote: On Mon, Aug 11, 2014 at 01:26:45AM +, Sha, Ruibin wrote: Hi Chintan, Thank you very much for your timely and kindly response and comments. Here is more detail about our Scenario: We have a big driver on Android product. The driver allocates

Re: [PATCH] export the function kmap_flush_unused.

...@codeaurora.org] Sent: Friday, August 8, 2014 9:40 PM To: Sha, Ruibin Cc: linux-kernel@vger.kernel.org; linux...@kvack.org; m...@csn.ul.ie; a.p.zijls...@chello.nl; mgor...@suse.de; mi...@redhat.com; Zhang, Yanmin; He, Bo Subject: Re: [PATCH] export the function kmap_flush_unused. On 08/08/2014 02

Re: [PATCH] export the function kmap_flush_unused.

...@codeaurora.org] Sent: Friday, August 8, 2014 9:40 PM To: Sha, Ruibin Cc: linux-kernel@vger.kernel.org; linux...@kvack.org; m...@csn.ul.ie; a.p.zijls...@chello.nl; mgor...@suse.de; mi...@redhat.com; Zhang, Yanmin; He, Bo Subject: Re: [PATCH] export the function kmap_flush_unused. On 08/08/2014 02

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/24 1:14, Mikulas Patocka wrote: On Wed, 23 Jul 2014, Alasdair G Kergon wrote: On Wed, Jul 23, 2014 at 08:16:58AM -0400, Mikulas Patocka wrote: So, it means that you do not use device mapper at all. So, why are you trying to change memory allocation in device mapper? So the

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/24 1:14, Mikulas Patocka wrote: On Wed, 23 Jul 2014, Alasdair G Kergon wrote: On Wed, Jul 23, 2014 at 08:16:58AM -0400, Mikulas Patocka wrote: So, it means that you do not use device mapper at all. So, why are you trying to change memory allocation in device mapper? So the

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/22 10:04, Alasdair G Kergon wrote: On Tue, Jul 22, 2014 at 02:23:52AM +0100, Alasdair G Kergon wrote: Unanswered. Let's ask the same question in a different way: A quick search for 'vold' returns: https://android.googlesource.com/platform/system/vold/ and the code there

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/22 9:23, Alasdair G Kergon wrote: On 2014/7/9 6:39, Mikulas Patocka wrote: Which ioctl with more than 16kB arguments do you use? Unanswered. Let's ask the same question in a different way: Please supply the output of these three commands on the real-world system on which you

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/22 9:23, Alasdair G Kergon wrote: On 2014/7/9 6:39, Mikulas Patocka wrote: Which ioctl with more than 16kB arguments do you use? Unanswered. Let's ask the same question in a different way: Please supply the output of these three commands on the real-world system on which you

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/22 10:04, Alasdair G Kergon wrote: On Tue, Jul 22, 2014 at 02:23:52AM +0100, Alasdair G Kergon wrote: Unanswered. Let's ask the same question in a different way: A quick search for 'vold' returns: https://android.googlesource.com/platform/system/vold/ and the code there

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/9 22:53, Mikulas Patocka wrote: On Wed, 9 Jul 2014, Zhang, Yanmin wrote: On 2014/7/9 6:39, Mikulas Patocka wrote: Hi Mikulas, Thanks for your kind comments. I don't really know what is the purpose of this patch. In existing device mapper code, if kmalloc fails, the allocation

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/9 22:53, Mikulas Patocka wrote: On Wed, 9 Jul 2014, Zhang, Yanmin wrote: On 2014/7/9 6:39, Mikulas Patocka wrote: Hi Mikulas, Thanks for your kind comments. I don't really know what is the purpose of this patch. In existing device mapper code, if kmalloc fails, the allocation

Re: [PATCH] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

On 2014/7/14 21:27, Peter Zijlstra wrote: On Thu, Jul 03, 2014 at 11:36:38AM +0800, Chen LinX wrote: From: "Chen LinX" when do cpu hotplug test and run below perf test together, pmu may access freed perf_event while true; do perf record -a -g -f sleep 10 rm perf.* done the scenario is

Re: [PATCH] perf: Don't enable the perf_event without in PERF_ATTACH_CONTEXT status

On 2014/7/14 21:27, Peter Zijlstra wrote: On Thu, Jul 03, 2014 at 11:36:38AM +0800, Chen LinX wrote: From: Chen LinX linx.z.c...@intel.com when do cpu hotplug test and run below perf test together, pmu may access freed perf_event while true; do perf record -a -g -f sleep 10 rm perf.* done

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/9 6:39, Mikulas Patocka wrote: Hi Mikulas, Thanks for your kind comments. I don't really know what is the purpose of this patch. In existing device mapper code, if kmalloc fails, the allocation is retried with __vmalloc. So there is no need to avoid kmalloc aritifically. kmalloc

Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params

On 2014/7/9 6:39, Mikulas Patocka wrote: Hi Mikulas, Thanks for your kind comments. I don't really know what is the purpose of this patch. In existing device mapper code, if kmalloc fails, the allocation is retried with __vmalloc. So there is no need to avoid kmalloc aritifically. kmalloc

Re: Should Pstore(ramoops) records customized information?

On 2014/6/27 20:06, Liu hua wrote: 于 2014/6/26 8:57, Zhang, Yanmin 写道: On 2014/6/25 21:08, Liu hua wrote: 于 2014/6/25 8:41, Zhang, Yanmin 写道: On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that "extern struct pstore_info *psinfo" locates in

Re: Should Pstore(ramoops) records customized information?

On 2014/6/27 20:06, Liu hua wrote: 于 2014/6/26 8:57, Zhang, Yanmin 写道: On 2014/6/25 21:08, Liu hua wrote: 于 2014/6/25 8:41, Zhang, Yanmin 写道: On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that extern struct pstore_info *psinfo locates in fs/pstore

Re: Should Pstore(ramoops) records customized information?

On 2014/6/25 21:08, Liu hua wrote: 于 2014/6/25 8:41, Zhang, Yanmin 写道: On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that "extern struct pstore_info *psinfo" locates in fs/pstore/internal.h. So users out of directory "fs/pstore/"

Re: Should Pstore(ramoops) records customized information?

On 2014/6/25 21:08, Liu hua wrote: 于 2014/6/25 8:41, Zhang, Yanmin 写道: On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that extern struct pstore_info *psinfo locates in fs/pstore/internal.h. So users out of directory fs/pstore/ can not use pstore

Re: Should Pstore(ramoops) records customized information?

On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that "extern struct pstore_info *psinfo" locates in fs/pstore/internal.h. So users out of directory "fs/pstore/" can not use pstore to record messages. We do not want other kernel users to use pstore, right?

Re: Should Pstore(ramoops) records customized information?

On 2014/6/20 18:47, Liu hua wrote: On 2014/6/20 7:42, Luck, Tony wrote: BTW, I note that extern struct pstore_info *psinfo locates in fs/pstore/internal.h. So users out of directory fs/pstore/ can not use pstore to record messages. We do not want other kernel users to use pstore, right? And

Re: [PATCH] perf: fix kernel panic when parsing user space CS saved in pt_regs

On 2014/6/5 17:15, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 04:00:24PM +0800, Zhang, Yanmin wrote: On 2014/6/5 15:55, Peter Zijlstra wrote: Why does pstore cause corruption? I thought that stuff was supposed to be 'good' ? pstore is good if the board is reset by WarmReset as memory

Re: [PATCH] perf: fix kernel panic when parsing user space CS saved in pt_regs

On 2014/6/5 15:55, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 03:33:21PM +0800, Liu ShuoX wrote: On Thu 5.Jun'14 at 9:19:19 +0200, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 10:36:10AM +0800, Liu ShuoX wrote: From: Zhang Yanmin We hit a kernel panic when running perf to collect some

Re: [PATCH] perf: fix kernel panic when parsing user space CS saved in pt_regs

On 2014/6/5 15:55, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 03:33:21PM +0800, Liu ShuoX wrote: On Thu 5.Jun'14 at 9:19:19 +0200, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 10:36:10AM +0800, Liu ShuoX wrote: From: Zhang Yanmin yanmin.zh...@intel.com We hit a kernel panic when

Re: [PATCH] perf: fix kernel panic when parsing user space CS saved in pt_regs

On 2014/6/5 17:15, Peter Zijlstra wrote: On Thu, Jun 05, 2014 at 04:00:24PM +0800, Zhang, Yanmin wrote: On 2014/6/5 15:55, Peter Zijlstra wrote: Why does pstore cause corruption? I thought that stuff was supposed to be 'good' ? pstore is good if the board is reset by WarmReset as memory

RE: linux-next: build failure after merge of the ia64 tree

Sorry. We would fix it ASAP. Yanmin -Original Message- From: Stephen Rothwell [mailto:s...@canb.auug.org.au] Sent: Monday, March 31, 2014 8:08 AM To: Luck, Tony Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Liu, ShuoX; Zhang, Yanmin Subject: linux-next: build failure

RE: linux-next: build failure after merge of the ia64 tree

Sorry. We would fix it ASAP. Yanmin -Original Message- From: Stephen Rothwell [mailto:s...@canb.auug.org.au] Sent: Monday, March 31, 2014 8:08 AM To: Luck, Tony Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; Liu, ShuoX; Zhang, Yanmin Subject: linux-next: build failure

Re: [PATCH] pstore: skip zero size persistent ram buffer in traverse

On 2014/2/28 14:38, shuox@intel.com wrote: From: Liu ShuoX In ramoops_pstore_read, a valid prz pointer with zero size buffer will break traverse of all persistent ram buffers. The latter buffer might be lost. Andrew, Would you like to merge it to your testing tree? pstore is a very

Re: [PATCH] pstore: reset ftrace_read_cnt at ramoops_pstore_open

On 2014/2/28 14:37, shuox@intel.com wrote: From: Liu ShuoX ftrace_read_cnt need to be reset in open to support mutli times getting the records. Andrew, Would you like to merge it to your testing tree? pstore is a very important feature for debugging hard issues on Android mobiles.

Re: [PATCH] pstore: reset ftrace_read_cnt at ramoops_pstore_open

On 2014/2/28 14:37, shuox@intel.com wrote: From: Liu ShuoX shuox@intel.com ftrace_read_cnt need to be reset in open to support mutli times getting the records. Andrew, Would you like to merge it to your testing tree? pstore is a very important feature for debugging hard issues on

Re: [PATCH] pstore: skip zero size persistent ram buffer in traverse

On 2014/2/28 14:38, shuox@intel.com wrote: From: Liu ShuoX shuox@intel.com In ramoops_pstore_read, a valid prz pointer with zero size buffer will break traverse of all persistent ram buffers. The latter buffer might be lost. Andrew, Would you like to merge it to your testing tree?

RE: [PATCH] klist: del waiter from klist_remove_waiters before wakeup waitting process

Andrew, Would you like to merge the patch to your MM tree? Yanmin >-Original Message- >From: Peter Zijlstra [mailto:pet...@infradead.org] >Sent: Friday, May 03, 2013 6:42 PM >To: Wang, Biao >Cc: a...@linux-foundation.org; linux-kernel@vger.kernel.org; >mi...@redhat.

RE: [PATCH] hrtimer:__run_hrtimer races with enqueue_hrtimer

>-Original Message- >From: Thomas Gleixner [mailto:t...@linutronix.de] >Sent: Friday, October 26, 2012 5:55 PM >To: He, Bo >Cc: linux-kernel@vger.kernel.org; Peter Zijlstra; Ingo Molnar; >yanmin_zh...@linux.intel.com; Zhang, Yanmin >Subject: Re: [PATCH] hrtime

RE: [PATCH] hrtimer:__run_hrtimer races with enqueue_hrtimer

-Original Message- From: Thomas Gleixner [mailto:t...@linutronix.de] Sent: Friday, October 26, 2012 5:55 PM To: He, Bo Cc: linux-kernel@vger.kernel.org; Peter Zijlstra; Ingo Molnar; yanmin_zh...@linux.intel.com; Zhang, Yanmin Subject: Re: [PATCH] hrtimer:__run_hrtimer races

RE: Why hold device_lock when calling callback in pci_walk_bus?

...@google.com Cc: Greg Kroah-Hartman; Zhang, Yanmin; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; r...@sisk.pl Subject: Why hold device_lock when calling callback in pci_walk_bus? Hi, All, If my understanding were correct, device_lock is used to provide mutual exclusion between device

RE: Why hold device_lock when calling callback in pci_walk_bus?

...@google.com Cc: Greg Kroah-Hartman; Zhang, Yanmin; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; r...@sisk.pl Subject: Why hold device_lock when calling callback in pci_walk_bus? Hi, All, If my understanding were correct, device_lock is used to provide mutual exclusion between device

Re: tbench regression in 2.6.25-rc1

Valdis, and David! Signed-off-by: Zhang Yanmin <[EMAIL PROTECTED]> Acked-by: Eric Dumazet <[EMAIL PROTECTED]> --- --- linux-2.6.25-rc1/include/net/dst.h 2008-02-21 14:33:43.0 +0800 +++ linux-2.6.25-rc1_work/include/net/dst.h 2008-02-22 12:52:19.0 +0800 @@ -52,15 +52,10 @

Re: tbench regression in 2.6.25-rc1

, and David! Signed-off-by: Zhang Yanmin [EMAIL PROTECTED] Acked-by: Eric Dumazet [EMAIL PROTECTED] --- --- linux-2.6.25-rc1/include/net/dst.h 2008-02-21 14:33:43.0 +0800 +++ linux-2.6.25-rc1_work/include/net/dst.h 2008-02-22 12:52:19.0 +0800 @@ -52,15 +52,10 @@ struct dst_entry

Re: tbench regression in 2.6.25-rc1

On Tue, 2008-02-19 at 08:40 +0100, Eric Dumazet wrote: > Zhang, Yanmin a �crit : > > On Mon, 2008-02-18 at 12:33 -0500, [EMAIL PROTECTED] wrote: > >> On Mon, 18 Feb 2008 16:12:38 +0800, "Zhang, Yanmin" said: > >> > >>> I also think __r

  1   2   3   >