Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Tue, Apr 03, 2018 at 08:43:27AM +0300, Alex Vesker wrote: > > > On 4/2/2018 12:12 PM, Jiri Pirko wrote: > >Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: > >>>Please see: > >>>http://patchwork.ozlabs.org/project/netdev/list/?series=36524 > >>> > >>>I bevieve that the solution in

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Tue, Apr 03, 2018 at 08:43:27AM +0300, Alex Vesker wrote: > > > On 4/2/2018 12:12 PM, Jiri Pirko wrote: > >Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: > >>>Please see: > >>>http://patchwork.ozlabs.org/project/netdev/list/?series=36524 > >>> > >>>I bevieve that the solution in

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Mon, Apr 02, 2018 at 02:30:45PM CEST, rahul.lakkire...@chelsio.com wrote: >On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: >> Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: >> >Rahul Lakkireddy writes: >> > >> >> On Friday,

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Mon, Apr 02, 2018 at 02:30:45PM CEST, rahul.lakkire...@chelsio.com wrote: >On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: >> Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: >> >Rahul Lakkireddy writes: >> > >> >> On Friday, March 03/30/18, 2018 at 16:09:07

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On 4/2/2018 12:12 PM, Jiri Pirko wrote: Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: Please see: http://patchwork.ozlabs.org/project/netdev/list/?series=36524 I bevieve that the solution in the patchset could be used for your usecase too. Hi Jiri

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On 4/2/2018 12:12 PM, Jiri Pirko wrote: Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: Please see: http://patchwork.ozlabs.org/project/netdev/list/?series=36524 I bevieve that the solution in the patchset could be used for your usecase too. Hi Jiri

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: > Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: > >Rahul Lakkireddy writes: > > > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > >>> Sat, Mar 24, 2018

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: > Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: > >Rahul Lakkireddy writes: > > > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > >>> Sat, Mar 24, 2018 at 11:56:33AM CET,

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

> >> The sysfs approach proposed here had been dropped in favour exporting > >> the dumps as ELF notes in /proc/vmcore. > >> > >> Will be posting the new patches soon. > > > >The concern was actually how you identify which device that came from. > >Where you read the identifier changes but sysfs

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

> >> The sysfs approach proposed here had been dropped in favour exporting > >> the dumps as ELF notes in /proc/vmcore. > >> > >> Will be posting the new patches soon. > > > >The concern was actually how you identify which device that came from. > >Where you read the identifier changes but sysfs

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: >> Please see: >> http://patchwork.ozlabs.org/project/netdev/list/?series=36524 >> >> I bevieve that the solution in the patchset could be used for >> your usecase too. > >Hi Jiri > >https://lkml.org/lkml/2018/3/20/436 > >How well does

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Fri, Mar 30, 2018 at 05:11:29PM CEST, and...@lunn.ch wrote: >> Please see: >> http://patchwork.ozlabs.org/project/netdev/list/?series=36524 >> >> I bevieve that the solution in the patchset could be used for >> your usecase too. > >Hi Jiri > >https://lkml.org/lkml/2018/3/20/436 > >How well does

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: >Rahul Lakkireddy writes: > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: >>> Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >>> >Add a new module

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: >Rahul Lakkireddy writes: > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: >>> Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >>> >Add a new module crashdd that exports the

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Rahul Lakkireddy writes: > On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: >> Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >> >Add a new module crashdd that exports the /sys/kernel/crashdd/ >> >directory in second

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Rahul Lakkireddy writes: > On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: >> Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >> >Add a new module crashdd that exports the /sys/kernel/crashdd/ >> >directory in second kernel, containing collected

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

> Please see: > http://patchwork.ozlabs.org/project/netdev/list/?series=36524 > > I bevieve that the solution in the patchset could be used for > your usecase too. Hi Jiri https://lkml.org/lkml/2018/3/20/436 How well does this API work for a 2Gbyte snapshot? Andrew

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

> Please see: > http://patchwork.ozlabs.org/project/netdev/list/?series=36524 > > I bevieve that the solution in the patchset could be used for > your usecase too. Hi Jiri https://lkml.org/lkml/2018/3/20/436 How well does this API work for a 2Gbyte snapshot? Andrew

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: > >Add a new module crashdd that exports the /sys/kernel/crashdd/ > >directory in second kernel, containing collected hardware/firmware > >dumps. > > >

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: > >Add a new module crashdd that exports the /sys/kernel/crashdd/ > >directory in second kernel, containing collected hardware/firmware > >dumps. > > >

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >Add a new module crashdd that exports the /sys/kernel/crashdd/ >directory in second kernel, containing collected hardware/firmware >dumps. > >The sequence of actions done by device drivers to append their device >specific

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Sat, Mar 24, 2018 at 11:56:33AM CET, rahul.lakkire...@chelsio.com wrote: >Add a new module crashdd that exports the /sys/kernel/crashdd/ >directory in second kernel, containing collected hardware/firmware >dumps. > >The sequence of actions done by device drivers to append their device >specific

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Hi Rahul, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Rahul-Lakkireddy/fs-crashdd-add-API-to-collect-hardware-dump-in-second-kernel/20180325-191308 config: i386-randconfig-s0-03251817

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Hi Rahul, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Rahul-Lakkireddy/fs-crashdd-add-API-to-collect-hardware-dump-in-second-kernel/20180325-191308 config: i386-randconfig-s0-03251817

[PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Add a new module crashdd that exports the /sys/kernel/crashdd/ directory in second kernel, containing collected hardware/firmware dumps. The sequence of actions done by device drivers to append their device specific hardware/firmware logs to /sys/kernel/crashdd/ directory are as follows: 1.

[PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

Add a new module crashdd that exports the /sys/kernel/crashdd/ directory in second kernel, containing collected hardware/firmware dumps. The sequence of actions done by device drivers to append their device specific hardware/firmware logs to /sys/kernel/crashdd/ directory are as follows: 1.