RE: qed*: debug infrastructures

2017-04-26 Thread Elior, Ariel
Jiri, Florian, Jakub, Thanks all for you suggestions. Some answers to questions posted: The signal tracing in our device can be used for tracing things like load/store/program_counter from our fastpath processors (which handle every packet) which can then be re-run in a simulative environment

Re: qed*: debug infrastructures

2017-04-25 Thread Florian Fainelli
On 04/24/2017 10:38 AM, Elior, Ariel wrote: > Hi Dave, > > According to the recent messages on the list indicating debugfs is not the way > to go, I am looking for some guidance on what is. dpipe approach was > mentioned as favorable, but I wanted to make sure molding our debug features > to >

Re: qed*: debug infrastructures

2017-04-25 Thread Jiri Pirko
Tue, Apr 25, 2017 at 05:44:10AM CEST, kubak...@wp.pl wrote: >On Mon, 24 Apr 2017 17:38:57 +, Elior, Ariel wrote: >> Hi Dave, > >Hi Ariel! > >I'm not Dave but let me share my perspective :) > >> According to the recent messages on the list indicating debugfs is not the >> way >> to go, I am

Re: qed*: debug infrastructures

2017-04-24 Thread Jakub Kicinski
On Mon, 24 Apr 2017 17:38:57 +, Elior, Ariel wrote: > Hi Dave, Hi Ariel! I'm not Dave but let me share my perspective :) > According to the recent messages on the list indicating debugfs is not the way > to go, I am looking for some guidance on what is. dpipe approach was > mentioned as

qed*: debug infrastructures

2017-04-24 Thread Elior, Ariel
Hi Dave, According to the recent messages on the list indicating debugfs is not the way to go, I am looking for some guidance on what is. dpipe approach was mentioned as favorable, but I wanted to make sure molding our debug features to this infrastructure will result in something acceptable. A