On Sun, Aug 01, 2010 at 03:35:41PM +0300, Avi Kivity wrote: > On 08/01/2010 03:23 PM, Gleb Natapov wrote: > >On Sun, Aug 01, 2010 at 03:17:10PM +0300, Avi Kivity wrote: > >> On 08/01/2010 01:53 PM, Gleb Natapov wrote: > >>>>That requires everyone to update, or suffer major breakage. > >>>> > >>>They will suffer major breakage when they update to a kvm that calls to > >>>kvm-tpr-opt.c from emulator anyway. > >>Why? > >> > >Because tpr code will be called with wrong rip. Emulator always updated rip at the end > >of an instruction emulation in writeback stage. > > > > We can change it before switching enabling e_i_g_s by default. > > Break emulator? We can't increment rip for all instructions before emulation since then exception will be injected at incorrect rip. Adding code that rollbacks rip in case of exception will complicate things and exception is not the only reason to keep rip pointed to the instruction. We may want to reenter guest to reexecute it for instance. > >>>So what can we do about it? > >>> > >>Keep the existing behaviour. > >> > >Existing behaviour will cause breakage. > > > > The existing user-visible behaviour. The user doesn't know whether > the emulator is involved or not. > When we are going to enable e_i_g_s by default? May be we have enough time to fix userspace? Too ancient userspace already does not run on recent kvm. Or may be we can make userspace enable e_i_g_s per guest. This way userspace that knows it is OK can tell kernel so. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
