On 30/04/20 02:45, Andy Lutomirski wrote: >> That's a very bad idea since one is synchronous and one is asynchronous. >> Part of the proposal we agreed upon was to keep "page not ready" >> synchronous while making "page ready" an interrupt. The data structure >> for "page not ready" will be #VE. > > #VE on SVM will be interesting, to say the least, and I think that a > solution that is VMX specific doesn't make much sense. You can always inject it manually. The same is true of Haswell and earlier processors. > #VE also has > unpleasant issues involving the contexts in which it can occur. You > will have quite a hard time convincing me to ack the addition of a #VE > entry handler for this. I think a brand new vector is the right > solution. I need --verbose. :) For #VE I liked the idea of re-enabling it from an IPI, at least in the case where we cannot move out of the IST stack. And any other vector that behaves like an exception would have the same issue, wouldn't it (especially re-entrancy)? Paolo
