Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6694464ybe; Wed, 18 Sep 2019 07:36:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqy2C0oyvQA+k/dQ2OHrM4Yirmr+UWyxYrkJIXJMkWagpefKFVMwEiRk4SKnm4fQGbuHZNHI X-Received: by 2002:a17:906:8054:: with SMTP id x20mr4921196ejw.65.1568817402503; Wed, 18 Sep 2019 07:36:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568817402; cv=none; d=google.com; s=arc-20160816; b=FH+m8kyuzpOFKRXhQUG8R5oYJUe09LIuw9CLeylfy7D0ptnIngctDieNUbUVX5HRiA hj+FaQbSExIr4N3m9871MupygSBAmQ8s473E1zqK9UX+USEwMqfaL+G5s7Eoei/PDPLM 6G8ohW6Q3hM5zZ7Tpk6dpbMOCZ6Ys9yXWqh+uihr1ntnxhcHOn33iqopU6kEHzTGFZyI 97xLAjQ7/YiLpfx8QBd3zt9h6yYX3xTXS1WZ5flX9ax/l9ZPbECDbeFWZhAH++R5L553 G/JqbZiWeQifcdKUfrYxczcp+RhSChgXE7dswx6mzC1WKVbcV+/e0dKoYW55gpbQpcYG Bwsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=1RgJVbQsYkN/qauahaNK+HJj92fbfDBACgG0bFF+Cqs=; b=LRBPCo72JOykAY6aw9fNgVcntTich46zjWQInsOy+/mvvkUIyTbPt66iOFw3DM4w9f BAoIsApmq/ypOSgXRMJA7egcRNzzNlGyz/3idu9uA+/XH4y6NHsbfMulKfPmEt3mXtdK CuQS6zPDCeSFfsj515FVhZqKkPMWrI5atG0SyvDn19LIyco55hBQrToafj7B+tCsOwQ/ cOxhplnuDmp1SEKCHZKV++bQ5zOHDeF2wLqUHZFVOV8PiCdFLMwVTn9UAuYLpr3rmBkt s84cus33MjxNw+4QKE1/EgR+nmq9gyqk8cNS3eUVoA+n4JBzdSPLCO6cfwrmzol9lhys Z9eg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k9si2788164ejj.256.2019.09.18.07.36.18; Wed, 18 Sep 2019 07:36:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731103AbfIRObr (ORCPT + 99 others); Wed, 18 Sep 2019 10:31:47 -0400 Received: from mail.steuer-voss.de ([85.183.69.95]:49270 "EHLO mail.steuer-voss.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730457AbfIRObq (ORCPT ); Wed, 18 Sep 2019 10:31:46 -0400 X-Virus-Scanned: Debian amavisd-new at mail.steuer-voss.de Received: by mail.steuer-voss.de (Postfix, from userid 1000) id 24F1D482F9; Wed, 18 Sep 2019 16:31:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.steuer-voss.de (Postfix) with ESMTP id 1F14B482F6; Wed, 18 Sep 2019 16:31:43 +0200 (CEST) Date: Wed, 18 Sep 2019 16:31:43 +0200 (CEST) From: Nikolaus Voss X-X-Sender: nv@fox.voss.local To: "Moore, Robert" cc: Ferry Toth , "Shevchenko, Andriy" , "Schmauss, Erik" , "Rafael J. Wysocki" , Len Brown , Jacek Anaszewski , Pavel Machek , Dan Murphy , "linux-acpi@vger.kernel.org" , "devel@acpica.org" , "linux-kernel@vger.kernel.org" , Jan Kiszka Subject: RE: [PATCH] ACPICA: make acpi_load_table() return table index In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E3B968327D@ORSMSX110.amr.corp.intel.com> Message-ID: References: <20190906174605.GY2680@smile.fi.intel.com> <20190912080742.24642-1-nikolaus.voss@loewensteinmedical.de> <94F2FBAB4432B54E8AACC7DFDE6C92E3B9679CE8@ORSMSX110.amr.corp.intel.com> <94F2FBAB4432B54E8AACC7DFDE6C92E3B967ADF6@ORSMSX110.amr.corp.intel.com> <20190913151228.GT2680@smile.fi.intel.com> <7625fe37-1710-056d-fb9e-39c33fd962a1@gmail.com> <94F2FBAB4432B54E8AACC7DFDE6C92E3B967AEC9@ORSMSX110.amr.corp.intel.com> <94F2FBAB4432B54E8AACC7DFDE6C92E3B968327D@ORSMSX110.amr.corp.intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Sep 2019, Moore, Robert wrote: > > > -----Original Message----- > From: Nikolaus Voss [mailto:nv@vosn.de] > Sent: Monday, September 16, 2019 2:47 AM > To: Moore, Robert > Cc: Ferry Toth ; Shevchenko, Andriy ; Schmauss, Erik ; Rafael J. Wysocki ; Len Brown ; Jacek Anaszewski ; Pavel Machek ; Dan Murphy ; linux-acpi@vger.kernel.org; devel@acpica.org; linux-kernel@vger.kernel.org; Jan Kiszka > Subject: RE: [PATCH] ACPICA: make acpi_load_table() return table index > > On Fri, 13 Sep 2019, Moore, Robert wrote: >> >> >> -----Original Message----- >> From: Ferry Toth [mailto:fntoth@gmail.com] >> Sent: Friday, September 13, 2019 9:48 AM >> To: Shevchenko, Andriy ; Moore, Robert >> >> Cc: Nikolaus Voss ; Schmauss, Erik >> ; Rafael J. Wysocki ; Len >> Brown ; Jacek Anaszewski >> ; Pavel Machek ; Dan Murphy >> ; linux-acpi@vger.kernel.org; devel@acpica.org; >> linux-kernel@vger.kernel.org; nikolaus.voss@loewensteinmedical.de; Jan >> Kiszka >> Subject: Re: [PATCH] ACPICA: make acpi_load_table() return table index >> >> Hello all, >> >> Sorry to have sent our message with cancelled e-mail address. I have correct this now. >> >> Op 13-09-19 om 17:12 schreef Shevchenko, Andriy: >>> On Fri, Sep 13, 2019 at 05:20:21PM +0300, Moore, Robert wrote: >>>> -----Original Message----- >>>> From: Nikolaus Voss [mailto:nv@vosn.de] >>>> Sent: Friday, September 13, 2019 12:44 AM >>>> To: Moore, Robert >>>> Cc: Shevchenko, Andriy ; Schmauss, Erik >>>> ; Rafael J. Wysocki ; >>>> Len Brown ; Jacek Anaszewski >>>> ; Pavel Machek ; Dan >>>> Murphy ; linux-acpi@vger.kernel.org; >>>> devel@acpica.org; linux-kernel@vger.kernel.org; Ferry Toth >>>> ; nikolaus.voss@loewensteinmedical.de >>>> Subject: RE: [PATCH] ACPICA: make acpi_load_table() return table >>>> index >>>> >>>> Bob, >>>> >>>> On Thu, 12 Sep 2019, Moore, Robert wrote: >>>>> The ability to unload an ACPI table (especially AML tables such as >>>>> SSDTs) is in the process of being deprecated in ACPICA -- since it >>>>> is also deprecated in the current ACPI specification. This is being >>>>> done because of the difficulty of deleting the namespace entries >>>>> for the table. FYI, Windows does not properly support this function either. >>>> >>>> ok, I see it can be a problem to unload an AML table with all it's >>>> consequences e.g. with respect to driver unregistering in setups >>>> with complex dependencies. It will only work properly under certain >>>> conditions >>>> - nevertheless acpi_tb_unload_table() is still exported in ACPICA and we should get this working as it worked before. >>>> >>>> AcpiTbUnloadTable is not exported, it is an internal interface only >>>> -- as recognized by the "AcpiTb". >>> >>> In Linux it became a part of ABI when the >>> >>> commit 772bf1e2878ecfca0d1f332071c83e021dd9cf01 >>> Author: Jan Kiszka >>> Date: Fri Jun 9 20:36:31 2017 +0200 >>> >>> ACPI: configfs: Unload SSDT on configfs entry removal >>> >>> appeared in the kernel. >> >> And the commit message explains quite well why it is an important feature: >> >> "This allows to change SSDTs without rebooting the system. >> It also allows to destroy devices again that a dynamically loaded SSDT created. >> >> The biggest problem AFAIK is that under linux, many drivers cannot be unloaded. Also, there are many race conditions as the namespace entries "owned" by an SSDT being unloaded are deleted (out from underneath a driver). >> >> This is widely similar to the DT overlay behavior." >> >>>> I'm not sure that I want to change the interface to AcpiLoadTable >>>> just for something that is being deprecated. Already, we throw an >>>> ACPI_EXCEPTION if the Unload operator is encountered in the AML byte >>>> stream. The same thing with AcpiUnloadParentTable - it is being deprecated. >>>> >>>> ACPI_EXCEPTION ((AE_INFO, AE_NOT_IMPLEMENTED, >>>> "AML Unload operator is not supported")); > > Bob, what is your suggestion to fix the regression then? > > We could revert acpi_configfs.c to use acpi_tb_install_and_load_table() > instead of acpi_load_table(), leaving loaded APCI objects uninitalized, > but at least, unloading will work again. > > I guess my next question is: why do you want to unload a table in the > first place? Because it worked before and there are people who rely on it. If it's deprecated there should be a user notification and a reasonable end-of-life timeline to give these users a chance to develop an alternative solution. Niko > > > Do we have any other options? > > Niko >