This bug is awaiting verification that the linux-azure-
fips/6.8.0-1034.39+fips1 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-azure-fips' to
'verification-done-noble-linux-azure-fips'. If the problem still exists,
change the tag 'verification-needed-noble-linux-azure-fips' to
'verification-failed-noble-linux-azure-fips'.


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-azure-fips-v2 
verification-needed-noble-linux-azure-fips

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2114218

Title:
  [Arm64] High reboot time for 96 core Linux VMs

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Noble:
  Fix Released
Status in linux-azure source package in Oracular:
  Invalid
Status in linux-azure source package in Plucky:
  Invalid
Status in linux-azure source package in Questing:
  Invalid

Bug description:
  SRU Justification

  [ Impact ]

  * Microsoft request to fix long boot times on arm64 VMs with 96 cores.

  [ Fix ]

  * Clean cherry-pick of the following patches from upstream:
  * 5c63db59c5f8: "arm64: mm: Don't remap pgtables per-cont(pte|pmd) block"
  * 1fcb7cea8a5f: "arm64: mm: Batch dsb and isb when populating pgtables"
  * 0e9df1c905d8: "arm64: mm: Don't remap pgtables for allocate vs populat"

  [ Test Plan ]

  * Compile tested
  * Microsoft to test further

  [ Where problems could occur ]

  * Changes made to memory-management, which could have impacts across the 
memory subsystems.
  * Backport involved stripping out portions of 5-level paging, which was 
missing prerequisite
    commits. This has been validated, but if logic was not well-separated in 
the upstream commits,
    the changes for present paging might have some reliance on the 5-level 
paging changes.

  [ Other info ]

  * SF#00412644

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2114218/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to