AMD

perf: Add support for hardware breakpoint address masks

Bug #1117548 reported by Kim Naru
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AMD
Won't Fix
Medium
Kim Naru
linux (Ubuntu)
Fix Released
Undecided
James M. Leddy

Bug Description

The following patchset adds address masks to existing perf hardware
breakpoint mechanism to allow trapping on an address range (currently
only single address) on supported architectures.

perf uapi is updated, x86 AMD implementation (for AMD Family 16h and
beyond) is provided, and perf tool has been extended to do:

  $ perf stat -e mem:0x1000:w:0xf a.out
                              ^^^
                              "don't care" bit mask

  which will count writes to [0x1000 ~ 0x1010)

This patch is upstream but not accepted yet:

https://lkml.org/lkml/2012/12/12/261

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Is there any information if these patches have hit a maintainer's tree and if they will land in the v3.9 merge window? We'd prefer to pick these up from a more official upstream repo if possible. Thanks.

Revision history for this message
Kim Naru (kim-naru) wrote :

This patch will probably not get into Linux 3.9. We will try to get it into 3.10.

Revision history for this message
James M. Leddy (jm-leddy) wrote :

Hi Kim,

We're going to use 3.11 for saucy, is the patch in 3.11?

Revision history for this message
Kim Naru (kim-naru) wrote :

No it is not.

Changed in amd:
importance: Undecided → Medium
assignee: nobody → Kim Naru (kim-naru)
Revision history for this message
James M. Leddy (jm-leddy) wrote :

This looks to be on hold because I haven't seen anything since v2 of this patch:

http://thread.gmane.org/gmane.linux.kernel/1479542

Correct me if there is something more current.

Changed in amd:
status: New → Incomplete
status: Incomplete → In Progress
Revision history for this message
Kim Naru (kim-naru) wrote :

The code has not been acked by the maintainer.

Revision history for this message
James M. Leddy (jm-leddy) wrote :

Hi Kim,

It seems the maintainer had a few concerns that need to be addressed, probably in a v3 of this patchset. Is Jacob planning on doing a v3?

Changed in amd:
status: In Progress → Incomplete
information type: Proprietary → Private
information type: Private → Public
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1117548

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
James M. Leddy (jm-leddy) wrote :

Confirmed with Kim that Jacob is still working on this and is planning on resubmitting.

Changed in linux (Ubuntu):
assignee: nobody → James M. Leddy (jm-leddy)
Revision history for this message
Kim Naru (kim-naru) wrote :

Appears this will go into Linux 3.15.

Changed in amd:
status: Incomplete → Won't Fix
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.