All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	pmenzel+bugzilla.kernel.org@molgen.mpg.de
Subject: Re: [PATCH] ACPI: use bitmap helper for masked GPEs
Date: Fri, 26 Jan 2018 23:02:05 +0800	[thread overview]
Message-ID: <1516978925.2752.0.camel@intel.com> (raw)
In-Reply-To: <CAJZ5v0gU=8a1_FkztbSrqc64u7i7W2PCSf-KDf=+79kr1e38HA@mail.gmail.com>

On Thu, 2018-01-25 at 17:31 +0100, Rafael J. Wysocki wrote:
> On Thu, Jan 25, 2018 at 7:14 AM, Zhang Rui <rui.zhang@intel.com>
> wrote:
> > 
> > "acpi_mask_gpe=" kernel parameter is introduced to mask one or more
> > GPEs
> > at boot stage, to prevent GPE flooding.
> > 
> > Currently, a maximum of 128 GPEs (from GPE 0x00 to GPE 0x7f) are
> > allowed
> > to be masked by this kernel parameter, but only one u64 variant is
> > used
> > as the bitmap for the masked GPEs in kernel.
> > 
> > This is bogus and makes some GPEs masked unexpected when masking a
> > GPE
> > larger than 0x40.
> Commit 0f27cff8597d (ACPI: sysfs: Make ACPI GPE mask kernel parameter
> cover all GPEs) in linux-next should cover this AFAICS.
> 
yes. please drop this one. Thanks.

-rui

> Thanks,
> Rafael
> --
> 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

      reply	other threads:[~2018-01-26 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  6:14 [PATCH] ACPI: use bitmap helper for masked GPEs Zhang Rui
2018-01-25 16:31 ` Rafael J. Wysocki
2018-01-26 15:02   ` Zhang Rui [this message]

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=1516978925.2752.0.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pmenzel+bugzilla.kernel.org@molgen.mpg.de \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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: link
Be 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.