From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-x241.google.com (mail-ot0-x241.google.com [IPv6:2607:f8b0:4003:c0f::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id E7E0320352AA6 for ; Fri, 15 Dec 2017 18:11:01 -0800 (PST) Received: by mail-ot0-x241.google.com with SMTP id j2so9327008ota.13 for ; Fri, 15 Dec 2017 18:15:44 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <20171214021019.13579-2-ross.zwisler@linux.intel.com> <1658696.rIK19Js0WO@aspire.rjw.lan> From: "Rafael J. Wysocki" Date: Sat, 16 Dec 2017 03:15:43 +0100 Message-ID: Subject: Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array() List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: "Box, David E" , Dave Hansen , "Zheng, Lv" , "linux-nvdimm@lists.01.org" , "Rafael J. Wysocki" , Anaczkowski,, "Robert , Linux ACPI , Odzioba, Lukasz" , "Schmauss, Erik , Len Brown , John Hubbard" , Jerome Glisse , Kogut,, "Marcin , Brice Goglin , Nachimuthu, Murugasamy" , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" , Koziej,, "Joonas , Andrew Morton , Tim Chen" List-ID: On Sat, Dec 16, 2017 at 2:57 AM, Dan Williams wrote: > On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: >> On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >>> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >>> wrote: >>> > The current implementation of acpi_parse_entries_array() assumes that each >>> > subtable has a standard ACPI subtable entry of type struct >>> > acpi_subtable_header. This standard subtable header has a one byte length >>> > followed by a one byte type. >>> > >>> > The HMAT subtables have to allow for a longer length so they have subtable >>> > headers of type struct acpi_hmat_structure which has a 2 byte type and a 4 >>> > byte length. >>> >>> Hmm, NFIT has a 2 byte type and a 2 byte length, so its one more >>> permutation. I happened to reinvent sub-table parsing in the NFIT >>> driver, but it might be nice in the future to refactor that to use the >>> common parsing. >>> >>> > >>> > Enhance the subtable parsing in acpi_parse_entries_array() so that it can >>> > handle these new HMAT subtables. >>> > >>> > Signed-off-by: Ross Zwisler >>> > --- >>> > drivers/acpi/tables.c | 52 ++++++++++++++++++++++++++++++++++++++++----------- >>> > 1 file changed, 41 insertions(+), 11 deletions(-) >>> > >>> > diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c >>> > index 80ce2a7d224b..f777b94c234a 100644 >>> > --- a/drivers/acpi/tables.c >>> > +++ b/drivers/acpi/tables.c >>> > @@ -218,6 +218,33 @@ void acpi_table_print_madt_entry(struct acpi_subtable_header *header) >>> > } >>> > } >>> > >>> > +static unsigned long __init >>> > +acpi_get_entry_type(char *id, void *entry) >>> > +{ >>> > + if (strncmp(id, ACPI_SIG_HMAT, 4) == 0) >>> > + return ((struct acpi_hmat_structure *)entry)->type; >>> > + else >>> > + return ((struct acpi_subtable_header *)entry)->type; >>> > +} >>> >>> It seems inefficient to make all checks keep asking "is HMAT?". >> >> Well, ideally, the signature should be checked once. I guess that can be >> arranged for here. >> >>> Especially if we want to extend this to other table types should we >>> instead setup and pass a pair of function pointers to parse the >>> sub-table format? >> >> Function pointers may be too much even. :-) > > True, how about an enum of acpi sub-table header types? That works. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array() Date: Sat, 16 Dec 2017 03:15:43 +0100 Message-ID: References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <20171214021019.13579-2-ross.zwisler@linux.intel.com> <1658696.rIK19Js0WO@aspire.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-ot0-f196.google.com ([74.125.82.196]:39311 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755970AbdLPCPo (ORCPT ); Fri, 15 Dec 2017 21:15:44 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Dan Williams Cc: "Rafael J. Wysocki" , Linux ACPI , Ross Zwisler , "linux-kernel@vger.kernel.org" , "Anaczkowski, Lukasz" , "Box, David E" , "Kogut, Jaroslaw" , "Koss, Marcin" , "Koziej, Artur" , "Lahtinen, Joonas" , "Moore, Robert" , "Nachimuthu, Murugasamy" , "Odzioba, Lukasz" , "Rafael J. Wysocki" , "Schmauss, Erik" , "Verma, Vishal L" , "Zheng, Lv" On Sat, Dec 16, 2017 at 2:57 AM, Dan Williams wrote: > On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: >> On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >>> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >>> wrote: >>> > The current implementation of acpi_parse_entries_array() assumes that each >>> > subtable has a standard ACPI subtable entry of type struct >>> > acpi_subtable_header. This standard subtable header has a one byte length >>> > followed by a one byte type. >>> > >>> > The HMAT subtables have to allow for a longer length so they have subtable >>> > headers of type struct acpi_hmat_structure which has a 2 byte type and a 4 >>> > byte length. >>> >>> Hmm, NFIT has a 2 byte type and a 2 byte length, so its one more >>> permutation. I happened to reinvent sub-table parsing in the NFIT >>> driver, but it might be nice in the future to refactor that to use the >>> common parsing. >>> >>> > >>> > Enhance the subtable parsing in acpi_parse_entries_array() so that it can >>> > handle these new HMAT subtables. >>> > >>> > Signed-off-by: Ross Zwisler >>> > --- >>> > drivers/acpi/tables.c | 52 ++++++++++++++++++++++++++++++++++++++++----------- >>> > 1 file changed, 41 insertions(+), 11 deletions(-) >>> > >>> > diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c >>> > index 80ce2a7d224b..f777b94c234a 100644 >>> > --- a/drivers/acpi/tables.c >>> > +++ b/drivers/acpi/tables.c >>> > @@ -218,6 +218,33 @@ void acpi_table_print_madt_entry(struct acpi_subtable_header *header) >>> > } >>> > } >>> > >>> > +static unsigned long __init >>> > +acpi_get_entry_type(char *id, void *entry) >>> > +{ >>> > + if (strncmp(id, ACPI_SIG_HMAT, 4) == 0) >>> > + return ((struct acpi_hmat_structure *)entry)->type; >>> > + else >>> > + return ((struct acpi_subtable_header *)entry)->type; >>> > +} >>> >>> It seems inefficient to make all checks keep asking "is HMAT?". >> >> Well, ideally, the signature should be checked once. I guess that can be >> arranged for here. >> >>> Especially if we want to extend this to other table types should we >>> instead setup and pass a pair of function pointers to parse the >>> sub-table format? >> >> Function pointers may be too much even. :-) > > True, how about an enum of acpi sub-table header types? That works. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756666AbdLPCPt (ORCPT ); Fri, 15 Dec 2017 21:15:49 -0500 Received: from mail-ot0-f196.google.com ([74.125.82.196]:39311 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755970AbdLPCPo (ORCPT ); Fri, 15 Dec 2017 21:15:44 -0500 X-Google-Smtp-Source: ACJfBovdDwwGYMaz5OQ084sD3wqYyQv/f/3WS97/MBPYeNtPPwKNvjERQEx2NaCLDsGUhpC6DmmOmpPFxQ/RGZRJbO8= MIME-Version: 1.0 In-Reply-To: References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <20171214021019.13579-2-ross.zwisler@linux.intel.com> <1658696.rIK19Js0WO@aspire.rjw.lan> From: "Rafael J. Wysocki" Date: Sat, 16 Dec 2017 03:15:43 +0100 X-Google-Sender-Auth: CLLmMCCOAcRc_nRnLOFBELSj1Cg Message-ID: Subject: Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array() To: Dan Williams Cc: "Rafael J. Wysocki" , Linux ACPI , Ross Zwisler , "linux-kernel@vger.kernel.org" , "Anaczkowski, Lukasz" , "Box, David E" , "Kogut, Jaroslaw" , "Koss, Marcin" , "Koziej, Artur" , "Lahtinen, Joonas" , "Moore, Robert" , "Nachimuthu, Murugasamy" , "Odzioba, Lukasz" , "Rafael J. Wysocki" , "Schmauss, Erik" , "Verma, Vishal L" , "Zheng, Lv" , Andrew Morton , Balbir Singh , Brice Goglin , Dave Hansen , Jerome Glisse , John Hubbard , Len Brown , Tim Chen , Linux MM , "linux-nvdimm@lists.01.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 16, 2017 at 2:57 AM, Dan Williams wrote: > On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: >> On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >>> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >>> wrote: >>> > The current implementation of acpi_parse_entries_array() assumes that each >>> > subtable has a standard ACPI subtable entry of type struct >>> > acpi_subtable_header. This standard subtable header has a one byte length >>> > followed by a one byte type. >>> > >>> > The HMAT subtables have to allow for a longer length so they have subtable >>> > headers of type struct acpi_hmat_structure which has a 2 byte type and a 4 >>> > byte length. >>> >>> Hmm, NFIT has a 2 byte type and a 2 byte length, so its one more >>> permutation. I happened to reinvent sub-table parsing in the NFIT >>> driver, but it might be nice in the future to refactor that to use the >>> common parsing. >>> >>> > >>> > Enhance the subtable parsing in acpi_parse_entries_array() so that it can >>> > handle these new HMAT subtables. >>> > >>> > Signed-off-by: Ross Zwisler >>> > --- >>> > drivers/acpi/tables.c | 52 ++++++++++++++++++++++++++++++++++++++++----------- >>> > 1 file changed, 41 insertions(+), 11 deletions(-) >>> > >>> > diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c >>> > index 80ce2a7d224b..f777b94c234a 100644 >>> > --- a/drivers/acpi/tables.c >>> > +++ b/drivers/acpi/tables.c >>> > @@ -218,6 +218,33 @@ void acpi_table_print_madt_entry(struct acpi_subtable_header *header) >>> > } >>> > } >>> > >>> > +static unsigned long __init >>> > +acpi_get_entry_type(char *id, void *entry) >>> > +{ >>> > + if (strncmp(id, ACPI_SIG_HMAT, 4) == 0) >>> > + return ((struct acpi_hmat_structure *)entry)->type; >>> > + else >>> > + return ((struct acpi_subtable_header *)entry)->type; >>> > +} >>> >>> It seems inefficient to make all checks keep asking "is HMAT?". >> >> Well, ideally, the signature should be checked once. I guess that can be >> arranged for here. >> >>> Especially if we want to extend this to other table types should we >>> instead setup and pass a pair of function pointers to parse the >>> sub-table format? >> >> Function pointers may be too much even. :-) > > True, how about an enum of acpi sub-table header types? That works. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f72.google.com (mail-oi0-f72.google.com [209.85.218.72]) by kanga.kvack.org (Postfix) with ESMTP id DF1C36B026E for ; Fri, 15 Dec 2017 21:15:44 -0500 (EST) Received: by mail-oi0-f72.google.com with SMTP id d76so4844233oig.12 for ; Fri, 15 Dec 2017 18:15:44 -0800 (PST) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id 20sor3125187otd.69.2017.12.15.18.15.43 for (Google Transport Security); Fri, 15 Dec 2017 18:15:44 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <20171214021019.13579-2-ross.zwisler@linux.intel.com> <1658696.rIK19Js0WO@aspire.rjw.lan> From: "Rafael J. Wysocki" Date: Sat, 16 Dec 2017 03:15:43 +0100 Message-ID: Subject: Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array() Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Dan Williams Cc: "Rafael J. Wysocki" , Linux ACPI , Ross Zwisler , "linux-kernel@vger.kernel.org" , "Anaczkowski, Lukasz" , "Box, David E" , "Kogut, Jaroslaw" , "Koss, Marcin" , "Koziej, Artur" , "Lahtinen, Joonas" , "Moore, Robert" , "Nachimuthu, Murugasamy" , "Odzioba, Lukasz" , "Rafael J. Wysocki" , "Schmauss, Erik" , "Verma, Vishal L" , "Zheng, Lv" , Andrew Morton , Balbir Singh , Brice Goglin , Dave Hansen , Jerome Glisse , John Hubbard , Len Brown , Tim Chen , Linux MM , "linux-nvdimm@lists.01.org" On Sat, Dec 16, 2017 at 2:57 AM, Dan Williams wrote: > On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: >> On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >>> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >>> wrote: >>> > The current implementation of acpi_parse_entries_array() assumes that each >>> > subtable has a standard ACPI subtable entry of type struct >>> > acpi_subtable_header. This standard subtable header has a one byte length >>> > followed by a one byte type. >>> > >>> > The HMAT subtables have to allow for a longer length so they have subtable >>> > headers of type struct acpi_hmat_structure which has a 2 byte type and a 4 >>> > byte length. >>> >>> Hmm, NFIT has a 2 byte type and a 2 byte length, so its one more >>> permutation. I happened to reinvent sub-table parsing in the NFIT >>> driver, but it might be nice in the future to refactor that to use the >>> common parsing. >>> >>> > >>> > Enhance the subtable parsing in acpi_parse_entries_array() so that it can >>> > handle these new HMAT subtables. >>> > >>> > Signed-off-by: Ross Zwisler >>> > --- >>> > drivers/acpi/tables.c | 52 ++++++++++++++++++++++++++++++++++++++++----------- >>> > 1 file changed, 41 insertions(+), 11 deletions(-) >>> > >>> > diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c >>> > index 80ce2a7d224b..f777b94c234a 100644 >>> > --- a/drivers/acpi/tables.c >>> > +++ b/drivers/acpi/tables.c >>> > @@ -218,6 +218,33 @@ void acpi_table_print_madt_entry(struct acpi_subtable_header *header) >>> > } >>> > } >>> > >>> > +static unsigned long __init >>> > +acpi_get_entry_type(char *id, void *entry) >>> > +{ >>> > + if (strncmp(id, ACPI_SIG_HMAT, 4) == 0) >>> > + return ((struct acpi_hmat_structure *)entry)->type; >>> > + else >>> > + return ((struct acpi_subtable_header *)entry)->type; >>> > +} >>> >>> It seems inefficient to make all checks keep asking "is HMAT?". >> >> Well, ideally, the signature should be checked once. I guess that can be >> arranged for here. >> >>> Especially if we want to extend this to other table types should we >>> instead setup and pass a pair of function pointers to parse the >>> sub-table format? >> >> Function pointers may be too much even. :-) > > True, how about an enum of acpi sub-table header types? That works. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org