[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60834BF8295536D1C6CE5C13FCD7A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Wed, 19 Nov 2025 17:31:15 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>, "Lai, Yi1" <yi1.lai@...el.com>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 4/7] EDAC/{skx_common,imh}: Add EDAC driver for Intel
Diamond Rapids servers
> So is adding the new functionality going to make the old one ugly enough to
> warrant the clean slate?
Yes.
> Is the integrated memory/IO hub the new thing that is
> going to be done going forward?
The next CPU generation will definitely do the same thing. After that
my crystal ball is too hazy :-(
> It doesn't get clear to me from the history (parts of which I remember too,
> btw. :))
>
> Don't get me wrong - you're going to end up maintaining all this so I'm just
> playing the devil's advocate here.
Understood.
-Tony
Powered by blists - more mailing lists