On Mon, Jul 14, 2014 at 04:22:26AM +0100, Liu hua wrote:
> On 2014/7/11 20:35, Will Deacon wrote:
> > On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
> >> So guys, Do you know a better way to do that?
> > What happens if, in the crash kernel, you disable the CPU interfaces
> >
On Mon, Jul 14, 2014 at 04:22:26AM +0100, Liu hua wrote:
On 2014/7/11 20:35, Will Deacon wrote:
On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
So guys, Do you know a better way to do that?
What happens if, in the crash kernel, you disable the CPU interfaces
(GICC_CTLR.ENABLE)
On 2014/7/11 20:35, Will Deacon wrote:
> [adding Marc]
>
> On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
>> For this version of GIC codes, kernel assumes that all the interrupt
>> status of GIC is inactive. So the kernel does not check this when
>> booting.
>>
>> This is no problem on
On 2014/7/11 20:35, Will Deacon wrote:
[adding Marc]
On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must sitations. But when kdump is deplayed.
And a panic occurs when a interrupt is being handled (may be PPI
and SPI). We have no
[adding Marc]
On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
> For this version of GIC codes, kernel assumes that all the interrupt
> status of GIC is inactive. So the kernel does not check this when
> booting.
>
> This is no problem on must sitations. But when kdump is deplayed.
>
[adding Marc]
On Fri, Jul 11, 2014 at 07:46:15AM +0100, Liu Hua wrote:
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must sitations. But when kdump is deplayed.
And a
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must sitations. But when kdump is deplayed.
And a panic occurs when a interrupt is being handled (may be PPI
and SPI). We have no
8 matches
Mail list logo