Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4239725ybi; Tue, 18 Jun 2019 14:30:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqzib/Fz/0INmc9YA0CBhiRSEON7e4NYaqS5qrH0rMQVp6KZwgh620DVwa6gioyjnL4PcSdH X-Received: by 2002:a63:2e02:: with SMTP id u2mr4766608pgu.112.1560893420115; Tue, 18 Jun 2019 14:30:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560893420; cv=none; d=google.com; s=arc-20160816; b=axOw+Ldbmcu6KJ/93bWwmSrR8VWSy2Q1wc7pDdsKay+Ju0tvQs9mUVtmKpktCbn3op jZN1xq8kFUdzVhsN98PEbD5aFjEMr2ElubwYRwfrDqIdSi+A9wKzWLAGsOAgVaWPdRZK wcltyKMu7YFOpun/bEDkyIO/tIzcdfkWQ219NL6Ap6JPgOdYIcYaA1K5mBsfPUoaZde2 eXXX8kD6eGQus9lXIvEPhdwd4ZcC78ycN+GgxsMURUr+Qo8vuUvvGMq6L3z6T/D7kVWg cSL6zJV2dUr1ViB5KTD3GZS+Nf1rjzD2jj33nGI1bv0+rU5H4liBQXAkPnsLLN0tbgHN J/Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=kuf+YcKDazVcQyP7KOS5u4T2HSJxAHb67W2y4zH6pM8=; b=bYgSEyDk5JTznVz7KWGlR4QKXJW4yy7iIqi/Uy3zJrcCfXdAyIgP5mXGtWFqmUWtph PfPttR0afuCmd4MAQgrvJjBv+mo+FxfGhAsM9Ll9Qhq3Bvo631umbOaupC3+ZZJ8Vbs8 BhXB6qclaxt/MFpTGaxnfAOo+a3Byr1CyH/4fyICzAMgN60WP4c3tYR38/m2KvQ/5H+B Hjx65tX/IberYs8T5LFzCTmrLnDB+tChKZdDCLxyrH3kP3mIRJMx86pGNwmRXGAH+DDP ARqev/UARoqxfxvbU849H8mcrMtMrMKuyZvX+jMS8Br4cmA7moIFmYoz+/P/iN+HlOpi iyOw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e39si14548998plg.103.2019.06.18.14.30.04; Tue, 18 Jun 2019 14:30:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730556AbfFRV2e (ORCPT + 99 others); Tue, 18 Jun 2019 17:28:34 -0400 Received: from foss.arm.com ([217.140.110.172]:33068 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730368AbfFRV2d (ORCPT ); Tue, 18 Jun 2019 17:28:33 -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 DAFCE360; Tue, 18 Jun 2019 14:28:32 -0700 (PDT) Received: from [192.168.122.164] (u201426.austin.arm.com [10.118.28.29]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C84843F718; Tue, 18 Jun 2019 14:28:32 -0700 (PDT) Subject: Re: [PATCH v2 1/2] ACPI/PPTT: Add support for ACPI 6.3 thread flag To: John Garry , Valentin Schneider , linux-arm-kernel@lists.infradead.org Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, will.deacon@arm.com, rjw@rjwysocki.net, sudeep.holla@arm.com, lenb@kernel.org References: <20190614223158.49575-1-jeremy.linton@arm.com> <20190614223158.49575-2-jeremy.linton@arm.com> <667f95c0-5aa9-f460-a49a-e6dfefc027d8@arm.com> <2d1b547f-f9ee-391c-c4f3-0232a08a86bc@arm.com> <718438d0-8648-897a-83e8-801146a0af86@arm.com> From: Jeremy Linton Message-ID: <11fb712f-b3c2-5491-89ee-ea7efb18ddd8@arm.com> Date: Tue, 18 Jun 2019 16:28:32 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 6/18/19 12:23 PM, John Garry wrote: > On 18/06/2019 15:40, Valentin Schneider wrote: >> On 18/06/2019 15:21, Jeremy Linton wrote: >> [...] >>>>> + * Return: -ENOENT if the PPTT doesn't exist, the CPU cannot be >>>>> found or >>>>> + *       the table revision isn't new enough. >>>>> + * Otherwise returns flag value >>>>> + */ >>>> >>>> Nit: strictly speaking we're not returning the flag value but its mask >>>> applied to the flags field. I don't think anyone will care about >>>> getting >>>> the actual flag value, but it should be made obvious in the doc: >>> >>> Or I clarify the code to actually do what the comments says. Maybe >>> that is what John G was also pointing out too? >>> > > No, I was just saying that the kernel topology can be broken without > this series. > >> >> Mmm I didn't find any reply from John regarding this in v1, but I >> wouldn't >> mind either way, as long as the doc & code are aligned. >> > > BTW, to me, function acpi_pptt_cpu_is_thread() seems to try to do too > much, i.e. check if the PPTT is new enough to support the thread flag > and also check if it is set for a specific cpu. I'd consider separate > functions here. ? Your suggesting replacing the if (table->revision >= rev) cpu_node = acpi_find_processor_node(table, acpi_cpu_id); check with if (revision_check(table, rev)) cpu_node = acpi_find_processor_node(table, acpi_cpu_id); and a function like static int revision_check(acpixxxx *table, int rev) { return (table->revision >= rev); } Although, frankly if one were to do this, it should probably be a macro with the table type, and used in the dozen or so other places I found doing similar checks (spcr, iort, etc). Or something else? > > thanks, > John > >> [...] >> >> . >> > >