Re: [PATCH 2/2] scripts/gdb: Support getting current task struct in UML

2023-02-15 Thread Jan Kiszka
On 15.02.23 16:55, Glenn Washburn wrote: > On Wed, 15 Feb 2023 08:45:20 +0100 > Jan Kiszka wrote: > >> On 15.02.23 00:35, Glenn Washburn wrote: >>> A running x86 UML kernel reports with architecture "i386:x86-64" as >>> it is a sub-architecture. However, a difference with bare-metal x86 >>> kerne

Re: [PATCH 2/2] scripts/gdb: Support getting current task struct in UML

2023-02-15 Thread Glenn Washburn
On Wed, 15 Feb 2023 08:45:20 +0100 Jan Kiszka wrote: > On 15.02.23 00:35, Glenn Washburn wrote: > > A running x86 UML kernel reports with architecture "i386:x86-64" as > > it is a sub-architecture. However, a difference with bare-metal x86 > > kernels is in how it manages tasks and the current ta

Re: [PATCH 2/2] scripts/gdb: Support getting current task struct in UML

2023-02-15 Thread Jan Kiszka
On 15.02.23 00:35, Glenn Washburn wrote: > A running x86 UML kernel reports with architecture "i386:x86-64" as > it is a sub-architecture. However, a difference with bare-metal x86 > kernels is in how it manages tasks and the current task struct. To > identify that the inferior is a UML kernel and

[PATCH 2/2] scripts/gdb: Support getting current task struct in UML

2023-02-14 Thread Glenn Washburn
A running x86 UML kernel reports with architecture "i386:x86-64" as it is a sub-architecture. However, a difference with bare-metal x86 kernels is in how it manages tasks and the current task struct. To identify that the inferior is a UML kernel and not bare-metal, the symbol "uml_kmalloc" is check