Hi Jacob, On Tue, Apr 23, 2013 at 08:57:02AM +0100, Jacob Shin wrote: > Some architectures (for us, AMD Family 16h) allow for "don't care" bit > mask to further qualify a hardware breakpoint address, in order to > trap on range of addresses. Update perf uapi to add bp_addr_mask field.
arm and arm64 have a similar feature to this, whereby we currently have to translate the bp_len field into a mask, which is all the hardware understands. Unlike what you describe, our mask indicates the bytes we *are* interested in, but I think we could make use of the same functionality that you're introducing here. There are some funky restrictions on the alignment of the base address, but we can detect those and tell userspace where to go if it tries any funny stuff. Can you see a problem if I simply invert the mask? Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
