From: "Ni, Ray via groups.io" <ray.ni=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"zhangchen@loongson.cn" <zhangchen@loongson.cn>
Cc: gaoliming <gaoliming@byosoft.com.cn>, lichao <lichao@loongson.cn>,
钱东彦 <qiandongyan@loongson.cn>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Problems with modifying variables after S4 recovery
Date: Thu, 23 Jan 2025 03:39:11 +0000 [thread overview]
Message-ID: <MN6PR11MB82440D6B54AB3F43AFC8B9358CE02@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <316709e6.1c917.194736e03ba.Coremail.zhangchen@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]
I checked the ACPI spec and it says the UEFI RuntimeCode/RuntimeData is treated as AddressRangeReserved type by OS (see ACPI spec 15.3 UEFI GetMemoryMap() Boot Services Function)
I think the AddressRangeReserved type is NOT restored by OS when resuming from S4.
Can you double check?
Thanks,
Ray
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of 张辰 <zhangchen@loongson.cn>
Sent: Friday, January 17, 2025 16:42
To: devel@edk2.groups.io <devel@edk2.groups.io>
Cc: gaoliming <gaoliming@byosoft.com.cn>; lichao <lichao@loongson.cn>; 钱东彦 <qiandongyan@loongson.cn>; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: [edk2-devel] Problems with modifying variables after S4 recovery
Hello,
An issue regarding the variable has been encountered on the LoongArch platform. Modifying the variable using efivar after S4 resume will cause data corruption in the flash.
It was found that when starting from S4, the BIOS might write to the variable. After the system resumes, the data in the runtime memory will also be restored, resulting in inconsistent data between that in the VARIABLE_MODULE_GLOBAL structure and the actual data. There is already data in the flash area corresponding to NonVolatileLastVariableOffset.
It's suspected that there will also be problems on other platforms. I'd like to know whether other platforms have encountered similar problems and if there are any solutions?
Thanks
________________________________
zhangchen@loongson.cn
本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121040): https://edk2.groups.io/g/devel/message/121040
Mute This Topic: https://groups.io/mt/110712299/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 8871 bytes --]
prev parent reply other threads:[~2025-01-23 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 8:42 [edk2-devel] Problems with modifying variables after S4 recovery 张辰
2025-01-23 3:39 ` Ni, Ray via groups.io [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-list 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=MN6PR11MB82440D6B54AB3F43AFC8B9358CE02@MN6PR11MB8244.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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