From patchwork Mon Feb 25 21:02:10 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Toshi Kani X-Patchwork-Id: 2182021 Return-Path: X-Original-To: patchwork-linux-acpi@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id 31224DF230 for ; Mon, 25 Feb 2013 21:13:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754791Ab3BYVNN (ORCPT ); Mon, 25 Feb 2013 16:13:13 -0500 Received: from g5t0007.atlanta.hp.com ([15.192.0.44]:15839 "EHLO g5t0007.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753779Ab3BYVNM (ORCPT ); Mon, 25 Feb 2013 16:13:12 -0500 Received: from g5t0030.atlanta.hp.com (g5t0030.atlanta.hp.com [16.228.8.142]) by g5t0007.atlanta.hp.com (Postfix) with ESMTP id A3EDE14749; Mon, 25 Feb 2013 21:13:11 +0000 (UTC) Received: from misato.fc.hp.com (misato.fc.hp.com [16.71.12.41]) by g5t0030.atlanta.hp.com (Postfix) with ESMTP id 80C46140E3; Mon, 25 Feb 2013 21:13:09 +0000 (UTC) From: Toshi Kani To: rjw@sisk.pl Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, isimatu.yasuaki@jp.fujitsu.com, vasilis.liaskovitis@profitbricks.com, Toshi Kani Subject: [PATCH v2] ACPI: Add sysfs links from memory device to memblocks Date: Mon, 25 Feb 2013 14:02:10 -0700 Message-Id: <1361826130-31062-1-git-send-email-toshi.kani@hp.com> X-Mailer: git-send-email 1.7.11.7 Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org In order to eject a memory device object represented as "PNP0C80:%d" in sysfs, its associated memblocks (system/memory/memory%d) need to be off-lined. However, there is no user friendly way to correlate between a memory device object and its memblocks in sysfs. This patch creates sysfs links to memblocks under a memory device object so that a user can easily checks and manipulates its memblocks in sysfs. For example, when PNP0C80:05 is associated with memory8 and memory9, the following two links are created under PNP0C80:05. This allows a user to access memory8/9 directly from PNP0C80:05. # ll /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C80:05 lrwxrwxrwx. memory8 -> ../../../system/memory/memory8 lrwxrwxrwx. memory9 -> ../../../system/memory/memory9 Signed-off-by: Toshi Kani Tested-by: Yasuaki Ishimatsu Acked-by: Yasuaki Ishimatsu --- This patch applies on top of the Rafael's patch below. https://patchwork.kernel.org/patch/2153261/ v2: Added a NULL return check for find_memory_block_hinted() as pointed by Yasuaki Ishimatsu. --- drivers/acpi/acpi_memhotplug.c | 56 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 56 insertions(+) -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c index 3b3abbc..98477a5 100644 --- a/drivers/acpi/acpi_memhotplug.c +++ b/drivers/acpi/acpi_memhotplug.c @@ -28,6 +28,7 @@ */ #include +#include #include #include "internal.h" @@ -168,6 +169,55 @@ static int acpi_memory_check_device(struct acpi_memory_device *mem_device) return 0; } +static void acpi_setup_mem_blk_links(struct acpi_memory_device *mem_device, + struct acpi_memory_info *info, bool add_links) +{ + struct memory_block *mem_blk = NULL; + struct mem_section *mem_sect; + unsigned long start_pfn, end_pfn, pfn; + unsigned long section_nr; + int ret; + + start_pfn = PFN_DOWN(info->start_addr); + end_pfn = PFN_UP(info->start_addr + info->length-1); + + for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) { + section_nr = pfn_to_section_nr(pfn); + + if (!present_section_nr(section_nr)) + continue; + + mem_sect = __nr_to_section(section_nr); + + /* skip if the same memblock */ + if (mem_blk) + if ((section_nr >= mem_blk->start_section_nr) && + (section_nr <= mem_blk->end_section_nr)) + continue; + + mem_blk = find_memory_block_hinted(mem_sect, mem_blk); + if (!mem_blk) + continue; + + if (add_links) { + ret = sysfs_create_link_nowarn( + &mem_device->device->dev.kobj, + &mem_blk->dev.kobj, + kobject_name(&mem_blk->dev.kobj)); + if (ret && ret != -EEXIST) + dev_err(&mem_device->device->dev, + "Failed to create sysfs link %s\n", + kobject_name(&mem_blk->dev.kobj)); + } else { + sysfs_remove_link(&mem_device->device->dev.kobj, + kobject_name(&mem_blk->dev.kobj)); + } + } + + if (mem_blk) + kobject_put(&mem_blk->dev.kobj); +} + static int acpi_memory_enable_device(struct acpi_memory_device *mem_device) { int result, num_enabled = 0; @@ -207,6 +257,9 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device) continue; } + /* Create sysfs links to its mem_blk devices */ + acpi_setup_mem_blk_links(mem_device, info, true); + if (!result) info->enabled = 1; /* @@ -241,6 +294,9 @@ static int acpi_memory_remove_memory(struct acpi_memory_device *mem_device) /* The kernel does not use this memory block */ continue; + /* Remove sysfs links to its mem_blk devices */ + acpi_setup_mem_blk_links(mem_device, info, false); + if (!info->enabled) /* * The kernel uses this memory block, but it may be not