summaryrefslogtreecommitdiff
path: root/sound/soc/codecs/dmic.c
diff options
context:
space:
mode:
Diffstat (limited to 'sound/soc/codecs/dmic.c')
0 files changed, 0 insertions, 0 deletions
xt.git/diff/?id=04cdf13e34e912dcab9a94f391e15b2c26dfd0a2&id2=1995876a06bcf6f9f7d7b699bdbf387831679771'>Diffstat (limited to 'tools/testing/selftests/powerpc/alignment/Makefile')ef='/cgit.cgi/linux/net-next.git/tree/tools/usb/ffs-aio-example/multibuff?h=nds-private-remove&id=910170442944e1f8674fd5ddbeeb8ccd1877ea98'>tools/usb/ffs-aio-example/multibuff
parent1c387188c60f53b338c20eee32db055dfe022a9b (diff)
iommu/vt-d: Fix PASID table allocation
Somehow I ended up with an off-by-three error in calculating the size of the PASID and PASID State tables, which triggers allocations failures as those tables unfortunately have to be physically contiguous. In fact, even the *correct* maximum size of 8MiB is problematic and is wont to lead to allocation failures. Since I have extracted a promise that this *will* be fixed in hardware, I'm happy to limit it on the current hardware to a maximum of 0x20000 PASIDs, which gives us 1MiB tables — still not ideal, but better than before. Reported by Mika Kuoppala <mika.kuoppala@linux.intel.com> and also by Xunlei Pang <xlpang@redhat.com> who submitted a simpler patch to fix only the allocation (and not the free) to the "correct" limit... which was still problematic. Signed-off-by: David Woodhouse <dwmw2@infradead.org> Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/usb/ffs-aio-example/multibuff')