[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4953CD1A.5090906@redhat.com>
Date: Thu, 25 Dec 2008 20:12:42 +0200
From: Avi Kivity <avi@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
CC: "H. Peter Anvin" <hpa@...or.com>,
Joerg Roedel <joerg.roedel@....com>,
Benjamin Serebrin <benjamin.serebrin@....com>,
linux-kernel <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org,
Alexander Graf <agraf@...e.de>,
Arjan van de Ven <arjan@...radead.org>,
Alexander van Heukelum <heukelum@...tmail.fm>
Subject: Re: kvm vmload/vmsave vs tss.ist
Ingo Molnar wrote:
>> I think it's enough to switch %rsp before incrementing irqcount, no?
>>
>
> no - that would introduce a small race: if an exception (say an NMI or
> MCE, or a debug trap) happens in that small window then the exception
> context thinks that it's on the IRQ stack already, and would use the task
> stack.
>
>
I'm suggesting
check irqcount
if (wasnt_in_irq)
rsp = irqstack
++irqcount
If the NMI happens before the increment, we'll switch the stack
unconditionally, and if the NMI happens after the increment, then we
won't switch the stack, but we're guaranteed to be on the irqstack
anyway. The window size is negative :)
Similarly, the exit path should be
oldstack_reg = oldstack;
--irqcount;
rsp = oldstack_register;
To guarantee that by the time we decrement irqcount, we don't need the
stack anymore.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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