RE: [PATCHv2] DSPBRIDGE: Include missing info in MMU Fault debugging trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ernesto

> @@ -2136,6 +2138,7 @@ dsp_status dump_dsp_stack(struct bridge_dev_context
> *bridge_context)
>  			total_size = MAX_MMU_DBGBUFF;
> 
>  		buffer = kzalloc(total_size, GFP_ATOMIC);
> +		buffer_beg = buffer;
>  		buffer_end =  buffer + total_size / 4;
> 
>  		if (!buffer) {

-- Shouldn't this check be present before the above 2 statements ?

>  		for (i = 0; buffer < buffer_end; i++, buffer++) {
>  			if ((*buffer > 0x01000000) && (node_find_addr(node_mgr,

-- Is 0x01000000 MAX_MMU_DBGBUFF ? 

Thank you,
Best regards,
Hari
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux