aws: Backport linear memory map change

Bug #2069352 reported by Philip Cox
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-aws (Ubuntu)
Fix Released
Undecided
Philip Cox
Jammy
Fix Committed
Undecided
Philip Cox
Noble
Fix Committed
Undecided
Philip Cox

Bug Description

SRU Justification:

[Impact]

AWS discovered an issue of long EC2 instance launch times on the upcoming R8g instance types.

[Fix]

They have identified the following fixes that address this issue:

* https://<email address hidden><email address hidden>/
* https://<email address hidden><email address hidden>/

They would like this fixced in the jammy, and noble kernels.

For reference, here are the links to the above patches in 6.10-rc3:

* arm64: mm: Don't remap pgtables per-cont(pte|pmd) block
https://github.com/torvalds/linux/commit/5c63db59c5f89925add57642be4f789d0d671ccd
* arm64: mm: Batch dsb and isb when populating pgtables
https://github.com/torvalds/linux/commit/1fcb7cea8a5f7747e02230f816c2c80b060d9517

AWS has requested only the first two patches of the series of three patches be back ported.

[Test Plan]
I have tested this, as has AWS.

[Where problems could occur]
With the reordering of tlb invalidation and memory barriers, there is some risk, but this chance for regressions on this change is fairly small as the scope is fairly narrow.

[Other info]
SF# 00387444

Philip Cox (philcox)
Changed in linux-aws (Ubuntu):
status: New → Fix Released
Philip Cox (philcox)
Changed in linux-aws (Ubuntu Noble):
assignee: nobody → Philip Cox (philcox)
Changed in linux-aws (Ubuntu Jammy):
assignee: nobody → Philip Cox (philcox)
status: New → In Progress
Changed in linux-aws (Ubuntu Noble):
status: New → In Progress
Philip Cox (philcox)
description: updated
Philip Cox (philcox)
Changed in linux-aws (Ubuntu Jammy):
status: In Progress → Fix Committed
Changed in linux-aws (Ubuntu Noble):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.15.0-1065.71 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy-linux-aws'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/6.8.0-1011.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-aws' to 'verification-done-noble-linux-aws'. If the problem still exists, change the tag 'verification-needed-noble-linux-aws' to 'verification-failed-noble-linux-aws'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-aws-v2 verification-needed-noble-linux-aws
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.