From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-efi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH] efi/libstub: arm64: avoid SetVirtualAddressMap() when possible #forregzbot
Date: Sun, 23 Oct 2022 16:58:18 +0200 [thread overview]
Message-ID: <a7eb41bf-3503-3057-783e-205ec4c2dc96@leemhuis.info> (raw)
In-Reply-To: <9c06c75d-5079-dd27-6533-c053c986083e@leemhuis.info>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 20.10.22 14:39, Thorsten Leemhuis wrote:
>> After entering 6.1-rc1 the efi runtime services is not working on my platform:
>>
>> [ 0.054039] Remapping and enabling EFI services.
>> [ 0.054043] UEFI virtual mapping missing or invalid -- runtime services will not be available
>>
>> Not sure this patch is the root cause since I see some refactor of efi codes in 6.1-rc1,
>> but simply reverting this make EFI runtime services works again. Tested on HiSilicon's
>> Kunpeng 920 arm64 server using 48 bit VA address:
>
> #regzbot ^introduced d3549a938b73f203ef522562ae9f2d38aa43d234
> #regzbot title efi/libstub: arm64: efi runtime services stopped working
> #regzbot ignore-activity
#regzbot fixed-by: 37926f96302d8b6
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-23 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 10:18 [PATCH] efi/libstub: arm64: avoid SetVirtualAddressMap() when possible Ard Biesheuvel
2022-09-16 10:20 ` Ard Biesheuvel
2022-10-19 3:24 ` Yicong Yang
2022-10-20 12:39 ` Thorsten Leemhuis
2022-10-20 13:04 ` Ard Biesheuvel
2022-10-21 1:59 ` Yicong Yang
2022-10-23 14:58 ` Thorsten Leemhuis [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=a7eb41bf-3503-3057-783e-205ec4c2dc96@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).