Alexey Kardashevskiy writes:
> On 06/30/2014 06:35 PM, Nikunj A Dadhania wrote:
>> PAPR compliant guest calls this in absence of kdump. This finally
>> reaches the guest and can be handled according to the policies set by
>> higher level tools(like taking dump) for further analysis by tools like
On 07/03/2014 01:41 PM, Alexey Kardashevskiy wrote:
> On 06/30/2014 06:35 PM, Nikunj A Dadhania wrote:
>> PAPR compliant guest calls this in absence of kdump. This finally
>> reaches the guest and can be handled according to the policies set by
>> higher level tools(like taking dump) for further an
On 06/30/2014 06:35 PM, Nikunj A Dadhania wrote:
> PAPR compliant guest calls this in absence of kdump. This finally
> reaches the guest and can be handled according to the policies set by
> higher level tools(like taking dump) for further analysis by tools like
> crash.
>
> Linux kernel calls ibm
> Am 01.07.2014 um 05:20 schrieb Nikunj A Dadhania :
>
> Alexander Graf writes:
>
>>> On 30.06.2014, at 17:49, Tyrel Datwyler
>>> wrote:
>>>
On 06/30/2014 01:35 AM, Nikunj A Dadhania wrote:
PAPR compliant guest calls this in absence of kdump. This finally
reaches the guest an
Alexander Graf writes:
> On 30.06.2014, at 17:49, Tyrel Datwyler
> wrote:
>
>> On 06/30/2014 01:35 AM, Nikunj A Dadhania wrote:
>>> PAPR compliant guest calls this in absence of kdump. This finally
>>> reaches the guest and can be handled according to the policies set by
>>> higher level tools(
On 30.06.2014, at 17:49, Tyrel Datwyler wrote:
> On 06/30/2014 01:35 AM, Nikunj A Dadhania wrote:
>> PAPR compliant guest calls this in absence of kdump. This finally
>> reaches the guest and can be handled according to the policies set by
>> higher level tools(like taking dump) for further anal
On 06/30/2014 01:35 AM, Nikunj A Dadhania wrote:
> PAPR compliant guest calls this in absence of kdump. This finally
> reaches the guest and can be handled according to the policies set by
> higher level tools(like taking dump) for further analysis by tools like
> crash.
>
> Linux kernel calls ibm
On 30.06.14 11:25, Nikunj A Dadhania wrote:
Alexander Graf writes:
Am 30.06.2014 um 10:35 schrieb Nikunj A Dadhania :
+static void rtas_ibm_os_term(PowerPCCPU *cpu,
+sPAPREnvironment *spapr,
+uint32_t token, uint32_t nargs,
+
Alexander Graf writes:
>> Am 30.06.2014 um 10:35 schrieb Nikunj A Dadhania :
>>
>> +static void rtas_ibm_os_term(PowerPCCPU *cpu,
>> +sPAPREnvironment *spapr,
>> +uint32_t token, uint32_t nargs,
>> +target_ulong
> Am 30.06.2014 um 10:35 schrieb Nikunj A Dadhania :
>
> PAPR compliant guest calls this in absence of kdump. This finally
> reaches the guest and can be handled according to the policies set by
> higher level tools(like taking dump) for further analysis by tools like
> crash.
>
> Linux kernel
PAPR compliant guest calls this in absence of kdump. This finally
reaches the guest and can be handled according to the policies set by
higher level tools(like taking dump) for further analysis by tools like
crash.
Linux kernel calls ibm,os-term when extended property of os-term is set.
This makes
11 matches
Mail list logo
