Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp4268887pxv; Tue, 27 Jul 2021 03:10:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw37YmcfbXn6ZMxvVYxrf8zOM+opVKnfx1T4ADy0q7B2Bd+m3Fn/EmTFI9bmVm+MZPTqW8T X-Received: by 2002:a05:6402:5246:: with SMTP id t6mr26436555edd.205.1627380657891; Tue, 27 Jul 2021 03:10:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627380657; cv=none; d=google.com; s=arc-20160816; b=hVHOz4pDqwJMxed9BQ5zbKw2LOW/xfoRs8ZeHjsUWJ+o7Nkui8lhuQVw9VpW1LjwFB CVDwOudJT4eucNyhOfFIOU2AaTl0u2y9B0eG+r6cPL6NKscXz9tKX0vEOKb9lU6vGlvk Eh1Jl0qusEt5QSd/5DSs85Dg+DglbHNN7z5Jb1tLPQzbbt4Mb2we8b+w7lY3TbvElk2i PVgf7GOX+/wepjXq87RAArUWm5Ip3k8XynqREMqEa0QOdAZFTDED1CG+wR7Xngn0YrGI 3H5gi+J8NHUUMxYzgg6iiMWP+46Wc7/Qa75wS7s2f2FEOIE8oFsK4ovBV6cCpqjjmjg3 dcSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=5Q2zO1uEI9p9AqfLoo5GseEKl+6VMva1bFZkYWyr5G8=; b=L/svO0CPgTP0DHcfrWb1GRcReMMnzQHhpQSfx4nbQ5KEcfAYpd3khqDS6Dwlyev39M To+J0Bs50UDk4S2uWPEkVlgq00lZGtc2V7ZiNnr81avPDD9VY8gvFUvuvctI9lrxSP1i 4mXAXOPEbNGrWfpMFh9gMXNbjY217Q49eA3WH+UKNh+Zq7/scobvLm59yCwfiQ2cj4Ik idsiz0Fh2r7kuPFHk3Z9dG/CtA8dw1/9vZeD4+i9z6g4aWqEyDCBj5elBtEG7MRZPU7C h4oQjf7u2OWa6MNNRy59x0clO6Re85Eml+LUcbcaCzgewMB6fQ/fktp6aigxTGYtelBp 9WoQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b9si2539508ede.326.2021.07.27.03.10.33; Tue, 27 Jul 2021 03:10:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236153AbhG0KGy (ORCPT + 99 others); Tue, 27 Jul 2021 06:06:54 -0400 Received: from foss.arm.com ([217.140.110.172]:36910 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236105AbhG0KGx (ORCPT ); Tue, 27 Jul 2021 06:06:53 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F15D81FB; Tue, 27 Jul 2021 03:06:52 -0700 (PDT) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 586893F73D; Tue, 27 Jul 2021 03:06:51 -0700 (PDT) Date: Tue, 27 Jul 2021 11:06:45 +0100 From: Lorenzo Pieralisi To: Ard Biesheuvel Cc: Linux Kernel Mailing List , Will Deacon , Hanjun Guo , Sudeep Holla , Catalin Marinas , "Rafael J. Wysocki" , ACPI Devel Maling List , Linux ARM , Veronika kabatova , Robin Murphy Subject: Re: [PATCH] ACPI: Add memory semantics to acpi_os_map_memory() Message-ID: <20210727100645.GA7108@lpieralisi> References: <20210726100026.12538-1-lorenzo.pieralisi@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 26, 2021 at 05:55:33PM +0200, Ard Biesheuvel wrote: > On Mon, 26 Jul 2021 at 12:00, Lorenzo Pieralisi > wrote: > > > > The memory attributes attached to memory regions depend on architecture > > specific mappings. > > > > For some memory regions, the attributes specified by firmware (eg > > uncached) are not sufficient to determine how a memory region should be > > mapped by an OS (for instance a region that is define as uncached in > > firmware can be mapped as Normal or Device memory on arm64) and > > therefore the OS must be given control on how to map the region to match > > the expected mapping behaviour (eg if a mapping is requested with memory > > semantics, it must allow unaligned accesses). > > > > Rework acpi_os_map_memory() and acpi_os_ioremap() back-end to split > > them into two separate code paths: > > > > acpi_os_memmap() -> memory semantics > > acpi_os_ioremap() -> MMIO semantics > > > > The split allows the architectural implementation back-ends to detect > > the default memory attributes required by the mapping in question > > (ie the mapping API defines the semantics memory vs MMIO) and map the > > memory accordingly. > > > > Link: https://lore.kernel.org/linux-arm-kernel/31ffe8fc-f5ee-2858-26c5-0fd8bdd68702@arm.com > > Signed-off-by: Lorenzo Pieralisi > > Cc: Ard Biesheuvel > > Cc: Will Deacon > > Cc: Hanjun Guo > > Cc: Sudeep Holla > > Cc: Catalin Marinas > > Cc: "Rafael J. Wysocki" > > For the patch in general > > Acked-by: Ard Biesheuvel Thanks ! [...] > > -void __iomem __ref > > -*acpi_os_map_iomem(acpi_physical_address phys, acpi_size size) > > +static void __iomem __ref > > +*__acpi_os_map_iomem(acpi_physical_address phys, acpi_size size, bool memory) > > { > > struct acpi_ioremap *map; > > void __iomem *virt; > > @@ -353,7 +356,7 @@ void __iomem __ref > > > > pg_off = round_down(phys, PAGE_SIZE); > > pg_sz = round_up(phys + size, PAGE_SIZE) - pg_off; > > - virt = acpi_map(phys, size); > > + virt = acpi_map(phys, size, memory); > > if (!virt) { > > mutex_unlock(&acpi_ioremap_lock); > > kfree(map); > > @@ -372,11 +375,17 @@ void __iomem __ref > > mutex_unlock(&acpi_ioremap_lock); > > return map->virt + (phys - map->phys); > > } > > + > > +void __iomem __ref > > +*acpi_os_map_iomem(acpi_physical_address phys, acpi_size size) > > I am aware that this just duplicated the prototype above, but I think > this should be > > void __iomem *__ref > > given that the __ref comes after the * in the prototype below. Yes I just moved/duplicated the prototype above but I believe this is consistent with include/acpi/acpi_io.h unless I have not understood what you meant ? It is probably worth changing it in both places to void __iomem *__ref ? I can do that with an additional patch. > > > +{ > > + return __acpi_os_map_iomem(phys, size, false); > > +} > > EXPORT_SYMBOL_GPL(acpi_os_map_iomem); > > > > void *__ref acpi_os_map_memory(acpi_physical_address phys, acpi_size size) > > { > > - return (void *)acpi_os_map_iomem(phys, size); > > + return (void *)__acpi_os_map_iomem(phys, size, true); > > I think this should be (__force void *) to shut up sparse address > space warnings. Yes I can add that attribute in an additional patch and rebase this one on top of it. Thanks, Lorenzo > > > } > > EXPORT_SYMBOL_GPL(acpi_os_map_memory); > > > > diff --git a/include/acpi/acpi_io.h b/include/acpi/acpi_io.h > > index 027faa8883aa..a0212e67d6f4 100644 > > --- a/include/acpi/acpi_io.h > > +++ b/include/acpi/acpi_io.h > > @@ -14,6 +14,14 @@ static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > > } > > #endif > > > > +#ifndef acpi_os_memmap > > +static inline void __iomem *acpi_os_memmap(acpi_physical_address phys, > > + acpi_size size) > > +{ > > + return ioremap_cache(phys, size); > > +} > > +#endif > > + > > extern bool acpi_permanent_mmap; > > > > void __iomem __ref > > -- > > 2.31.0 > >