[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210218105710.GA5814@alpha.franken.de>
Date: Thu, 18 Feb 2021 11:57:10 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: "Maciej W. Rozycki" <macro@...am.me.uk>
Cc: Tiezhu Yang <yangtiezhu@...ngson.cn>,
Oleg Nesterov <oleg@...hat.com>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, Xuefeng Li <lixuefeng@...ngson.cn>,
kernel test robot <lkp@...el.com>,
Xingxing Su <suxingxing@...ngson.cn>
Subject: Re: [PATCH v2] MIPS: Add basic support for ptrace single step
On Tue, Feb 16, 2021 at 02:55:36PM +0100, Maciej W. Rozycki wrote:
> On Fri, 12 Feb 2021, Thomas Bogendoerfer wrote:
>
> > > IMHO ptrace single step is for CPUs supporting single stepping and not
> > > for emulating it in the kernel.
> >
> > I've checked other arch how they implement single step, and looks like
> > I'm wrong. So I'm ok with applying your patch. Can you resend it again,
> > so I'll get the latest version in patchwork ?
>
> [..]
> This is broken and belongs to the userland anyway. See how complex the
> handling is in GDB, specifically `mips16_next_pc', `micromips_next_pc' and
> `mips32_next_pc' in gdb/mips-tdep.c.
I should have looked closer how other archs are implementing single
stepping. It's only alpha, which emulates it by setting breakpoints. All
others have some type of cpu cupport for getting traps after a single
intstruction has been issued. So I'm reverting the commit and supporting
Maciej's statement about putting that stuff into userland (again).
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists