firmware: cs_dsp: Fix fragmentation regression in firmware download
Subsystems (2)
Richard Fitzgerald
maintainerPATCH 1/1 firmware: cs_dsp: Fix fragmentation regression in firmware download
Use vmalloc() instead of kmalloc(..., GFP_DMA) to alloc the temporary buffer for firmware download blobs. This avoids the problem that a heavily fragmented system cannot allocate enough physically-contiguous memory for a large blob.
The redundant alloc buffer mechanism was removed in commit 900baa6e7bb0 ("firmware: cs_dsp: Remove redundant download buffer allocator"). While doing that I was overly focused on the possibility of the underlying bus requiring DMA-safe memory. So I used GFP_DMA kmalloc()s. I failed to notice that the code I was removing used vmalloc(). This creates a regression.
Way back in 2014 the problem of fragmentation with kmalloc()s was fixed by commit cdcd7f728753 ("ASoC: wm_adsp: Use vmalloc to allocate firmware download buffer").
Although we don't need physically-contiguous memory, we don't know if the bus needs some particular alignment of the buffers. Since the change in 2014, the firmware download has always used whatever alignment vmalloc() returns. To avoid introducing a new problem, the temporary buffer is still used, to keep the same alignment of pointers passed to regmap_raw_write().
--- drivers/firmware/cirrus/cs_dsp.c | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-)
drivers/firmware/cirrus/cs_dsp.c +18 -6
@@ -1649,11 +1649,17 @@ static int cs_dsp_load(struct cs_dsp *dsp, const struct firmware *firmware, region_name);if (reg) { +/* +* Although we expect the underlying bus does not require +* physically-contiguous buffers, we pessimistically use +* a temporary buffer instead of trusting that the +* alignment of region->data is ok. +*/ region_len =le32_to_cpu (region->len);if (region_len > buf_len) { buf_len =round_up (region_len,PAGE_SIZE ); -kfree (buf); - buf =kmalloc (buf_len,GFP_KERNEL |GFP_DMA ); +vfree (buf); + buf =vmalloc (buf_len);if (!buf) { ret = -ENOMEM ; goto out_fw;
@@ -1682,7 +1688,7 @@ static int cs_dsp_load(struct cs_dsp *dsp, const struct firmware *firmware, ret =0 ; out_fw: -kfree (buf); +vfree (buf);if (ret == -EOVERFLOW )cs_dsp_err (dsp,"%s: file content overflows file data\n" , file);
@@ -2370,11 +2376,17 @@ static int cs_dsp_load_coeff(struct cs_dsp *dsp, const struct firmware *firmware }if (reg) { +/* +* Although we expect the underlying bus does not require +* physically-contiguous buffers, we pessimistically use +* a temporary buffer instead of trusting that the +* alignment of blk->data is ok. +*/ region_len =le32_to_cpu (blk->len);if (region_len > buf_len) { buf_len =round_up (region_len,PAGE_SIZE ); -kfree (buf); - buf =kmalloc (buf_len,GFP_KERNEL |GFP_DMA ); +vfree (buf); + buf =vmalloc (buf_len);if (!buf) { ret = -ENOMEM ; goto out_fw;
@@ -2405,7 +2417,7 @@ static int cs_dsp_load_coeff(struct cs_dsp *dsp, const struct firmware *firmware ret =0 ; out_fw: -kfree (buf); +vfree (buf);if (ret == -EOVERFLOW )cs_dsp_err (dsp,"%s: file content overflows file data\n" , file);
Signature · 1 line
2.47.3
Quoted 17 lines · Richard Fitzgerald
Use
vmalloc()instead ofkmalloc(..., GFP_DMA)to alloc the temporary buffer for firmware download blobs. This avoids the problem that a heavily fragmented system cannot allocate enough physically-contiguous memory for a large blob.The redundant alloc buffer mechanism was removed in commit
900baa6e7bb0("firmware:cs_dsp: Remove redundant download buffer allocator"). While doing that I was overly focused on the possibility of the underlying bus requiring DMA-safe memory. So I usedGFP_DMAkmalloc()s. I failed to notice that the code I was removing usedvmalloc(). This creates a regression.Way back in 2014 the problem of fragmentation with kmalloc()s was fixed by commit
cdcd7f728753("ASoC:wm_adsp: Use vmalloc to allocate firmware download buffer").
Quoted 8 lines
Although we don't need physically-contiguous memory, we don't know if the bus needs some particular alignment of the buffers. Since the change in 2014, the firmware download has always used whatever alignment
vmalloc()returns. To avoid introducing a new problem, the temporary buffer is still used, to keep the same alignment of pointers passed toregmap_raw_write().Signed-off-by Richard Fitzgerald <[email protected]>Fixes 900baa6e7bb0 ("firmware: cs_dsp: Remove redundant download buffer allocator")
FYI, if the data isn't always large, kvmalloc() could be a better alternative, which is a hybrid for both speed and size, too.
Takashi
Richard Fitzgerald
maintainerQuoted 25 lines · Takashi Iwai
Quoted 23 lines · Richard Fitzgerald
Use
vmalloc()instead ofkmalloc(..., GFP_DMA)to alloc the temporary buffer for firmware download blobs. This avoids the problem that a heavily fragmented system cannot allocate enough physically-contiguous memory for a large blob.The redundant alloc buffer mechanism was removed in commit
900baa6e7bb0("firmware:cs_dsp: Remove redundant download buffer allocator"). While doing that I was overly focused on the possibility of the underlying bus requiring DMA-safe memory. So I usedGFP_DMAkmalloc()s. I failed to notice that the code I was removing usedvmalloc(). This creates a regression.Way back in 2014 the problem of fragmentation with kmalloc()s was fixed by commit
cdcd7f728753("ASoC:wm_adsp: Use vmalloc to allocate firmware download buffer").Although we don't need physically-contiguous memory, we don't know if the bus needs some particular alignment of the buffers. Since the change in 2014, the firmware download has always used whatever alignment
vmalloc()returns. To avoid introducing a new problem, the temporary buffer is still used, to keep the same alignment of pointers passed toregmap_raw_write().
Quoted 8 lines
Quoted 2 lines
Signed-off-by Richard Fitzgerald <[email protected]>Fixes 900baa6e7bb0 ("firmware: cs_dsp: Remove redundant download buffer allocator")FYI, if the data isn't always large,
kvmalloc()could be a better alternative, which is a hybrid for both speed and size, too.Takashi
I originally did that, but as this is a bugfix for backporting I decided not to risk introducing a change inside a bugfix. The original code was vmalloc() so I have corrected back to what the original code did.
vmalloc() appears to allocate whole pages, on PAGE_SIZE boundary but kvmalloc() could allocate on a smaller boundary. I know that kmalloc() memory is claimed to be be DMA-safe. But I don't want to risk fixing one regression and introducing a new regression into stable kernels.
It's on my to-do list to have a look at using kvmalloc(), and possibly skipping the buffer if the source data is already aligned on ARCH_KMALLOC_MINALIGN. But that's for future kernel releases.
Quoted 40 lines · Richard Fitzgerald
Quoted 25 lines · Takashi Iwai
Quoted 23 lines · Richard Fitzgerald
Use
vmalloc()instead ofkmalloc(..., GFP_DMA)to alloc the temporary buffer for firmware download blobs. This avoids the problem that a heavily fragmented system cannot allocate enough physically-contiguous memory for a large blob.The redundant alloc buffer mechanism was removed in commit
900baa6e7bb0("firmware:cs_dsp: Remove redundant download buffer allocator"). While doing that I was overly focused on the possibility of the underlying bus requiring DMA-safe memory. So I usedGFP_DMAkmalloc()s. I failed to notice that the code I was removing usedvmalloc(). This creates a regression.Way back in 2014 the problem of fragmentation with kmalloc()s was fixed by commit
cdcd7f728753("ASoC:wm_adsp: Use vmalloc to allocate firmware download buffer").Although we don't need physically-contiguous memory, we don't know if the bus needs some particular alignment of the buffers. Since the change in 2014, the firmware download has always used whatever alignment
vmalloc()returns. To avoid introducing a new problem, the temporary buffer is still used, to keep the same alignment of pointers passed toregmap_raw_write().Quoted 8 lines
Quoted 2 lines
Signed-off-by Richard Fitzgerald <[email protected]>Fixes 900baa6e7bb0 ("firmware: cs_dsp: Remove redundant download buffer allocator")FYI, if the data isn't always large,
kvmalloc()could be a better alternative, which is a hybrid for both speed and size, too.Takashi
I originally did that, but as this is a bugfix for backporting I decided not to risk introducing a change inside a bugfix. The original code was
vmalloc()so I have corrected back to what the original code did.
Quoted 8 lines
vmalloc()appears to allocate whole pages, onPAGE_SIZEboundary butkvmalloc()could allocate on a smaller boundary. I know thatkmalloc()memory is claimed to be be DMA-safe. But I don't want to risk fixing one regression and introducing a new regression into stable kernels.It's on my to-do list to have a look at using
kvmalloc(), and possibly skipping the buffer if the source data is already aligned onARCH_KMALLOC_MINALIGN. But that's for future kernel releases.
OK, then the change sounds reasonable. Thanks for explanation!
Takashi
Quoted 5 lines · Richard Fitzgerald
Use
vmalloc()instead ofkmalloc(..., GFP_DMA)to alloc the temporary buffer for firmware download blobs. This avoids the problem that a heavily fragmented system cannot allocate enough physically-contiguous memory for a large blob.
Quoted 8 lines
The redundant alloc buffer mechanism was removed in commit
900baa6e7bb0("firmware:cs_dsp: Remove redundant download buffer allocator"). While doing that I was overly focused on the possibility of the underlying bus requiring DMA-safe memory. So I usedGFP_DMAkmalloc()s. I failed to notice that the code I was removing usedvmalloc(). This creates a regression.[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] firmware: cs_dsp: Fix fragmentation regression in firmware download
commit: facfdef64d11c08e6f1e69d02a0b87cb74cee0f5
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark