Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
Am Donnerstag, den 15.10.2015, 16:32 +0100 schrieb Russell King - ARM Linux: > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > Install a non-faulting handler just before unmasking imprecise aborts > > and switch back to the regular one after unmasking is done. > > > > This catches any pending imprecise abort that the firmware/bootloader > > may have left behind that would normally crash the kernel at that point. > > As there are apparently a lot of bootlaoders out there that do such a > > thing it makes sense to handle it in the common startup code. > > > > Signed-off-by: Lucas Stach> > Much better. Please feel free to add it to the patch system, thanks. > > I think, given that the original seems to be breaking platforms, this > patch needs to go into -rc kernels, right? > Okay, this is in the patch system as patch 8447/1 now. As Russell hasn't said whether he would like to pick up the platform patches I've omitted them for now and would ask the platform maintainers to pick them up themselves for kernel 4.4. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
Am Donnerstag, den 15.10.2015, 16:32 +0100 schrieb Russell King - ARM Linux: > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > Install a non-faulting handler just before unmasking imprecise aborts > > and switch back to the regular one after unmasking is done. > > > > This catches any pending imprecise abort that the firmware/bootloader > > may have left behind that would normally crash the kernel at that point. > > As there are apparently a lot of bootlaoders out there that do such a > > thing it makes sense to handle it in the common startup code. > > > > Signed-off-by: Lucas Stach> > Much better. Please feel free to add it to the patch system, thanks. > Do you feel like taking patches 2 and 3 through your tree too, given that they are already acked by the platform maintainers, or should they pick them up themselves? > I think, given that the original seems to be breaking platforms, this > patch needs to go into -rc kernels, right? > No, the original patch is only queued for 4.4, so the regression is only in -next. This patch only needs to make it into your 4.4 pull request. Thanks, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > Install a non-faulting handler just before unmasking imprecise aborts > and switch back to the regular one after unmasking is done. > > This catches any pending imprecise abort that the firmware/bootloader > may have left behind that would normally crash the kernel at that point. > As there are apparently a lot of bootlaoders out there that do such a > thing it makes sense to handle it in the common startup code. > > Signed-off-by: Lucas StachMuch better. Please feel free to add it to the patch system, thanks. I think, given that the original seems to be breaking platforms, this patch needs to go into -rc kernels, right? -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
* Russell King - ARM Linux[151015 08:37]: > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > Install a non-faulting handler just before unmasking imprecise aborts > > and switch back to the regular one after unmasking is done. > > > > This catches any pending imprecise abort that the firmware/bootloader > > may have left behind that would normally crash the kernel at that point. > > As there are apparently a lot of bootlaoders out there that do such a > > thing it makes sense to handle it in the common startup code. > > > > Signed-off-by: Lucas Stach > > Much better. Please feel free to add it to the patch system, thanks. > > I think, given that the original seems to be breaking platforms, this > patch needs to go into -rc kernels, right? Hmm do we still see a trace where the issue happened though with this one? What I though wes something pending from the bootloader, turned out to be a bogus SRAM init code that I was able to easily fix with the trace. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
On Thu, Oct 15, 2015 at 08:39:15AM -0700, Tony Lindgren wrote: > * Russell King - ARM Linux[151015 08:37]: > > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > > Install a non-faulting handler just before unmasking imprecise aborts > > > and switch back to the regular one after unmasking is done. > > > > > > This catches any pending imprecise abort that the firmware/bootloader > > > may have left behind that would normally crash the kernel at that point. > > > As there are apparently a lot of bootlaoders out there that do such a > > > thing it makes sense to handle it in the common startup code. > > > > > > Signed-off-by: Lucas Stach > > > > Much better. Please feel free to add it to the patch system, thanks. > > > > I think, given that the original seems to be breaking platforms, this > > patch needs to go into -rc kernels, right? > > Hmm do we still see a trace where the issue happened though with this > one? That's not the intention of this specific patch. This is solely to detect the bootloader induced imprecise exception, nothing more. A backtrace for that won't be useful in any shape or form - in fact, the backtrace will be well known (it'll be from the site where the imprecise exceptions are unmasked.) Any imprecise exception which happens after this will be handled in the normal way: it'll raise a kernel oops, and that will have all the details that a kernel oops normally has. The difference is, rather than the boot loader provoking the kernel to oops at this point, we're able to report the event and continue on. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask
* Russell King - ARM Linux[151015 09:11]: > On Thu, Oct 15, 2015 at 08:39:15AM -0700, Tony Lindgren wrote: > > * Russell King - ARM Linux [151015 08:37]: > > > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > > > Install a non-faulting handler just before unmasking imprecise aborts > > > > and switch back to the regular one after unmasking is done. > > > > > > > > This catches any pending imprecise abort that the firmware/bootloader > > > > may have left behind that would normally crash the kernel at that point. > > > > As there are apparently a lot of bootlaoders out there that do such a > > > > thing it makes sense to handle it in the common startup code. > > > > > > > > Signed-off-by: Lucas Stach > > > > > > Much better. Please feel free to add it to the patch system, thanks. > > > > > > I think, given that the original seems to be breaking platforms, this > > > patch needs to go into -rc kernels, right? > > > > Hmm do we still see a trace where the issue happened though with this > > one? > > That's not the intention of this specific patch. > > This is solely to detect the bootloader induced imprecise exception, > nothing more. A backtrace for that won't be useful in any shape or > form - in fact, the backtrace will be well known (it'll be from the > site where the imprecise exceptions are unmasked.) > > Any imprecise exception which happens after this will be handled in > the normal way: it'll raise a kernel oops, and that will have all the > details that a kernel oops normally has. OK makes sense. > The difference is, rather than the boot loader provoking the kernel to > oops at this point, we're able to report the event and continue on. OK Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html