From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Luck, Tony" Date: Thu, 29 May 2003 21:47:34 +0000 Subject: RE: [Linux-ia64] SAL error record logging/decoding Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org So some SAL records are platform related, and some are tied to a specific CPU. And different SAL implementations might fuzz the issue further by making cpu dependent records visible at the platform level. Stepping back from this (a few miles) for a broader view. What benefit do we gain at the application level by making all the mca/init/cmci/cpei files visible on a per-cpu basis? For platform level errors, this just causes confusion as the same record is definitely available on all cpus. But if your application is "poll"ing all the files, only one needs to read&clear. For cpu-level errors (assuming that a SAL implementation keeps them in separate queues) ... I'm not certain why the application needs to be able to read from a cpu-spcific file. If all the error records were funneled into a single file, would we lose anything? -Tony