netdev - Re: sblk->status_tag on drivers/net/ethernet/broadcom/tg3.c

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: <1394002230.4632.28.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
Date:	Tue, 4 Mar 2014 22:50:30 -0800
From:	Michael Chan <mchan@...adcom.com>
To:	Jagan Teki <jagannadh.teki@...il.com>
CC:	<netdev@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Nithin Nayak Sujir <nsujir@...adcom.com>,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: sblk->status_tag on drivers/net/ethernet/broadcom/tg3.c

On Wed, 2014-03-05 at 11:43 +0530, Jagan Teki wrote: 
> As per your point I've a question here like - the status block is not properly
> updated (DMA'ed), does this depends on the address range we are advertised
> on PCIe ranges filed to make sure to use EP-
> http://devicetree.org/Device_Tree_Usage#PCI_Host_Bridge 

The status block is in host memory (CPU memory).  This memory is
allocated by the driver.  The DMA address of the status block is then
programmed into the NIC register HOSTCC_STATUS_BLK_HOST_ADDR so that the
NIC knows where to DMA the status block.  When there is an event, the
NIC DMAs a new status block and then generates IRQ.

The status block is not in PCI memory.  PCI memory is where the
registers are mapped.  Hope this helps.

--
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