Re: [PATCH] EDAC/dummy: Add a dummy EDAC driver

[Borislav Petkov]

On Thu, Jul 30, 2026 at 04:55:45PM -0400, Yazen Ghannam wrote:
> There can be module parameters to describe the layers and their types.
> 
> Examples:
>  layer0=all
>  layer0=channel layer1=slot
>  layer0=slot layer1=channel layer2=chip_select
> 
> With this, we could test all the permutations of enumerating the EDAC
> sysfs interface.

Patches are welcome! :-)

But yes, the basic idea is to use this for testing the EDAC subsystem and in
a VM for drivers where I don't have access to the HW (and I don't want to have
access to... :-)).

> > +config EDAC_DUMMY
> > +	tristate "Dummy EDAC driver"
> > +	default n
> > +	help
> > +	  A dummy EDAC driver is useful for testing purposes in a VM when one
> > +	  doesn't have all the hardware needed to test aspects of the EDAC
> > +	  subsystem code.
> 
> This is verbatim the commit message.

Yes, sometimes one doesn't need to talk too much. :-)

> > +/*
> > + * Simulated "error syndrome". In real hardware drivers this would be
> > + * read out of a per-CPU system/MMIO register. Here userspace (via
> > + * debugfs) or nothing at all drives it, which is exactly the point:
> > + * the driver has no dependency on any physical error source.
> 
> This needs revision.

Revision?

> I find this approach helps clean up the first draft. And it seems easier
> to make minor adjustments as you go along.

Maybe.

Frankly, my experience currently is AI is getting more and more in the way.
I'm faster doing it myself instead of talking to a LLM. For review it is fine
I guess.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette