On 03/19/2012 08:52 AM, Jan Kiszka wrote:
> On 2012-03-16 16:57, Jason Wessel wrote:
> The rest should be fine. I can test this and add it to the merge queue with
> the NUMREGBYTES change, unless you disagree.
> I don't disagree. :)
Sounds fine. I added this to the merge queue for the 3.4 kern
On 2012-03-16 16:57, Jason Wessel wrote:
> On 03/16/2012 07:17 AM, Jan Kiszka wrote:
>> Even if the content is always 0, gdb expects us to return also ds,
>> es, fs, and gs while in x86-64 mode. Do this to avoid ugly errors on
>> "info registers".
>>
>> Signed-off-by: Jan Kiszka
>> ---
>> arch/x8
On 03/16/2012 07:17 AM, Jan Kiszka wrote:
> Even if the content is always 0, gdb expects us to return also ds,
> es, fs, and gs while in x86-64 mode. Do this to avoid ugly errors on
> "info registers".
>
> Signed-off-by: Jan Kiszka
> ---
> arch/x86/include/asm/kgdb.h |6 +-
> arch/x86/ker
Even if the content is always 0, gdb expects us to return also ds,
es, fs, and gs while in x86-64 mode. Do this to avoid ugly errors on
"info registers".
Signed-off-by: Jan Kiszka
---
arch/x86/include/asm/kgdb.h |6 +-
arch/x86/kernel/kgdb.c |6 --
2 files changed, 9 inserti
Even if the content is always 0, gdb expects us to return also ds,
es, fs, and gs while in x86-64 mode. Do this to avoid ugly errors on
"info registers".
Signed-off-by: Jan Kiszka
---
arch/x86/include/asm/kgdb.h |6 +-
arch/x86/kernel/kgdb.c |6 --
2 files changed, 9 inserti
