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
Hi Srinivasarao,
On Wed, Feb 15, 2023 at 6:36 AM Srinivasarao Pathipati
wrote:
> On 2/15/2023 3:27 AM, Richard Weinberger wrote:
> > - Ursprüngliche Mail -
> >> Von: "Srinivasarao Pathipati"
> >> static void sig_handler_common(int sig, struct siginfo *si, mcontext_t *mc)
> >> {
> >> -
On Wed, 2023-02-15 at 09:07 +0100, Geert Uytterhoeven wrote:
> Hi Srinivasarao,
>
> On Wed, Feb 15, 2023 at 6:36 AM Srinivasarao Pathipati
> wrote:
> > On 2/15/2023 3:27 AM, Richard Weinberger wrote:
> > > - Ursprüngliche Mail -
> > > > Von: "Srinivasarao Pathipati"
> > > > static void s
On Tue, 2023-02-14 at 22:57 +0100, Richard Weinberger wrote:
> - Ursprüngliche Mail -
> > Von: "Srinivasarao Pathipati"
> > static void sig_handler_common(int sig, struct siginfo *si, mcontext_t *mc)
> > {
> > - struct uml_pt_regs r;
> > + struct uml_pt_regs *r;
> > int save_errno
Hi Greert Uytterhoeven,
On 2/15/2023 1:37 PM, Geert Uytterhoeven wrote:
Hi Srinivasarao,
On Wed, Feb 15, 2023 at 6:36 AM Srinivasarao Pathipati
wrote:
On 2/15/2023 3:27 AM, Richard Weinberger wrote:
- Ursprüngliche Mail -
Von: "Srinivasarao Pathipati"
static void sig_handler_common
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
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
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, check
for the existence of the UM
There is an extra space in a couple blocks in get_current_task.
Though python does not care, let's make the spacing consistent.
Also, format better an if expression, removing unneeded parenthesis.
Signed-off-by: Glenn Washburn
---
scripts/gdb/linux/cpus.py | 18 +-
1 file changed
Added suggestions from Jan.
Glenn
Glenn Washburn (2):
scripts/gdb: Correct indentation in get_current_task
scripts/gdb: Support getting current task struct in UML
scripts/gdb/linux/cpus.py | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
Range-diff against v1
10 matches
Mail list logo