summaryrefslogtreecommitdiffstats
path: root/arch/sh/include
diff options
context:
space:
mode:
authorFrederic Weisbecker <fweisbec@gmail.com>2010-04-13 00:32:30 +0200
committerFrederic Weisbecker <fweisbec@gmail.com>2010-05-01 04:32:12 +0200
commitf93a20541134fa767e8dc4eb32e956d30b9f6b92 (patch)
treeda262316510683286dcaf1dbc2e4dddc5ac44ba3 /arch/sh/include
parent0102752e4c9e0655b39734550d4c35327954f7f9 (diff)
downloadop-kernel-dev-f93a20541134fa767e8dc4eb32e956d30b9f6b92.zip
op-kernel-dev-f93a20541134fa767e8dc4eb32e956d30b9f6b92.tar.gz
hw-breakpoints: Handle breakpoint weight in allocation constraints
Depending on their nature and on what an arch supports, breakpoints may consume more than one address register. For example a simple absolute address match usually only requires one address register. But an address range match may consume two registers. Currently our slot allocation constraints, that tend to reflect the limited arch's resources, always consider that a breakpoint consumes one slot. Then provide a way for archs to tell us the weight of a breakpoint through a new hw_breakpoint_weight() helper. This weight will be computed against the generic allocation constraints instead of a constant value. Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Acked-by: Paul Mundt <lethal@linux-sh.org> Cc: Will Deacon <will.deacon@arm.com> Cc: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com> Cc: K. Prasad <prasad@linux.vnet.ibm.com> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Paul Mackerras <paulus@samba.org> Cc: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/sh/include')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud