From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753352AbbEAE4a (ORCPT ); Fri, 1 May 2015 00:56:30 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:50855 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbbEAE42 (ORCPT ); Fri, 1 May 2015 00:56:28 -0400 Date: Fri, 1 May 2015 05:56:19 +0100 From: Matthew Garrett To: "Rafael J. Wysocki" Cc: Darren Hart , Kast Bernd , corentin.chary@gmail.com, lenb@kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, acpi4asus-user@lists.sourceforge.net, platform-driver-x86@vger.kernel.org Subject: Re: [RFC 1/2] ACPI: activate&export acpi_os_get_physical_address Message-ID: <20150501045618.GA22054@srcf.ucam.org> References: <20150430181025.GC40200@fury.dvhart.com> <4189370.scsJsnLdx0@vostro.rjw.lan> <2766179.6BuP3vhKAH@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2766179.6BuP3vhKAH@vostro.rjw.lan> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 01, 2015 at 03:45:52AM +0200, Rafael J. Wysocki wrote: > And I don't really understand the Matthew's comment regarding limiting > operation regions to system memory. This is about a specific operation > region (which BTW only seems to be used as a means to access system memory > at the location pointed to by the arg) in that particular method. My feeling was that it really ought to have been the ACPI code dealing with this in some way, but having looked at it again I accept that this is really something that's limited by the vendor implementation. virt_to_phys() isn't the worst thing to do here. -- Matthew Garrett | mjg59@srcf.ucam.org