search for: popf

...s, 2011) [downloadable] deadspace Dead Space (EA, 2008) deadspace2 Dead Space 2 (drm broken on wine) (EA, 2011) dragonage_ue Dragon Age: Origins - Ultimate Edition (Bioware / EA, 2010) mise Monkey Island: Special Edition (LucasArts, 2009) popfs Prince of Persia The Forgotten Sands (Ubisoft, 2010) splitsecond Split Second (Disney, 2010) splitsecond_demo Split Second Demo (Disney, 2010) [downloadable] spore Spore (EA, 2008) For bug tracker, mailing lists, and wiki, see http://wi...

Hello all, I am trying to implement intrinsics __readeflags and __writeeflags reading and writing EFLAGS register on x86. These intrinsics expand to two instructions popf and push to register for __readeflags and pushf and pop to register for __writeeflags. These instructions are not connected explicitly so I can't use patterns in .td file to match intrinsics. I tried to implement custom expansion making COPY DAG node with copy from EFLAGS to register. But this...

...irtual machine, and you can allow userspace to disable interrupts and still have a perfectly fine solution -- if you restrict the enabling and disabling of interrupts in userspace to the cli and sti instructions. But it does not work if you start using nested interrupt control, using pushf and popf. The virtual machine monitor must always leave hardware interrupts enabled, since it must service them without allowing the guest VM to interfere. As such, the actual state of the hardware interrupt flag is visible to userspace programs. CLI and STI get away with this, because they are privi...

...irtual machine, and you can allow userspace to disable interrupts and still have a perfectly fine solution -- if you restrict the enabling and disabling of interrupts in userspace to the cli and sti instructions. But it does not work if you start using nested interrupt control, using pushf and popf. The virtual machine monitor must always leave hardware interrupts enabled, since it must service them without allowing the guest VM to interfere. As such, the actual state of the hardware interrupt flag is visible to userspace programs. CLI and STI get away with this, because they are privi...

...ngRef.html#id1164 On Tue, Dec 17, 2013 at 1:02 AM, Alexey Volkov <avolkov.intel at gmail.com>wrote: > Hello all, > > I am trying to implement intrinsics __readeflags and __writeeflags reading > and writing EFLAGS register on x86. > These intrinsics expand to two instructions popf and push to register for > __readeflags and pushf and pop to register for __writeeflags. > These instructions are not connected explicitly so I can't use patterns in > .td file to match intrinsics. > > I tried to implement custom expansion making COPY DAG node with copy from >...

Agreed, never emit pushf/popf. Sorry I never committed the patch, the cmov issue got hairy and I never got to debugging it :-) I can get back to it if there's interest! On Wed, Jul 29, 2015 at 4:12 PM, Reid Kleckner <rnk at google.com> wrote: > I remember this bug. :) IMO, LLVM should never emit pushf / popf. I...

I am new to the LLVM backends, I am wondering how instruction selection is done in LLVM backends, I looked at the .td files in Target/X86, they all seem to be small and do not deal with common X86 instructions, i.e. mov, push, pop, etc. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

...shf; pop %[re]ax > .mmu_read_cr2 = { 0x0f, 0x20, 0xd0 }, // mov %cr2, %[re]ax > .mmu_read_cr3 = { 0x0f, 0x20, 0xd8 }, // mov %cr3, %[re]ax > -# ifdef CONFIG_X86_64 > .mmu_write_cr3 = { 0x0f, 0x22, 0xdf }, // mov %rdi, %cr3 > .irq_restore_fl = { 0x57, 0x9d }, // push %rdi; popfq > .cpu_wbinvd = { 0x0f, 0x09 }, // wbinvd > @@ -50,19 +45,11 @@ static const struct patch_xxl patch_data_xxl = { > 0x48, 0x0f, 0x07 }, // swapgs; sysretq > .cpu_swapgs = { 0x0f, 0x01, 0xf8 }, // swapgs > .mov64 = { 0x48, 0x89, 0xf8 }, // mov %rdi, %rax > -# els...

...shf; pop %[re]ax > .mmu_read_cr2 = { 0x0f, 0x20, 0xd0 }, // mov %cr2, %[re]ax > .mmu_read_cr3 = { 0x0f, 0x20, 0xd8 }, // mov %cr3, %[re]ax > -# ifdef CONFIG_X86_64 > .mmu_write_cr3 = { 0x0f, 0x22, 0xdf }, // mov %rdi, %cr3 > .irq_restore_fl = { 0x57, 0x9d }, // push %rdi; popfq > .cpu_wbinvd = { 0x0f, 0x09 }, // wbinvd > @@ -50,19 +45,11 @@ static const struct patch_xxl patch_data_xxl = { > 0x48, 0x0f, 0x07 }, // swapgs; sysretq > .cpu_swapgs = { 0x0f, 0x01, 0xf8 }, // swapgs > .mov64 = { 0x48, 0x89, 0xf8 }, // mov %rdi, %rax > -# els...

Hi all, Does anyone have thoughts on extending v->arch.hvm_vcpu.single_step to support pre-MTF systems, in a way that would mimic the MTF? So far I''m emulating PUSHF/POPF to hide the hypervisor''s trap flag, and eventually I''ll multiplex it down to the guest, but I''m having issues. Right now, I''m enabling X86_EFLAGS_TF in vmx_intr_assist, just like where MTF is enabled if desired. It''s cleared at the start of vmx_exit_han...

