From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752263AbdBTJor (ORCPT ); Mon, 20 Feb 2017 04:44:47 -0500 Received: from mx2.suse.de ([195.135.220.15]:52716 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072AbdBTJop (ORCPT ); Mon, 20 Feb 2017 04:44:45 -0500 Date: Mon, 20 Feb 2017 10:44:19 +0100 From: Borislav Petkov To: "Huang, Ying" Cc: "Rafael J . Wysocki" , Len Brown , Tomasz Nowicki , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH -v2] ACPI, APEI: Fix BERT resources conflict with ACPI NVS area Message-ID: <20170220094419.j6effubsn7qct55q@pd.tnic> References: <20170220011343.6736-1-ying.huang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170220011343.6736-1-ying.huang@intel.com> User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 20, 2017 at 09:12:58AM +0800, Huang, Ying wrote: > From: Huang Ying > > It was reported that on some machines, there is overlap between ACPI > NVS area and BERT address range. This appears reasonable because BERT > contents need to be non-volatile across reboot. But this will cause > resources conflict in current Linux kernel implementation because the > ACPI NVS area is marked as busy. The resource conflict is fixed via > excluding the ACPI NVS area when requesting IO resources for BERT. > When accessing the BERT contents, the whole BERT address range will be > ioremapped and accessed. > > Reported-and-tested-by: Hans Kristian Rosbach > Signed-off-by: "Huang, Ying" > --- > drivers/acpi/apei/bert.c | 20 ++++++++++++-------- > 1 file changed, 12 insertions(+), 8 deletions(-) Acked-by: Borislav Petkov -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --