netdev - Re: [NET_NEXT RFC PATCH 3/3] ixgbe: added reg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120509205459.4939c98d@s6510.linuxnetplumber.net>
Date:	Wed, 9 May 2012 20:54:59 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	Catherine Sullivan <catherine.sullivan@...el.com>,
	<netdev@...r.kernel.org>
Subject: Re: [NET_NEXT RFC PATCH 3/3] ixgbe: added reg_ops file to debugfs

On Thu, 10 May 2012 01:18:10 +0100
Ben Hutchings <bhutchings@...arflare.com> wrote:

> On Wed, 2012-05-09 at 16:14 -0700, Stephen Hemminger wrote:
> > On Wed, 09 May 2012 16:09:50 -0700
> > Catherine Sullivan <catherine.sullivan@...el.com> wrote:
> > 
> > > Added the reg_ops file to debugfs with commands to read and write
> > > a register to give users the ability to read and write individual
> > > registers on the fly.
> > > 
> > > Signed-off-by: Catherine Sullivan <catherine.sullivan@...el.com>
> > > ---
> > > 
> > >  drivers/net/ethernet/intel/ixgbe/ixgbe_debugfs.c |  112 ++++++++++++++++++++++
> > >  1 files changed, 112 insertions(+), 0 deletions(-)
> > > 
> > 
> > Aren't these registers already in ethtool?
> 
> ethtool register access is read-only and would be very heavy-weight for
> interactive debugging.  Not sure this is the best interface to
> read/write registers, but it's certainly not redundant.

For debugging couldn't you could mmap the PCI  space? That would allow writing
a user level debugger for the hardware.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html