[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141009224304.GA4818@jhogan-linux.le.imgtec.org>
Date: Thu, 9 Oct 2014 23:43:04 +0100
From: James Hogan <james.hogan@...tec.com>
To: Leonid Yegoshin <Leonid.Yegoshin@...tec.com>
CC: <linux-mips@...ux-mips.org>, <Zubair.Kakakhel@...tec.com>,
<geert+renesas@...der.be>, <david.daney@...ium.com>,
<peterz@...radead.org>, <paul.gortmaker@...driver.com>,
<davidlohr@...com>, <macro@...ux-mips.org>, <chenhc@...ote.com>,
<richard@....at>, <zajec5@...il.com>, <keescook@...omium.org>,
<alex@...x-smith.me.uk>, <tglx@...utronix.de>,
<blogic@...nwrt.org>, <jchandra@...adcom.com>,
<paul.burton@...tec.com>, <qais.yousef@...tec.com>,
<linux-kernel@...r.kernel.org>, <ralf@...ux-mips.org>,
<markos.chandras@...tec.com>, <dengcheng.zhu@...tec.com>,
<manuel.lauss@...il.com>, <akpm@...ux-foundation.org>,
<lars.persson@...s.com>
Subject: Re: [PATCH v2 2/3] MIPS: Setup an instruction emulation in VDSO
protected page instead of user stack
Hi Leonid,
On Thu, Oct 09, 2014 at 01:00:17PM -0700, Leonid Yegoshin wrote:
> Signal happend during run in emulation block is handled properly - EPC is
> changed to before an emulated jump or to target address, depending from point of
> signal.
Great!
> Small stack of emulation blocks is supported because nested traps are possible
> in MIPS32/64 R6 emulation mix with FPU emulation.
Could you please clarify how this nesting of emulation blocks could
happen now that signals are handled more cleanly.
I.e. isn't the emuframe stuff only required for instructions in branch
delay slots, and branches shouldn't be in branch delay slots anyway, so
I don't get how they could nest.
Thanks
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists