summaryrefslogtreecommitdiffstats
path: root/firmware/r128
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2010-08-11 16:42:48 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-08-24 15:26:31 +1000
commit7aa241fdcef2a1d6587fe4c390e9fdbfc767af28 (patch)
treed54e07498245696a16ef7702f28e32ca9efc0f03 /firmware/r128
parent4138d65333fa8961714441ed40229ea8cbeaf7e5 (diff)
downloadop-kernel-dev-7aa241fdcef2a1d6587fe4c390e9fdbfc767af28.zip
op-kernel-dev-7aa241fdcef2a1d6587fe4c390e9fdbfc767af28.tar.gz
powerpc: Fix bogus it_blocksize in VIO iommu code
When looking at some issues with the virtual ethernet driver I noticed that TCE allocation was following a very strange pattern: address 00e9000 length 2048 address 0409000 length 2048 <----- address 0429000 length 2048 address 0449000 length 2048 address 0469000 length 2048 address 0489000 length 2048 address 04a9000 length 2048 address 04c9000 length 2048 address 04e9000 length 2048 address 4009000 length 2048 <----- address 4029000 length 2048 Huge unexplained gaps in what should be an empty TCE table. It turns out it_blocksize, the amount we want to align the next allocation to, was c0000000fe903b20. Completely bogus. Initialise it to something reasonable in the VIO IOMMU code, and use kzalloc everywhere to protect against this when we next add a non compulsary field to iommu code and forget to initialise it. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'firmware/r128')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud