* Change the fix for KDB not defined build problem by changing
the kgdb_nmicallin() interface to include the KDB specific
reason code. This removes a dependency on KDB in the debug
core. Also requires a change the call in from UV NMI handler.
* Fix some problems found by the kbuild test robot.
* Fix UV call into kgdb to depend only on whether KGDB is defined
and not both KGDB and KDB. This allows the power nmi command
to use the gdb remote connection if enabled. Note new action
of 'kgdb' needs to be set as well to indicate user wants to
wait for gdb to be connected. If it's set to 'kdb' then an
error message is displayed if KDB is not configured.
--
--
* Mike Travis <[email protected]> wrote:
>
> * Change the fix for KDB not defined build problem by changing
> the kgdb_nmicallin() interface to include the KDB specific
> reason code. This removes a dependency on KDB in the debug
> core. Also requires a change the call in from UV NMI handler.
>
> * Fix some problems found by the kbuild test robot.
>
> * Fix UV call into kgdb to depend only on whether KGDB is defined
> and not both KGDB and KDB. This allows the power nmi command
> to use the gdb remote connection if enabled. Note new action
> of 'kgdb' needs to be set as well to indicate user wants to
> wait for gdb to be connected. If it's set to 'kdb' then an
> error message is displayed if KDB is not configured.
> --
This looks better.
Jason, any objections?
Thanks,
Ingo
On 10/19/2013 1:56 AM, Ingo Molnar wrote:
>
> * Mike Travis <[email protected]> wrote:
>
>>
>> * Change the fix for KDB not defined build problem by changing
>> the kgdb_nmicallin() interface to include the KDB specific
>> reason code. This removes a dependency on KDB in the debug
>> core. Also requires a change the call in from UV NMI handler.
>>
>> * Fix some problems found by the kbuild test robot.
>>
>> * Fix UV call into kgdb to depend only on whether KGDB is defined
>> and not both KGDB and KDB. This allows the power nmi command
>> to use the gdb remote connection if enabled. Note new action
>> of 'kgdb' needs to be set as well to indicate user wants to
>> wait for gdb to be connected. If it's set to 'kdb' then an
>> error message is displayed if KDB is not configured.
>> --
>
> This looks better.
>
> Jason, any objections?
>
> Thanks,
>
> Ingo
>
I haven't heard anything back about this update. Were there
objections? Looks like another merge window is closing?
Thanks,
Mike
* Mike Travis <[email protected]> wrote:
> On 10/19/2013 1:56 AM, Ingo Molnar wrote:
> >
> > * Mike Travis <[email protected]> wrote:
> >
> >>
> >> * Change the fix for KDB not defined build problem by changing
> >> the kgdb_nmicallin() interface to include the KDB specific
> >> reason code. This removes a dependency on KDB in the debug
> >> core. Also requires a change the call in from UV NMI handler.
> >>
> >> * Fix some problems found by the kbuild test robot.
> >>
> >> * Fix UV call into kgdb to depend only on whether KGDB is defined
> >> and not both KGDB and KDB. This allows the power nmi command
> >> to use the gdb remote connection if enabled. Note new action
> >> of 'kgdb' needs to be set as well to indicate user wants to
> >> wait for gdb to be connected. If it's set to 'kdb' then an
> >> error message is displayed if KDB is not configured.
> >> --
> >
> > This looks better.
> >
> > Jason, any objections?
> >
> > Thanks,
> >
> > Ingo
> >
>
> I haven't heard anything back about this update. Were there
> objections? Looks like another merge window is closing?
Please resend the series.
Thanks,
Ingo