Mark Rutland writes:
> On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
>> On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
>> > Christopher Covington writes:
>> > > On 05/22/2014 03:27 PM, Larry Bassel wrote:
>> > >> Make calls to ct_user_enter when the kernel is
On Fri, May 23, 2014 at 04:55:44PM +0100, Mark Rutland wrote:
> On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
> > On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
> > I haven't checked all the code paths but at least for pushing onto the
> > stack we must keep it
On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
> On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
> > Christopher Covington writes:
> > > On 05/22/2014 03:27 PM, Larry Bassel wrote:
> > >> Make calls to ct_user_enter when the kernel is exited
> > >> and ct_user_exit
On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
> Christopher Covington writes:
> > On 05/22/2014 03:27 PM, Larry Bassel wrote:
> >> Make calls to ct_user_enter when the kernel is exited
> >> and ct_user_exit when the kernel is entered (in el0_da,
> >> el0_ia, el0_svc, el0_irq and
On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
Christopher Covington c...@codeaurora.org writes:
On 05/22/2014 03:27 PM, Larry Bassel wrote:
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc,
On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
Christopher Covington c...@codeaurora.org writes:
On 05/22/2014 03:27 PM, Larry Bassel wrote:
Make calls to ct_user_enter when the kernel is exited
and
On Fri, May 23, 2014 at 04:55:44PM +0100, Mark Rutland wrote:
On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
I haven't checked all the code paths but at least for pushing onto the
stack we must keep it 16-bytes
Mark Rutland mark.rutl...@arm.com writes:
On Fri, May 23, 2014 at 03:51:07PM +0100, Catalin Marinas wrote:
On Fri, May 23, 2014 at 01:11:38AM +0100, Kevin Hilman wrote:
Christopher Covington c...@codeaurora.org writes:
On 05/22/2014 03:27 PM, Larry Bassel wrote:
Make calls to
+Mark Rutland
Christopher Covington writes:
> Hi Larry,
>
> On 05/22/2014 03:27 PM, Larry Bassel wrote:
>> Make calls to ct_user_enter when the kernel is exited
>> and ct_user_exit when the kernel is entered (in el0_da,
>> el0_ia, el0_svc, el0_irq and all of the "error" paths).
>>
>> These
Hi Larry,
On 05/22/2014 03:27 PM, Larry Bassel wrote:
> Make calls to ct_user_enter when the kernel is exited
> and ct_user_exit when the kernel is entered (in el0_da,
> el0_ia, el0_svc, el0_irq and all of the "error" paths).
>
> These macros expand to function calls which will only work
>
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the "error" paths).
These macros expand to function calls which will only work
properly if el0_sync and related code has been rearranged
(in a previous
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the error paths).
These macros expand to function calls which will only work
properly if el0_sync and related code has been rearranged
(in a previous
Hi Larry,
On 05/22/2014 03:27 PM, Larry Bassel wrote:
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the error paths).
These macros expand to function calls which will only work
properly if
+Mark Rutland
Christopher Covington c...@codeaurora.org writes:
Hi Larry,
On 05/22/2014 03:27 PM, Larry Bassel wrote:
Make calls to ct_user_enter when the kernel is exited
and ct_user_exit when the kernel is entered (in el0_da,
el0_ia, el0_svc, el0_irq and all of the error paths).
These
14 matches
Mail list logo