search for: sysexits

> On Jan 10, 2025, at 11:33, Steffen Nurpmeso <steffen at sdaoden.eu> wrote: > > Fyi there is the >35 years old BSD sysexits.h that unfortunately > did not become standardized, but is widely available nonetheless. If you mean [this sysexits][*], that doesn't seem great for several reasons: 1. "A few programs exit with the following non-portable error codes. Do not use them." 2. The only statuses liste...

Jim Knoble wrote in <06004671-E946-4462-9076-5C11D5D46E40 at pobox.com>: |> On Jan 10, 2025, at 11:33, Steffen Nurpmeso <steffen at sdaoden.eu> wrote: |> Fyi there is the >35 years old BSD sysexits.h that unfortunately |> did not become standardized, but is widely available nonetheless. | |If you mean [this sysexits][*], that doesn't seem great for several \ |reasons: | |1. "A few programs exit with the following non-portable error codes. \ |Do not use them." This is...

On 19/11/15 22: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. >>

On 19/11/15 22: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. >>

I implemented sysenter for 32-on-64, since it seemed straightforward enough. It mostly works, but every now and again I get vcpus just hanging in blocked state, as if events are being lost or ignored. Its very similar to the symptoms that other people have reported against the pvops kernel, which I have not managed to reproduce. Perhaps using sysenter is exacerbating an existing bug...

...|> |>> Adding a new exit status for the |>> no-keys-in-agent case would be |>> acceptable too I think. |> |> I interpreted that as "make ssh-add exit with status 2 or 3 or 99, \ |> for example, as opposed to 1". Fyi there is the >35 years old BSD sysexits.h that unfortunately did not become standardized, but is widely available nonetheless. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) | |In Fall and Win...

-----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

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

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

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

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

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

Xen PV guests have been the only ones using it and now they don't. Signed-off-by: Boris Ostrovsky <boris.ostrovsky at oracle.com> --- arch/x86/entry/entry_32.S | 8 ++------ arch/x86/include/asm/paravirt.h | 7 ------- arch/x86/include/asm/paravirt_types.h | 9 --------- arch/x86/kernel/asm-offsets.c | 3 --- arch/x86/kernel/paravirt.c | 7

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

...teffen Nurpmeso wrote in <20250111031926.AGltefav at steffen%sdaoden.eu>: |Jim Knoble wrote in | <06004671-E946-4462-9076-5C11D5D46E40 at pobox.com>: ||> On Jan 10, 2025, at 11:33, Steffen Nurpmeso <steffen at sdaoden.eu> wrote: ||> Fyi there is the >35 years old BSD sysexits.h that unfortunately ||> did not become standardized, but is widely available nonetheless. || ||If you mean [this sysexits][*], that doesn't seem great for several \ ||reasons: ... |I recalled something, and it could be the manual change was around |the standard discussion even: ......

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected 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

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected 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

i386 Transparent Paravirtualization Patch #2 Changes required to low level fault / system call code for supporting transparent paravirtualization where the kernel may be running at non-zero CPL. The testing of VM_MASK and CS together uses a neat trick which is now extended to support CPL 0,1,2 kernels. Note that assembly code must test against __ESPFIX_SS, the 16-bit stack on interrupts and

i386 Transparent Paravirtualization Patch #2 Changes required to low level fault / system call code for supporting transparent paravirtualization where the kernel may be running at non-zero CPL. The testing of VM_MASK and CS together uses a neat trick which is now extended to support CPL 0,1,2 kernels. Note that assembly code must test against __ESPFIX_SS, the 16-bit stack on interrupts and

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