[Impact]
For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf.
To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so.
[Test Plan]
Install linux-tools-aws, check for libperf-jvmti.so
[Where problems could occur]
Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression.
SRU Justification
[Impact]
For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf.
To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so.
[Test Plan]
Install linux-tools-aws, check for libperf-jvmti.so
[Where problems could occur]
Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression.