search for: sysexit

...:07, Andy Lutomirski wrote: > On Thu, Nov 19, 2015 at 1:55 PM, Boris Ostrovsky > <boris.ostrovsky at oracle.com> wrote: >> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the >> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit >> (and sysret32 in compat mode) pv ops, as suggested by Andy. >> >> As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not >> used anymore by anyone and so can be removed. > This whole series is: > > Acked-by: Andy Lutomirski <luto at kern...

...:07, Andy Lutomirski wrote: > On Thu, Nov 19, 2015 at 1:55 PM, Boris Ostrovsky > <boris.ostrovsky at oracle.com> wrote: >> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the >> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit >> (and sysret32 in compat mode) pv ops, as suggested by Andy. >> >> As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not >> used anymore by anyone and so can be removed. > This whole series is: > > Acked-by: Andy Lutomirski <luto at kern...

...;'s sysenter generates is not exactly the same as the one the kernel expects, so the direct access to the threadinfo structure doesn''t work properly. What''s the difference in the frames? I guess the other reason for the separate PV Xen sysenter entrypoint is to deal with sysexit not working. I addressed this by implementing a sysexit pvop using iret, though I think I could just set the TIF_IRET flag in threadinfo. Anyway, could you look at these changes and see if anything problematic leaps out. I''m also having debugging it, since xenctx and gdbserver-xen do...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've put together an always tempfail & sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. The hooks are so that: a) config file setting: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When no mode is specified, it defaults to "default", which is the current behaviour. In sendmail mode, mail_send_r...

The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit (and sysret32 in compat mode) pv ops, as suggested by Andy. (I ended up patching TEST with XOR to avoid extra NOPs, even though I said yesterday it would be wrong. It's not wrong) As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not used anymore by anyone and so can be...

The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit (and sysret32 in compat mode) pv ops, as suggested by Andy. (I ended up patching TEST with XOR to avoid extra NOPs, even though I said yesterday it would be wrong. It's not wrong) As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not used anymore by anyone and so can be...

The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit (and sysret32 in compat mode) pv ops, as suggested by Andy. As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not used anymore by anyone and so can be removed. v2: * patch both TEST and JZ intructions with a single JMP * Add magic prefix to X86_FEATURE_XENPV comment t...

The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit (and sysret32 in compat mode) pv ops, as suggested by Andy. As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not used anymore by anyone and so can be removed. v2: * patch both TEST and JZ intructions with a single JMP * Add magic prefix to X86_FEATURE_XENPV comment t...

From: Boris Ostrovsky <boris.ostrovsky at oracle.com> commit 88c15ec90ff16880efab92b519436ee17b198477 upstream. As result of commit "x86/xen: Avoid fast syscall path for Xen PV guests", the irq_enable_sysexit pv op is not called by Xen PV guests anymore and since they were the only ones who used it we can safely remove it. Signed-off-by: Boris Ostrovsky <boris.ostrovsky at oracle.com> Reviewed-by: Borislav Petkov <bp at suse.de> Acked-by: Andy Lutomirski <luto at kernel.org> Cc: Andre...

.../entry_32.S index 901f186..e2158ae 100644 --- a/arch/x86/entry/entry_32.S +++ b/arch/x86/entry/entry_32.S @@ -329,7 +329,8 @@ sysenter_past_esp: * Return back to the vDSO, which will pop ecx and edx. * Don't bother with DS and ES (they already contain __USER_DS). */ - ENABLE_INTERRUPTS_SYSEXIT + sti + sysexit .pushsection .fixup, "ax" 2: movl $0, PT_FS(%esp) @@ -552,11 +553,6 @@ ENTRY(native_iret) iret _ASM_EXTABLE(native_iret, iret_exc) END(native_iret) - -ENTRY(native_irq_enable_sysexit) - sti - sysexit -END(native_irq_enable_sysexit) #endif ENTRY(overflow) diff...

This is a note to let you know that I've just added the patch titled x86/paravirt: Remove the unused irq_enable_sysexit pv op to the 4.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: x86-paravirt-remove-the-unused-irq_enable_sysexit-pv-op.patch and it can be found in the queue-4.4 subdirectory. If you, or a...

...cted by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event injection by emulating the native processor exception frame interface. N.B. Sti; Sysexit is a required abstraction, as the STI instruction implies holdoff of interrupts, which is destroyed by any NOP padding. There is a race condition is present in all virtualization solutions in which the guest kernel may issue a raw IRET instruction, as the IRET instruction is not properly virtualiz...

...cted by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event injection by emulating the native processor exception frame interface. N.B. Sti; Sysexit is a required abstraction, as the STI instruction implies holdoff of interrupts, which is destroyed by any NOP padding. There is a race condition is present in all virtualization solutions in which the guest kernel may issue a raw IRET instruction, as the IRET instruction is not properly virtualiz...

...e is no reason to load __KERNEL_DS into %ds or %es. __KERNEL_DS is actually quite poorly named, and is in fact the kernel stack selector. The kernel uses __USER_DS internally as both %es and %ds (since it is a flat CPL-3 accessible data segment that allows the kernel to skip reloading segments on sysexit). The reason for avoiding the __KERNEL_DS macro is it is predefined as an RPL zero segment. Diffs against: linux-2.6.13-rc6 Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/arch/i386/kernel/entry.S =================================================================== --- li...

...e is no reason to load __KERNEL_DS into %ds or %es. __KERNEL_DS is actually quite poorly named, and is in fact the kernel stack selector. The kernel uses __USER_DS internally as both %es and %ds (since it is a flat CPL-3 accessible data segment that allows the kernel to skip reloading segments on sysexit). The reason for avoiding the __KERNEL_DS macro is it is predefined as an RPL zero segment. Diffs against: linux-2.6.13-rc6 Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.13/arch/i386/kernel/entry.S =================================================================== --- li...

Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of

Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of

Hello! I just migrated from Ubuntu 12.04 LTS to 14.04 LTS and thereby from Dovecot 2.0.19 to 2.2.9. I've been using dovecot-antispam plugin with great success for the past year with 2.0.19, but after this migration, I've been seeing the exit status code 134 in the syslog when attempting to debug the Dovecot Antispam plugin not working after the migration. I have some debugging output in

Hello, I am studing Xen hypercall now. I found that hypercall is invoked via hypercall_page, which is only filled with (in no-hypervisor-kernel-mode ): mov $i, %eax int $0x82 ret Why not invoked the hypercall directly by "int $0x82" ? What''s the advantage of using hypercall_page? Thanks, Wu _______________________________________________ Xen-devel mailing list

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 if there is no Return-Path in the message and Deliver cannot deliver the message, no DSN is sent _and_ the MTA is returned 0 (aka success) return code, which leads to mail loss. This is not the case, when the message actually finds a Return-Path, but fails to invoke the MTA. - --- src/deliver/mail-send.c (revision 47) +++