All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Zheng, Lv" <lv.zheng@intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	"Moore, Robert" <robert.moore@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"devel@acpica.org" <devel@acpica.org>
Subject: Re: [PATCH] ACPICA: Log Exceptions and Errors as warning while loading extra tables
Date: Tue, 14 Mar 2017 12:54:21 +0100	[thread overview]
Message-ID: <bdc2deb1-6ab2-ef14-e402-a3b3bb745b61@redhat.com> (raw)
In-Reply-To: <9a6d4e50-41e7-28f6-b19d-f5f989da032d@redhat.com>

Hi,

On 14-03-17 09:56, Hans de Goede wrote:
> Hi,
>
> On 14-03-17 09:15, Zheng, Lv wrote:
>> Hi, Hans
>>
>>> From: Hans de Goede [mailto:hdegoede@redhat.com]
>>> Subject: Re: [PATCH] ACPICA: Log Exceptions and Errors as warning while loading extra tables
>>>
>>> Hi,
>>>
>>> On 13-03-17 10:52, Zheng, Lv wrote:
>>>> Hi, Hans
>>>>
>>>> For log level issue, is this fix useful for you?
>>>> https://github.com/acpica/acpica/pull/121/commits/a505d3942
>>>
>>> That fixes reloading already loaded tables, the problem I'm
>>> getting errors about its loading a different table with identical
>>> contents.
>>>
>>> I will look into your suggestion to do something similar to
>>> AcpiTbInstallStandardTable using AcpiTbCompareTables for the
>>> SSDT tables. I will send a new patch when I can make some time
>>> to look into this.
>>
>> I just completed a prototype here:
>> https://github.com/acpica/acpica/pull/121
>>
>> I guess the original "duplicate table check" couldn't cover static SSDTs.
>> Actually the duplicate table check should be a sanity check of table load.
>> And for table install, we should have a different sanity check like:
>> https://github.com/acpica/acpica/pull/121/commits/6e825cae5e5
>> I'm not sure if this is what you want.
>
> This checks for having 2 table_descriptors pointing to the same table
> (address in memory). But in my case there are 2 identical copies of
> the table at 2 different addresses in memory, so this won't work.
>
> After looking at this a bit myself, I think fixing this is actually
> quite easy (now that you've pointed me to acpi_tb_install_standard_table()
>
> I've come up with the attached patch to fix this. I will give this a test
> spin and then submit it officially (assuming it works).

Ok the approach of doing the check during acpi_tb_install_standard_table
does not work because then acpi_gbl_verify_table_checksum is false so
we are only loading the header of the table, that and we are not supposed
to load more data / use more mem this early, which the call to
acpi_tb_acquire_table() will do for the table being compared against.

So it looks like we will need to go with some version of my patch which
does the check later when acpi_gbl_verify_table_checksum is true.

Regards,

Hans

  reply	other threads:[~2017-03-14 11:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:36 [PATCH] ACPICA: Log Exceptions and Errors as warning while loading extra tables Hans de Goede
2017-03-02  2:03 ` Zheng, Lv
2017-03-02  2:03   ` [Devel] " Zheng, Lv
2017-03-02 15:27   ` Hans de Goede
2017-03-03  2:48     ` Zheng, Lv
2017-03-03  2:48       ` [Devel] " Zheng, Lv
2017-03-03 13:55       ` Hans de Goede
2017-03-13  9:52         ` Zheng, Lv
2017-03-13  9:52           ` [Devel] " Zheng, Lv
2017-03-13 10:06           ` Hans de Goede
2017-03-14  8:15             ` Zheng, Lv
2017-03-14  8:15               ` [Devel] " Zheng, Lv
2017-03-14  8:56               ` Hans de Goede
2017-03-14 11:54                 ` Hans de Goede [this message]
2017-03-15  1:16                 ` Zheng, Lv
2017-03-15  1:16                   ` [Devel] " Zheng, Lv
2018-01-11 19:28 [PATCH 0/1] " Hans de Goede
2018-01-11 19:28 ` [PATCH] " Hans de Goede
2018-01-12 10:25   ` Hans de Goede

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=bdc2deb1-6ab2-ef14-e402-a3b3bb745b61@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=devel@acpica.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@intel.com \
    /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.