From: Dan Williams <dan.j.williams@intel.com> To: x86@kernel.org Cc: ard.biesheuvel@linaro.org, peterz@infradead.org, Dave Hansen <dave.hansen@linux.intel.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-nvdimm@lists.01.org, Jonathan Cameron <Jonathan.Cameron@huawei.com>, tglx@linutronix.de, Len Brown <lenb@kernel.org> Subject: [PATCH v4 09/10] acpi/numa/hmat: Register HMAT at device_initcall level Date: Mon, 24 Jun 2019 11:20:21 -0700 [thread overview] Message-ID: <156140042119.2951909.7727308817426477621.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) In-Reply-To: <156140036490.2951909.1837804994781523185.stgit@dwillia2-desk3.amr.corp.intel.com> In preparation for registering device-dax instances for accessing EFI specific-purpose memory, arrange for the HMAT registration to occur later in the init process. Critically HMAT initialization needs to occur after e820__reserve_resources_late() which is the point at which the iomem resource tree is populated with "Application Reserved" (IORES_DESC_APPLICATION_RESERVED). e820__reserve_resources_late() happens at subsys_initcall time. Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: Len Brown <lenb@kernel.org> Cc: Keith Busch <keith.busch@intel.com> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- drivers/acpi/numa/hmat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/numa/hmat.c b/drivers/acpi/numa/hmat.c index 2c220cb7b620..1d329c4af3bf 100644 --- a/drivers/acpi/numa/hmat.c +++ b/drivers/acpi/numa/hmat.c @@ -671,4 +671,4 @@ static __init int hmat_init(void) acpi_put_table(tbl); return 0; } -subsys_initcall(hmat_init); +device_initcall(hmat_init); _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com> To: x86@kernel.org Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>, Keith Busch <keith.busch@intel.com>, Jonathan Cameron <Jonathan.Cameron@huawei.com>, Dave Hansen <dave.hansen@linux.intel.com>, peterz@infradead.org, vishal.l.verma@intel.com, ard.biesheuvel@linaro.org, tglx@linutronix.de, linux-acpi@vger.kernel.org, linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org Subject: [PATCH v4 09/10] acpi/numa/hmat: Register HMAT at device_initcall level Date: Mon, 24 Jun 2019 11:20:21 -0700 [thread overview] Message-ID: <156140042119.2951909.7727308817426477621.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) In-Reply-To: <156140036490.2951909.1837804994781523185.stgit@dwillia2-desk3.amr.corp.intel.com> In preparation for registering device-dax instances for accessing EFI specific-purpose memory, arrange for the HMAT registration to occur later in the init process. Critically HMAT initialization needs to occur after e820__reserve_resources_late() which is the point at which the iomem resource tree is populated with "Application Reserved" (IORES_DESC_APPLICATION_RESERVED). e820__reserve_resources_late() happens at subsys_initcall time. Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: Len Brown <lenb@kernel.org> Cc: Keith Busch <keith.busch@intel.com> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> --- drivers/acpi/numa/hmat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/numa/hmat.c b/drivers/acpi/numa/hmat.c index 2c220cb7b620..1d329c4af3bf 100644 --- a/drivers/acpi/numa/hmat.c +++ b/drivers/acpi/numa/hmat.c @@ -671,4 +671,4 @@ static __init int hmat_init(void) acpi_put_table(tbl); return 0; } -subsys_initcall(hmat_init); +device_initcall(hmat_init);
next prev parent reply other threads:[~2019-06-24 18:34 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-24 18:19 [PATCH v4 00/10] EFI Specific Purpose Memory Support Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-06-24 18:19 ` [PATCH v4 01/10] acpi/numa: Establish a new drivers/acpi/numa/ directory Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-06-25 14:59 ` Jonathan Cameron 2019-06-25 14:59 ` Jonathan Cameron 2019-06-25 16:02 ` Dan Williams 2019-06-25 16:02 ` Dan Williams 2019-07-03 11:09 ` Rafael J. Wysocki 2019-07-03 11:09 ` Rafael J. Wysocki 2019-06-24 18:19 ` [PATCH v4 02/10] acpi/numa/hmat: Skip publishing target info for nodes with no online memory Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-07-03 11:10 ` Rafael J. Wysocki 2019-07-03 11:10 ` Rafael J. Wysocki 2019-06-24 18:19 ` [PATCH v4 03/10] efi: Enumerate EFI_MEMORY_SP Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-06-24 18:19 ` [PATCH v4 04/10] x86, efi: Push EFI_MEMMAP check into leaf routines Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-06-24 18:19 ` [PATCH v4 05/10] x86, efi: Reserve UEFI 2.8 Specific Purpose Memory for dax Dan Williams 2019-06-24 18:19 ` Dan Williams 2019-06-25 15:26 ` Jonathan Cameron 2019-06-25 15:26 ` Jonathan Cameron 2019-06-24 18:20 ` [PATCH v4 06/10] x86, efi: Add efi_fake_mem support for EFI_MEMORY_SP Dan Williams 2019-06-24 18:20 ` Dan Williams 2019-06-24 18:20 ` [PATCH v4 07/10] resource: Uplevel the pmem "region" ida to a global allocator Dan Williams 2019-06-24 18:20 ` Dan Williams 2019-06-24 18:20 ` [PATCH v4 08/10] device-dax: Add a driver for "hmem" devices Dan Williams 2019-06-24 18:20 ` Dan Williams 2019-06-25 15:37 ` Jonathan Cameron 2019-06-25 15:37 ` Jonathan Cameron 2019-06-25 20:07 ` Dan Williams 2019-06-25 20:07 ` Dan Williams 2019-06-24 18:20 ` Dan Williams [this message] 2019-06-24 18:20 ` [PATCH v4 09/10] acpi/numa/hmat: Register HMAT at device_initcall level Dan Williams 2019-07-03 11:12 ` Rafael J. Wysocki 2019-07-03 11:12 ` Rafael J. Wysocki 2019-06-24 18:20 ` [PATCH v4 10/10] acpi/numa/hmat: Register "specific purpose" memory as an "hmem" device Dan Williams 2019-06-24 18:20 ` Dan Williams 2019-06-25 15:58 ` Jonathan Cameron 2019-06-25 15:58 ` Jonathan Cameron 2019-07-03 11:17 ` Rafael J. Wysocki 2019-07-03 11:17 ` Rafael J. Wysocki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=156140042119.2951909.7727308817426477621.stgit@dwillia2-desk3.amr.corp.intel.com \ --to=dan.j.williams@intel.com \ --cc=Jonathan.Cameron@huawei.com \ --cc=ard.biesheuvel@linaro.org \ --cc=dave.hansen@linux.intel.com \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=peterz@infradead.org \ --cc=rjw@rjwysocki.net \ --cc=tglx@linutronix.de \ --cc=x86@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.