Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp971418ybc; Sat, 16 Nov 2019 12:07:53 -0800 (PST) X-Google-Smtp-Source: APXvYqyKSDVFi9V5nyVI+BK16FAKWwPLaoj0qvth08AZYuWBN/W96k02cqPgQIPSvU9xQbIIeNxC X-Received: by 2002:a17:906:1942:: with SMTP id b2mr12431584eje.36.1573934873504; Sat, 16 Nov 2019 12:07:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573934873; cv=none; d=google.com; s=arc-20160816; b=kU0aqmhBV1XJLlD7uZ04jfyRsMGHfezhYoCJIEFz6VwlGMjSHYPmsRtNQGyT5mnb+5 Wbh4cQw+U0Vbjw3jCnSA3M4h/U8iEVxkjhkP8HBcpPmsS+hOU9I/qpPGUhDd9moRdA0e c1iITImcNzPdhOYxQW3mxsKSgRpftiFGIQQQuNFeq6k5Ex3Gf9rBOaSQLNu1Vu6em2X/ 0jWj4BLvpusD2FsmE+sbIimsDJWPomrN62fDDfaDIYG649NrHL7ta2GUBpS6qBk5eM/r AVRcAxLNC4DHYOc7qCExj3zvXPm0p2YoUpernLPXFRvqjO39hfqL/UYbpjy4LQCgI7Mg c81g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=wY1wH3qJgZtpNtkLWPMs/Hx5JZ/6TSGVFBrFCFyrP5o=; b=R6cNlpIuWJqDdm/PASH/WpheuBXI5K5hgslVABuGn0Yz+pzupqEEz9+oaJidLlqCUo GEq98vstQI2Yz8e+p++yH2QTtJpBT8ax2z9T/xlNIxTYRUCC9lweVCD+c7sKoZvymVel hp8oCihs5rKxX4llsSeHoh+J7QS2qrGGOPlT9lucQoAPCa1SB59sHlojhGldc/tInN53 ad5EcoDoddd6wbAFf7A1Wh6Z9ZdED375RqYs9cSEhKtha/bPQO8urJvDngihV54npfTo kkLH0KwI56PV74VYf1kJkMyPWxWu74tZ54fOyEe/usiITBduK9+n3uE7l9yESJOqSmRu 2PjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=zziXcq55; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j24si5989591ejx.326.2019.11.16.12.07.28; Sat, 16 Nov 2019 12:07:53 -0800 (PST) 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; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=zziXcq55; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727632AbfKPUGG (ORCPT + 99 others); Sat, 16 Nov 2019 15:06:06 -0500 Received: from mail-io1-f68.google.com ([209.85.166.68]:43722 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727115AbfKPUGG (ORCPT ); Sat, 16 Nov 2019 15:06:06 -0500 Received: by mail-io1-f68.google.com with SMTP id r2so9120861iot.10; Sat, 16 Nov 2019 12:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wY1wH3qJgZtpNtkLWPMs/Hx5JZ/6TSGVFBrFCFyrP5o=; b=zziXcq55OlVOLuZm7MpRDSXWx30fu7+5Cc3euyCJwYEaWyc2g7+EtTnm9Id9niU/Nm W+EZ8rWp14SISd2GKzLLAkXRwHYdzns3wsabAHX56ZN/2qTHNkqyCj9tymnEF1k3LUg4 EtoLos0XdYzH0kq5sHpkiHLGBE7DKzR8NXHoiHIcTuZjlyRDZCb1AhH+U8F82bVIZQ1e 604IsRtqHo7qfhCQh7bcBA6SoF1auC3TKjHgdDQkis2vYgvBQ/IHcG45+GUAoz1yyJVR 0zPjpZWXLipG/qtReTR432LKjQdmnyUA7ZNQI4Q0IAXm2uTiNzzqici4JwcEQOLnrocm 52bw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wY1wH3qJgZtpNtkLWPMs/Hx5JZ/6TSGVFBrFCFyrP5o=; b=e/ngN2sabzG5ipZh3vnOYTIYSNlK7N5u0iCTHMbgeQAxO++DpJYt3NOGTqjewlkwNN ZleMDPxbGbW3gxBTjm4Q87gK9q5SaC2l84A6WE72LIVZMzgo/5Ay4b9GT6xdRW9fYEkm 1Uq+eYkeHZdb6Q731hcSBNci2KD8mLbtdUBRD2qcT6roPZOo+2RpB1sLBjlrsegOqWE8 W75ec3Rl9xcpLQdEHjQOXL8n5SRycJPL5znF8pdNug/nMnmiPx7qPOu1CNHy51dRkhjc q6FQIsCEUyBztDGiOZXyV50CccA5i+TPRk6SCNSK2mf53V0j9DFZQN+EkhMDL/H1JgHK p55g== X-Gm-Message-State: APjAAAU+1cA/CH2IOrJZVava/CSwgQmyin5Y1JJpsYi0AlYhdsYlzGDV yWB6Ol6DAYj7BaBjw2L16kshX4njm99qqmwWYnM= X-Received: by 2002:a6b:b58b:: with SMTP id e133mr543469iof.86.1573934763525; Sat, 16 Nov 2019 12:06:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dan Williams Date: Sat, 16 Nov 2019 12:05:52 -0800 Message-ID: Subject: Re: [PATCH v2] ACPI: sysfs: Change ACPI_MASKABLE_GPE_MAX to 0x100 To: Yunfeng Ye Cc: "Rafael J. Wysocki" , Len Brown , Linux ACPI , Linux Kernel Mailing List , linux-doc@vger.kernel.org, "hushiyuan@huawei.com" , "linfeilong@huawei.com" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 13, 2019 at 11:17 PM Yunfeng Ye wrote: > > The commit 0f27cff8597d ("ACPI: sysfs: Make ACPI GPE mask kernel > parameter cover all GPEs") says: > "Use a bitmap of size 0xFF instead of a u64 for the GPE mask so 256 > GPEs can be masked" > > But the masking of GPE 0xFF it not supported and the check condition > "gpe > ACPI_MASKABLE_GPE_MAX" is not valid because the type of gpe is > u8. > > So modify the macro ACPI_MASKABLE_GPE_MAX to 0x100, and drop the "gpe > > ACPI_MASKABLE_GPE_MAX" check. In addition, update the docs "Format" for > acpi_mask_gpe parameter. > > Fixes: 0f27cff8597d ("ACPI: sysfs: Make ACPI GPE mask kernel parameter cover all GPEs") > Signed-off-by: Yunfeng Ye > --- > v1 -> v2: > - drop the "gpe > ACPI_MASKABLE_GPE_MAX" check > - update the docs "Format" from to for acpi_mask_gpe parameter > - update the commit comment > > Documentation/admin-guide/kernel-parameters.txt | 2 +- > drivers/acpi/sysfs.c | 4 ++-- > 2 files changed, 3 insertions(+), 3 deletions(-) Bisect flags commit eb09878e1301 "ACPI: sysfs: Change ACPI_MASKABLE_GPE_MAX to 0x100" in -next as the reason for a boot regression in my qemu-kvm test environment. It spews: [ 1.456728] ACPI: Masking GPE 0x0. ... [ 161.721420] ACPI: Masking GPE 0x0. ...and then hangs. A straight revert gets the configuration back on its feet. qemu-system-x86_64 --version QEMU emulator version 4.0.50 (v4.0.0-928-g49c6c6ac0cd8)