<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/x86/kernel/kgdb.c, branch linux-2.6.30.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-05-15T12:56:25Z</updated>
<entry>
<title>kgdb,i386: use address that SP register points to in the exception frame</title>
<updated>2009-05-15T12:56:25Z</updated>
<author>
<name>Jason Wessel</name>
</author>
<published>2009-02-12T00:46:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=33ab1979bc9f719213bc3f392c8fd9d012e4f4e9'/>
<id>urn:sha1:33ab1979bc9f719213bc3f392c8fd9d012e4f4e9</id>
<content type='text'>
The treatment of the SP register is different on x86_64 and i386.
This is a regression fix that lived outside the mainline kernel from
2.6.27 to now.  The regression was a result of the original merge
consolidation of the i386 and x86_64 archs to x86.

The incorrectly reported SP on i386 prevented stack tracebacks from
working correctly in gdb.

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
</content>
</entry>
<entry>
<title>x86, apic: remove genapic.h</title>
<updated>2009-02-17T16:52:44Z</updated>
<author>
<name>Ingo Molnar</name>
</author>
<published>2009-02-17T12:58:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7b6aa335ca1a845c2262ec7a595b4521bca0f79d'/>
<id>urn:sha1:7b6aa335ca1a845c2262ec7a595b4521bca0f79d</id>
<content type='text'>
Impact: cleanup

Remove genapic.h and remove all references to it.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>x86, smp: remove mach_ipi.h</title>
<updated>2009-01-29T13:16:49Z</updated>
<author>
<name>Ingo Molnar</name>
</author>
<published>2009-01-28T18:14:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d53e2f2855f1c7c2725d550c1ae6b26f4d671c50'/>
<id>urn:sha1:d53e2f2855f1c7c2725d550c1ae6b26f4d671c50</id>
<content type='text'>
Move mach_ipi.h definitions into genapic.h.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>x86, apic: untangle the send_IPI_*() jungle</title>
<updated>2009-01-28T22:20:31Z</updated>
<author>
<name>Ingo Molnar</name>
</author>
<published>2009-01-28T14:42:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dac5f4121df3c39fdb2ea57acd669a0ae19e46f8'/>
<id>urn:sha1:dac5f4121df3c39fdb2ea57acd669a0ae19e46f8</id>
<content type='text'>
Our send_IPI_*() methods and definitions are a twisted mess: the same
symbol is defined to different things depending on .config details,
in a non-transparent way.

 - spread out the quirks into separately named per apic driver methods

 - prefix the standard PC methods with default_

 - get rid of wrapper macro obfuscation

 - clean up various details

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>kgdb, x86: Avoid invoking kgdb_nmicallback twice per NMI</title>
<updated>2008-10-06T18:50:59Z</updated>
<author>
<name>Jan Kiszka</name>
</author>
<published>2008-10-06T18:50:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e85ceae9102f6e3c1d707e7ac88fa48d252e9cfa'/>
<id>urn:sha1:e85ceae9102f6e3c1d707e7ac88fa48d252e9cfa</id>
<content type='text'>
Stress-testing KVM's latest NMI support with kgdbts inside an SMP guest,
I came across spurious unhandled NMIs while running the singlestep test.
Looking closer at the code path each NMI takes when KGDB is enabled, I
noticed that kgdb_nmicallback is called twice per event: One time via
DIE_NMI_IPI notification, the second time on DIE_NMI. Removing the first
invocation cures the unhandled NMIs here.

Signed-off-by: Jan Kiszka &lt;jan.kiszka@siemens.com&gt;
Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
</content>
</entry>
<entry>
<title>kgdb, x86_64: fix PS CS SS registers in gdb serial</title>
<updated>2008-09-26T15:36:42Z</updated>
<author>
<name>Jason Wessel</name>
</author>
<published>2008-09-26T15:36:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=703a1edcd1534468fc18f733c03bd91a65c8c6f0'/>
<id>urn:sha1:703a1edcd1534468fc18f733c03bd91a65c8c6f0</id>
<content type='text'>
On x86_64 the gdb serial register structure defines the PS (also known
as eflags), CS and SS registers as 4 bytes entities.

This patch splits the x86_64 regnames enum into a 32 and 64 version to
account for the 32 bit entities in the gdb serial packets.

Also the program counter is properly filled in for the sleeping
threads.

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
</content>
</entry>
<entry>
<title>kgdb, x86, arm, mips, powerpc: ignore user space single stepping</title>
<updated>2008-09-26T15:36:41Z</updated>
<author>
<name>Jason Wessel</name>
</author>
<published>2008-09-26T15:36:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d7161a65341556bacb5e6654e133803f46f51063'/>
<id>urn:sha1:d7161a65341556bacb5e6654e133803f46f51063</id>
<content type='text'>
On the x86 arch, user space single step exceptions should be ignored
if they occur in the kernel space, such as ptrace stepping through a
system call.

First check if it is kgdb that is executing a single step, then ensure
it is not an accidental traversal into the user space, while in kgdb,
any other time the TIF_SINGLESTEP is set, kgdb should ignore the
exception.

On x86, arm, mips and powerpc, the kgdb_contthread usage was
inconsistent with the way single stepping is implemented in the kgdb
core.  The arch specific stub should always set the
kgdb_cpu_doing_single_step correctly if it is single stepping.  This
allows kgdb to correctly process an instruction steps if ptrace
happens to be requesting an instruction step over a system call.

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
</content>
</entry>
<entry>
<title>x86: KGDB build fix</title>
<updated>2008-04-19T17:19:54Z</updated>
<author>
<name>Ingo Molnar</name>
</author>
<published>2008-04-19T17:19:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f8dfd5ed149ae340451f25847b434297c20d4645'/>
<id>urn:sha1:f8dfd5ed149ae340451f25847b434297c20d4645</id>
<content type='text'>
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
<entry>
<title>x86: kgdb build fix</title>
<updated>2008-04-18T17:02:12Z</updated>
<author>
<name>Harvey Harrison</name>
</author>
<published>2008-04-18T16:54:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fda31d7d4b5a9c663ac3ed1ba244018a88deecaf'/>
<id>urn:sha1:fda31d7d4b5a9c663ac3ed1ba244018a88deecaf</id>
<content type='text'>
TF_MASK is no longer defined, use X86_EFLAGS_TF.

Signed-off-by: Harvey Harrison &lt;harvey.harrison@gmail.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>kgdb: fix several kgdb regressions</title>
<updated>2008-04-17T18:05:40Z</updated>
<author>
<name>Jason Wessel</name>
</author>
<published>2008-03-07T22:34:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=737a460f21febe551ff1d2299b63bae9b154078f'/>
<id>urn:sha1:737a460f21febe551ff1d2299b63bae9b154078f</id>
<content type='text'>
kgdb core fixes:
- Check to see that mm-&gt;mmap_cache is not null before calling
  flush_cache_range(), else on arch=ARM it will cause a fatal
  fault.

- Breakpoints should only be restored if they are in the BP_ACTIVE
  state.

- Fix a typo in comments to "kgdb_register_io_module"

x86 kgdb fixes:
- Fix the x86 arch handler such that on a kill or detach that the
  appropriate cleanup on the single stepping flags gets run.

- Add in the DIE_NMIWATCHDOG call for x86_64

- Touch the nmi watchdog before returning the system to normal
  operation after performing any kind of kgdb operation, else
  the possibility exists to trigger the watchdog.

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
</content>
</entry>
</feed>
