AWS: enable FPGA support in amd64 AWS kernels

Bug #1898781 reported by Kamal Mostafa
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-aws (Ubuntu)
Fix Released
Fix Released
Kamal Mostafa

Bug Description

CONFIG_FPGA needs to be enabled in linux-aws amd64 kernels (thereby supplying the fpga-mgr module), to support the AWS F1 instance type.

Delivering the fpga-mgr module via the 'linux-modules-extras' package is acceptable.

This config change only needs to be specifically applied to linux-aws/focal, since:

  linux-aws/bionic (aws-5.4) will pick it up from focal;
  linux-aws-groovy already has it enabled;
  linux-aws-xenial cannot support F1 anyway.



 * Since fpga-mgr is inadvertently omitted from linux-aws, use of the F1 instance type requires the user to manually install linux-virtual or linux-generic, which is an annoyance.

 * This patch just enables the module in linux-aws as we do for other kernels.

 * Fwiw, fpga-mgr is actually (needlessly) already enabled for linux-aws/arm64 but disabled for linux-aws/amd64 (where its needed for F1).

[Test Case]

 * Install the linux-modules-extras package; modprobe fpga-mgr.

[Regression Potential]

 * None.

description: updated
description: updated
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

I have verified that the patch ^^ properly enables fpga-mgr on an AWS F1 instance.

Stefan Bader (smb)
Changed in linux-aws (Ubuntu Focal):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Kamal Mostafa (kamalmostafa)
Changed in linux-aws (Ubuntu):
assignee: Kamal Mostafa (kamalmostafa) → nobody
status: In Progress → Confirmed
status: Confirmed → Fix Released
description: updated
Ian May (ian-may)
Changed in linux-aws (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-aws - 5.4.0-1029.30

linux-aws (5.4.0-1029.30) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1029.30 -proposed tracker (LP: #1900671)

  * CVE-2020-12351 // CVE-2020-12352 // CVE-2020-24490
    - [Config] [aws] Disable BlueZ highspeed support

  * EFA: add support for 0xefa1 devices (LP: #1896791)
    - RDMA/efa: Expose maximum TX doorbell batch
    - RDMA/efa: Expose minimum SQ size
    - RDMA/efa: User/kernel compatibility handshake mechanism
    - RDMA/efa: Add EFA 0xefa1 PCI ID

  * aws: enable PCI write-combine for arm64 (LP: #1893817)
    - SAUCE: arm64: Enable PCI write-combine resources under sysfs

  * AWS: enable FPGA support in amd64 AWS kernels (LP: #1898781)
    - [Config] aws: enable FPGA for amd64 also

  [ Ubuntu: 5.4.0-52.57 ]

  * focal/linux: 5.4.0-52.57 -proposed tracker (LP: #1899920)
  * CVE-2020-12351 // CVE-2020-12352 // CVE-2020-24490
    - Bluetooth: Disable High Speed by default
    - Bluetooth: MGMT: Fix not checking if BT_HS is enabled
    - [Config] Disable BlueZ highspeed support
  * CVE-2020-12351
    - Bluetooth: L2CAP: Fix calling sk_filter on non-socket based channel
  * CVE-2020-12352
    - Bluetooth: A2MP: Fix not initializing all members

 -- Andrea Righi <email address hidden> Tue, 20 Oct 2020 11:32:33 +0200

Changed in linux-aws (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers