This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1046.51~20.04.1 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-focal-linux-
aws-5.15' to
This bug was fixed in the package linux-aws - 6.2.0-1002.2
---
linux-aws (6.2.0-1002.2) lunar; urgency=medium
* lunar/linux-aws: 6.2.0-1002.2 -proposed tracker (LP: #2011518)
-- Paolo Pisati Tue, 14 Mar 2023 11:04:29
+0100
** Changed in: linux-aws (Ubuntu Lunar)
Status:
This bug was fixed in the package linux-aws - 5.15.0-1030.34
---
linux-aws (5.15.0-1030.34) jammy; urgency=medium
* jammy/linux-aws: 5.15.0-1030.34 -proposed tracker (LP: #2003424)
[ Ubuntu: 5.15.0-60.66 ]
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
*
This bug is awaiting verification that the linux-
aws-5.19/5.19.0-1019.20~22.04.1 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' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.19.0-1018.19
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-kinetic' to 'verification-done-kinetic'. If the
problem still
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification
** Changed in: linux-aws (Ubuntu Jammy)
Status: Fix Committed => In Progress
** Changed in: linux-aws (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Kinetic)
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
Status in linux package in Ubuntu:
Fix Released
Status in
This bug was fixed in the package linux - 4.19.0-12.13
---
linux (4.19.0-12.13) disco; urgency=medium
* linux: 4.19.0-12.13 -proposed tracker (LP: #1813664)
* kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
* Disco update:
This bug was fixed in the package linux - 4.18.0-14.15
---
linux (4.18.0-14.15) cosmic; urgency=medium
* linux: 4.18.0-14.15 -proposed tracker (LP: #1811406)
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: Avoid lock contention and thundering
This bug was fixed in the package linux - 4.15.0-44.47
---
linux (4.15.0-44.47) bionic; urgency=medium
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to
Performance on NVMe has increased a lot.
-update kernel
Run status group 0 (all jobs):
READ: bw=1358MiB/s (1424MB/s), 1358MiB/s-1358MiB/s (1424MB/s-1424MB/s),
io=133GiB (142GB), run=19-19msec
-proposed kernel
Run status group 0 (all jobs):
READ: bw=1406MiB/s (1475MB/s),
** Description changed:
[Impact]
The Intel IOMMU driver provides an option for strict mode. When disabled,
batching of IOTLB flush operations is permitted, allowing the user to trade-off
isolation for improved performance. Ubuntu's kernel currently lacks a parity
for this feature for ARM.
This bug is awaiting verification that the 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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the 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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
Status in
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806488
Title:
Support non-strict iommu mode on arm64
Status in
** Description changed:
[Impact]
- There's a significant performance gain to be had by removing the need to
flush the IOMMU TLB on every unmap. I'm seeing a 25% performance gain w/ fio
reads on a single NVMe device. This mode of operation is available for x86 via
the "intel_iommu=strict"
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
**
25 matches
Mail list logo
