[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190314105143.GA15410@e107155-lin>
Date: Thu, 14 Mar 2019 10:51:44 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: "Haibo Xu (Arm Technology China)" <Haibo.Xu@....com>
Cc: Andy Lutomirski <luto@...nel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Catalin Marinas <Catalin.Marinas@....com>,
Will Deacon <Will.Deacon@....com>,
Oleg Nesterov <oleg@...hat.com>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Richard Weinberger <richard@....at>,
"jdike@...toit.com" <jdike@...toit.com>,
Steve Capper <Steve.Capper@....com>,
"Bin Lu (Arm Technology China)" <Bin.Lu@....com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 3/6] x86: clean up _TIF_SYSCALL_EMU handling using
ptrace_syscall_enter hook
On Wed, Mar 13, 2019 at 01:03:18AM +0000, Haibo Xu (Arm Technology China) wrote:
[...]
> Since ptrace() system call do have so many request type, I'm not sure
> whether the test cases have covered all of that. But here we'd better make
> sure the PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP requests are work
> correctly. May be you can verify them with tests from Bin Lu(bin.lu@....com).
Sure happy to try them. Can you point me to them ?
I did end up writing few more tests.
--
Regards,
Sudeep
Powered by blists - more mailing lists