From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BCF4120D4F6 for ; Thu, 23 Jan 2025 09:56:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737626216; cv=none; b=emj51/ZqnX7xLQZtVNdcYh5+vq+H2DdurzbVP+LTWMdn4MZxUlvBefmG6mBsfY+Jjk4cUpKDcK4DiZAfVCg6kprveHyd/TpQErAqWRv2Q7g/8JZPzMv4kDulFK+9wPlcoSMU+z52lhC4Kgg9ZV+ov7EVR6+vGutU5+nLnsw4I+w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737626216; c=relaxed/simple; bh=FBDPDLQBba1NKXHTUdji4zwB2ZwPfwVfpvm6Nk3j/p4=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=utDGxe8RWuGS0i7SzEod7AyMgEsNRxGKoQ7bzibgieCCSsk1AKzwACQUmCO7ZMEr9emFf6yZFHhQCmTjI2SzrpOKJmO7dILvJiaJVfH/3U7YZzhfuCv4mBqaeLVK6Q1fjjwefrMnwcp/IEHdVcg2a2KLS82jQbMB+cWnXSPLlMk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4YdxDJ1WVxz6K9N4; Thu, 23 Jan 2025 17:56:32 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 8E128140A70; Thu, 23 Jan 2025 17:56:50 +0800 (CST) Received: from localhost (10.203.177.66) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 23 Jan 2025 10:56:50 +0100 Date: Thu, 23 Jan 2025 09:56:48 +0000 From: Jonathan Cameron To: Mauro Carvalho Chehab CC: Igor Mammedov , "Michael S . Tsirkin" , Shiju Jose , , , Ani Sinha , Dongjiu Geng , Peter Maydell , "Shannon Zhao" , Subject: Re: [PATCH 01/11] acpi/ghes: Prepare to support multiple sources on ghes Message-ID: <20250123095648.000063a5@huawei.com> In-Reply-To: <781c65c9188c4649821885a62b6f6370ff7874d2.1737560101.git.mchehab+huawei@kernel.org> References: <781c65c9188c4649821885a62b6f6370ff7874d2.1737560101.git.mchehab+huawei@kernel.org> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml100004.china.huawei.com (7.191.162.219) To frapeml500008.china.huawei.com (7.182.85.71) On Wed, 22 Jan 2025 16:46:18 +0100 Mauro Carvalho Chehab wrote: > The current code is actually dependent on having just one error > structure with a single source. > > As the number of sources should be arch-dependent, as it will depend on > what kind of synchronous/assynchronous notifications will exist, change asynchronous. > the logic to dynamically build the table. > > Yet, for a proper support, we need to get the number of sources by > reading the number from the HEST table. However, bios currently doesn't > store a pointer to it. > > For now just change the logic at table build time, while enforcing that > it will behave like before with a single source ID. > > A future patch will add a HEST table bios pointer and change the logic > at acpi_ghes_record_errors() to dynamically use the new size. > > Signed-off-by: Mauro Carvalho Chehab > Reviewed-by: Jonathan Cameron