search for: stack_pointer

...;From all discussions on the LLVM list, the one that has shown more consistently as a problem was the reservation of allocatable registers. Some background... My original intent was to be able to support the kernel unwinding code. There was a discussion, in which we agree that for that a building stack_pointer would do. But the GCC community has voiced two concerns: there is already a feature for that widely in use, and that feature is more generic. Back to the LLVM list, people were concerned with the implementation and semantics of reserving allocatable registers (yes, we do reserve some of them speci...

..., 0x7ffff7af423d <PyEval_EvalFrameEx+17725>, 0x7ffff7af10a3 <PyEval_EvalFrameEx+5027>, 0x7ffff7af3c31 <PyEval_EvalFrameEx+16177>, 0x7ffff7af3b8f <PyEval_EvalFrameEx+16015>, 0x7ffff7af423d <PyEval_EvalFrameEx+17725> <repeats 108 times>} stack_pointer = <optimized out> next_instr = <optimized out> opcode = 131 oparg = <optimized out> why = WHY_NOT err = 0 x = <optimized out> v = <optimized out> ---Type <return> to continue, or q <return> to quit---...

On 29 March 2014 10:37, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > I'd like to separate this into two different functionalities: We will. But in reverse order. > (1) Reserve registers, so that normal allocation won't use them. > This can be done on a global or function level. This is the most controversial part of the proposal and is the least important to

On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: > Anyone? Can you please post a gdb backtrace --full? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 862 bytes Desc: This is a digitally signed message part URL:

...ellent reasons to not implement the dangerous feature > and instead to provide a significantly safer feature and direct users either > to not do the dangerous things, or if they are trying to do the safe thing, > use the feature which was designed for it. The point here is that __builting_stack_pointer doesn't provide enough additional value to be worth deviating from the norm. True, you can only use the stack pointers and not allocatable registers, and you don't have to name the register, so it's slightly more target-independent, but those were the only reasons. Named registers exis...

...00 +0200 +++ linux-2.6-patched/arch/s390/kernel/traps.c 2006-09-01 12:50:25.000000000 +0200 @@ -65,6 +65,7 @@ extern void pfault_interrupt(struct pt_r static ext_int_info_t ext_int_pfault; #endif extern pgm_check_handler_t do_monitor_call; +extern pgm_check_handler_t do_discard_fault; #define stack_pointer ({ void **sp; asm("la %0,0(15)" : "=&d" (sp)); sp; }) @@ -734,6 +735,9 @@ void __init trap_init(void) pgm_check_table[0x1C] = &space_switch_exception; pgm_check_table[0x1D] = &hfp_sqrt_exception; pgm_check_table[0x40] = &do_monitor_call; +#i...

...00 +0200 +++ linux-2.6-patched/arch/s390/kernel/traps.c 2006-09-01 12:50:25.000000000 +0200 @@ -65,6 +65,7 @@ extern void pfault_interrupt(struct pt_r static ext_int_info_t ext_int_pfault; #endif extern pgm_check_handler_t do_monitor_call; +extern pgm_check_handler_t do_discard_fault; #define stack_pointer ({ void **sp; asm("la %0,0(15)" : "=&d" (sp)); sp; }) @@ -734,6 +735,9 @@ void __init trap_init(void) pgm_check_table[0x1C] = &space_switch_exception; pgm_check_table[0x1D] = &hfp_sqrt_exception; pgm_check_table[0x40] = &do_monitor_call; +#i...

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.

After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic

After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic