On 5/14/19 9:07 AM, Peter Zijlstra wrote:
On Mon, May 13, 2019 at 11:13:34AM -0700, Andy Lutomirski wrote:
On Mon, May 13, 2019 at 9:28 AM Alexandre Chartre
wrote:
Actually, I am not sure this is effectively useful because the IRQ
handler is probably faulting before it tries to exit isolat
On Mon, May 13, 2019 at 11:13:34AM -0700, Andy Lutomirski wrote:
> On Mon, May 13, 2019 at 9:28 AM Alexandre Chartre
> wrote:
> > Actually, I am not sure this is effectively useful because the IRQ
> > handler is probably faulting before it tries to exit isolation, so
> > the isolation exit will b
On Mon, May 13, 2019 at 9:28 AM Alexandre Chartre
wrote:
>
>
>
> On 5/13/19 5:51 PM, Andy Lutomirski wrote:
> > On Mon, May 13, 2019 at 7:39 AM Alexandre Chartre
> > wrote:
> >>
> >> From: Liran Alon
> >>
> >> Next commits will change most of KVM #VMExit handlers to run
> >> in KVM isolated addr
On 5/13/19 5:51 PM, Andy Lutomirski wrote:
On Mon, May 13, 2019 at 7:39 AM Alexandre Chartre
wrote:
From: Liran Alon
Next commits will change most of KVM #VMExit handlers to run
in KVM isolated address space. Any interrupt handler raised
during execution in KVM address space needs to swit
On Mon, May 13, 2019 at 7:39 AM Alexandre Chartre
wrote:
>
> From: Liran Alon
>
> Next commits will change most of KVM #VMExit handlers to run
> in KVM isolated address space. Any interrupt handler raised
> during execution in KVM address space needs to switch back
> to host address space.
>
> Th
From: Liran Alon
Next commits will change most of KVM #VMExit handlers to run
in KVM isolated address space. Any interrupt handler raised
during execution in KVM address space needs to switch back
to host address space.
This patch makes sure that IRQ handlers will run in full
host address space
6 matches
Mail list logo