From: Lan Tianyu <tianyu.lan@intel.com>
To: rjw@rjwysocki.net, lenb@kernel.org
Cc: Lan Tianyu <tianyu.lan@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2] ACPI/NVS: Not save NVS region for new machine to accelerate S3
Date: Wed, 23 Jul 2014 14:42:33 +0800 [thread overview]
Message-ID: <1406097753-7398-1-git-send-email-tianyu.lan@intel.com> (raw)
In-Reply-To: <1405662922-23606-1-git-send-email-tianyu.lan@intel.com>
NVS region is saved and restored unconditionally for machines without
nvs_nosave quirk during S3. Tested some new machines and the operation
is not necessary. Saving NVS region also affects S2RAM speed. The time of
NVS saving and restoring depends on the size of NVS region and it consumes
7~10ms normally.
This patch is to make machines produced from 2012 to now not saving NVS region
to accelerate S3.
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
---
Change since V1:
Change the order between checking acpisleep quirk table and setting
the flag of nosaving nvs for S3.
drivers/acpi/sleep.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/acpi/sleep.c b/drivers/acpi/sleep.c
index b3e3cc7..54da4a3 100644
--- a/drivers/acpi/sleep.c
+++ b/drivers/acpi/sleep.c
@@ -322,6 +322,11 @@ static struct dmi_system_id acpisleep_dmi_table[] __initdata = {
static void acpi_sleep_dmi_check(void)
{
+ int year;
+
+ if (dmi_get_date(DMI_BIOS_DATE, &year, NULL, NULL) && year >= 2012)
+ acpi_nvs_nosave_s3();
+
dmi_check_system(acpisleep_dmi_table);
}
--
1.8.4.rc0.1.g8f6a3e5.dirty
prev parent reply other threads:[~2014-07-23 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 5:55 [PATCH] ACPI/NVS: Not save NVS region for new machines to accelerate S3 Lan Tianyu
2014-07-18 8:00 ` Chen, Gong
2014-07-21 2:14 ` Lan Tianyu
2014-07-21 5:01 ` Chen, Gong
2014-07-21 5:54 ` Lan Tianyu
2014-07-21 6:25 ` Chen, Gong
2014-07-21 7:37 ` Lan Tianyu
2014-07-22 23:40 ` Rafael J. Wysocki
2014-07-23 5:35 ` Lan Tianyu
2014-07-23 6:42 ` Lan Tianyu [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=1406097753-7398-1-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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