[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190711201706.GB20140@rapoport-lnx>
Date: Thu, 11 Jul 2019 23:17:07 +0300
From: Mike Rapoport <rppt@...ux.ibm.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Alexandre Chartre <alexandre.chartre@...cle.com>,
pbonzini@...hat.com, rkrcmar@...hat.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, hpa@...or.com,
dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
kvm@...r.kernel.org, x86@...nel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, konrad.wilk@...cle.com,
jan.setjeeilers@...cle.com, liran.alon@...cle.com,
jwadams@...gle.com, graf@...zon.de, rppt@...ux.vnet.ibm.com
Subject: Re: [RFC v2 02/26] mm/asi: Abort isolation on interrupt, exception
and context switch
On Thu, Jul 11, 2019 at 01:11:43PM -0700, Andi Kleen wrote:
> Alexandre Chartre <alexandre.chartre@...cle.com> writes:
> > jmp paranoid_exit
> > @@ -1182,6 +1196,16 @@ ENTRY(paranoid_entry)
> > xorl %ebx, %ebx
> >
> > 1:
> > +#ifdef CONFIG_ADDRESS_SPACE_ISOLATION
> > + /*
> > + * If address space isolation is active then abort it and return
> > + * the original kernel CR3 in %r14.
> > + */
> > + ASI_START_ABORT_ELSE_JUMP 2f
> > + movq %rdi, %r14
> > + ret
> > +2:
> > +#endif
>
> Unless I missed it you don't map the exception stacks into ASI, so it
> has likely already triple faulted at this point.
The exception stacks are in the CPU entry area, aren't they?
> -Andi
>
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists