On 04/09/2014 07:47 PM, Borislav Petkov wrote: > On Wed, Apr 09, 2014 at 10:59:49PM +0530, Punnaiah Choudary wrote: >> There is a driver file cache-l2x0.c under arch/arm/mm for pl310 cache >> configuration and management. Russel king had suggested to use >> single driver file for both pl310 edac implementation and cache-l2x0.c >> Here is the thread >> http://www.spinics.net/lists/arm-kernel/msg320407.html >> >> please provide your inputs > > Well, it is very simple - you don't really need an EDAC compilation unit > just so that you can report errors - you can very well do that in your > cache-l2x0.c and boom, problem solved. > > Simply move the irq handler and the parity error checker to that file. I am just curious about this recommendation. Does it mean that we shouldn't use edac interface just for reporting problems? I didn't play with it but I guess that there is a record about edac driver via sysfs, etc. You could read some useful information that you know what it is protected and I hope that edac interface bring any value to reporting errors comparing to just printk message from IRQ handler. My question is if using printk in IRQ handler and report problem is equal to reporting this via edac interface. Or it is just easy way to do but using edac interface is right solution and how to do it properly is different question. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
Attachment:
signature.asc
Description: OpenPGP digital signature
