From: "Schmauss, Erik" <erik.schmauss@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>, Moore,
Subject: RE: [PATCH v2 5/7] ACPICA: Integrate package handling with module-level code
Date: Mon, 16 Apr 2018 23:15:49 +0000 [thread overview]
Message-ID: <CF6A88132359CE47947DB4C6E1709ED539727606@ORSMSX110.amr.corp.intel.com> (raw)
In-Reply-To: <CAPcyv4j-iC+b07=JPP_TV1MLHA2iO5iKLvc+jaPHoEuRfzoAFQ@mail.gmail.com>
[ trimming ]
> >> Rafael, we may want to hold back on the module-level code changes
> >> (the patches below) for rc1. Between this and the strange _TSS issue,
> >> it seems like there are a few more things to resolve before this is
> >> ready for kernel upstream.
> >
Hi Rafael,
> > It looks like you are asking me to queue up reverts as per the Dan's
> > report, is that correct?
This is indeed what I meant last week. However, I've looked into the issue and Dan's qemu
instance had AML that we no longer support. This is because the ACPICA commit makes changes to the execution of AML
during table load to match windows AML interpreter behavior so this commit also got rid of support for executing code
containing forward references (except for package elements).
I've suggested a fix for the firmware in a separate email. So I would say that this issue is resolved after if Dan can run
his test successfully with the adjusted firmware.
If Dan's test is successful, we don’t need to revert these changes
Erik
>
> Note, that I'm willing to try any proposed fix patches on top. I just wanted to
> clarify that we have a simple fallback position if the debug starts dragging out.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-04-16 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180215210932.15490-1-erik.schmauss@intel.com>
[not found] ` <20180215210932.15490-6-erik.schmauss@intel.com>
2018-04-12 22:50 ` [PATCH v2 5/7] ACPICA: Integrate package handling with module-level code Dan Williams
2018-04-13 0:56 ` Dan Williams
2018-04-13 4:54 ` Schmauss, Erik
2018-04-13 7:42 ` Rafael J. Wysocki
2018-04-13 17:50 ` Dan Williams
2018-04-16 23:15 ` Schmauss, Erik [this message]
2018-04-16 23:21 ` Dan Williams
2018-04-17 0:05 ` Schmauss, Erik
2018-04-17 4:06 ` Dan Williams
2018-04-13 19:11 ` Moore, Robert
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=CF6A88132359CE47947DB4C6E1709ED539727606@ORSMSX110.amr.corp.intel.com \
--to=erik.schmauss@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.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).