I remember this bug. :) IMO, LLVM should never emit pushf / popf. I'm not sure this patch to fix it ever got committed: http://reviews.llvm.org/D6629 On Wed, Jul 29, 2015 at 3:11 PM, Michael Hordijk <hoffbrinkle at hotmail.com> wrote: > > Using Clang/LLVM 3.6.0 we are observing a case where the optimizations are > clobbering EFLAGS on x86_64...

On 7/29/15 18:35, JF Bastien wrote: > Agreed, never emit pushf/popf. Sorry I never committed the patch, the > cmov issue got hairy and I never got to debugging it :-) > I can get back to it if there's interest! You've definitely got some interest here. I've been looking at your patch on http://reviews.llvm.org/D6629 and I think I'm up to sp...

On 06/05/18 10:05, Nick Desaulniers wrote: > + > +/* > + * void native_restore_fl(unsigned long flags) > + * %rdi: flags > + */ > +ENTRY(native_restore_fl) > + push %_ASM_DI > + popf > + ret > +ENDPROC(native_restore_fl) > +EXPORT_SYMBOL(native_restore_fl) > To work on i386, this would have to be %_ASM_AX in that case. Something like this added to <asm/asm.h> might be useful; then you can simply: push %_ASM_ARG1 -------------- next part -------------- A n...

On 06/05/18 10:05, Nick Desaulniers wrote: > + > +/* > + * void native_restore_fl(unsigned long flags) > + * %rdi: flags > + */ > +ENTRY(native_restore_fl) > + push %_ASM_DI > + popf > + ret > +ENDPROC(native_restore_fl) > +EXPORT_SYMBOL(native_restore_fl) > To work on i386, this would have to be %_ASM_AX in that case. Something like this added to <asm/asm.h> might be useful; then you can simply: push %_ASM_ARG1 -------------- next part -------------- A n...

I found a clever way to make the extra IOPL switching invisible to non-paravirt compiles - since kernel_rpl is statically defined to be zero there, and only non-zero rpl kernel have a problem restoring IOPL, as popf does not restore IOPL flags unless run at CPL-0. Subject: IOPL handling for paravirt guests Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 8110943fd7ad arch/i386/kernel/process.c --- a/arch/i386/kernel/process.c Thu Dec 14 16:15:20 2006 -0800 +++ b/arch/i386/kernel/process.c Thu De...

Steven Hi, I'm unable to compile testcpuid.c with the __x86_64__ architecture (Athlon 64 processor). The messages are: /tmp/ccONleRV.s: Assembly messages: /tmp/ccONleRV.s: Error: suffix or operands invalid for 'pushf' " 'pop' " 'push' " 'popf' Is it safe to ignore this module? When I attempt to start asterisk, libspandsp.so.0 fails to load because 'top_bit' is undefined. Is this related to the compile problem? Thanks for your help, -- Michael Welter Introspect Telephony Corp. Denver, Colorado US +1.303.674.2575 mike@i...

...r operands invalid for `pushf' /tmp/ccXxGHg6.s:9: Error: suffix or operands invalid for `pushf' /tmp/ccXxGHg6.s:10: Error: suffix or operands invalid for `pop' /tmp/ccXxGHg6.s:13: Error: suffix or operands invalid for `push' /tmp/ccXxGHg6.s:14: Error: suffix or operands invalid for `popf' /tmp/ccXxGHg6.s:15: Error: suffix or operands invalid for `pushf' /tmp/ccXxGHg6.s:16: Error: suffix or operands invalid for `pop' /tmp/ccXxGHg6.s:17: Error: suffix or operands invalid for `popf' make[2]: *** [testcpuid.lo] Error 1 -- Juan Jose Comellas (juanjo@comellas.com.ar)

I found a clever way to make the extra IOPL switching invisible to non-paravirt compiles - since kernel_rpl is statically defined to be zero there, and only non-zero rpl kernel have a problem restoring IOPL, as popf does not restore IOPL flags unless run at CPL-0. Subject: IOPL handling for paravirt guests Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 8110943fd7ad arch/i386/kernel/process.c --- a/arch/i386/kernel/process.c Thu Dec 14 16:15:20 2006 -0800 +++ b/arch/i386/kernel/process.c Thu De...

...lls local_irq_disable(). But why there is no local_irq_enable() in local_irq_restore? #define local_irq_save(x) ({ local_save_flags(x); local_irq_disable(); }) #define local_irq_restore(x) ({ BUILD_BUG_ON(sizeof(x) != sizeof(long)); asm volatile ( "push" __OS " %0 ; popf" __OS : : "g" (x) : "memory", "cc" ); }) -- Xinxin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

...operands invalid for `pushf' /tmp/ccrDL6i4.s:17: Error: suffix or operands invalid for `pushf' /tmp/ccrDL6i4.s:18: Error: suffix or operands invalid for `pop' /tmp/ccrDL6i4.s:21: Error: suffix or operands invalid for `push' /tmp/ccrDL6i4.s:22: Error: suffix or operands invalid for `popf' /tmp/ccrDL6i4.s:23: Error: suffix or operands invalid for `pushf' /tmp/ccrDL6i4.s:24: Error: suffix or operands invalid for `pop' /tmp/ccrDL6i4.s:25: Error: suffix or operands invalid for `popf' /tmp/ccrDL6i4.s:31: Error: suffix or operands invalid for `push' /tmp/ccrDL6i4.s:34...