From: <Mario_Limonciello@Dell.com>
To: <rafael@kernel.org>, <luto@amacapital.net>
Cc: <pjones@redhat.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <lenb@kernel.org>,
<rjw@rjwysocki.net>
Subject: RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.
Date: Thu, 23 Jun 2016 15:38:04 +0000 [thread overview]
Message-ID: <d117d2c7b63446d098aa93f88a2b5686@ausx13mpc124.AMER.DELL.COM> (raw)
In-Reply-To: <CAJZ5v0g5E-=ORTQEqjnv-U=7mAwqD-t1-A1nfaFTJsypuT2ueg@mail.gmail.com>
> -----Original Message-----
> From: rjwysocki@gmail.com [mailto:rjwysocki@gmail.com] On Behalf Of
> Rafael J. Wysocki
> Sent: Wednesday, June 22, 2016 5:48 PM
> To: Andy Lutomirski <luto@amacapital.net>; Limonciello, Mario
> <Mario_Limonciello@Dell.com>
> Cc: Rafael Wysocki <rafael@kernel.org>; Peter Jones <pjones@redhat.com>;
> Linux ACPI <linux-acpi@vger.kernel.org>; linux-kernel@vger.kernel.org; Len
> Brown <lenb@kernel.org>; Rafael J. Wysocki <rjw@rjwysocki.net>
> Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of
> PCIe hotplug.
>
> On Wed, Jun 22, 2016 at 10:53 PM, Andy Lutomirski <luto@amacapital.net>
> wrote:
> > On Wed, Jun 22, 2016 at 12:43 PM, <Mario_Limonciello@dell.com> wrote:
> >>> -----Original Message-----
> >>> From: rjwysocki@gmail.com [mailto:rjwysocki@gmail.com] On Behalf Of
>
> [cut]
>
> >> I think changing that would help communicate what's going on here and at
> >> least let the user know the result will be that the firmware is still
> controlling
> >> ASPM due to the _OSC failure.
>
> You seem to be assuming that all systems returning "unsupported UUID"
> from the PCI host bridge _OSC will always fall into the same category,
> but what if they don't? What if at least some of them are really
> broken?
>
Even if they are broken, the net result will be the firmware is in control
of ASPM, won't it? At least outside of the group on this mailing list that
might not be very apparent from the current set of errors output into
logs.
> >> Something else that I think Andy recommended a while back was at that
> >> time try to evaluate NEXP and display its value and an associated message
> >> in debug logs when _OSC fails. Would you be amenable to a change like
> that?
> >
> > That seems dangerous if NEXP is anything other than a SystemMemory
> > variable. I don't know if there's a clean way to check that before
> > evaluating it. (i.e. we don't want to hit some other thing called
> > NEXP that has side effects.)
>
> Well, that's generic code and NEXP is not generic really, so agreed.
OK.
prev parent reply other threads:[~2016-06-23 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 22:15 [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug Peter Jones
2016-06-16 0:12 ` Rafael J. Wysocki
2016-06-16 14:56 ` Rafael J. Wysocki
2016-06-21 15:18 ` Peter Jones
2016-06-21 18:01 ` Mario_Limonciello
2016-06-21 18:07 ` Andy Lutomirski
2016-06-21 22:54 ` Rafael J. Wysocki
2016-06-21 22:51 ` Rafael J. Wysocki
2016-06-22 19:43 ` Mario_Limonciello
2016-06-22 20:53 ` Andy Lutomirski
2016-06-22 22:47 ` Rafael J. Wysocki
2016-06-23 15:38 ` Mario_Limonciello [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=d117d2c7b63446d098aa93f88a2b5686@ausx13mpc124.AMER.DELL.COM \
--to=mario_limonciello@dell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pjones@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).