search for: saved_stack

...I get some feedback): Have a new instruction, called "yield" to return a value from a co-routine, preserving the state. Thus, we immediately know which functions are co-routines. Each co-routine will have a new stack. Associate each co-routine with a thread-local global variable (called saved_stack here, will have to be mangled with the name of the co-routine) which points to the start stack block for that co-routine. This will be the first block in the chain of blocks to follow. The structure of the block will be similar to the structure of a regular stack block, except that it will also ha...

...gt; Have a new instruction, called "yield" to return a value from a > co-routine, preserving the state. Thus, we immediately know which > functions are co-routines. Each co-routine will have a new stack. > Associate each co-routine with a thread-local global variable (called > saved_stack here, will have to be mangled with the name of the > co-routine) which points to the start stack block for that co-routine. > This will be the first block in the chain of blocks to follow. > > The structure of the block will be similar to the structure of a regular > stack block, exc...

...nstruction, called "yield" to return a value from a >> co-routine, preserving the state. Thus, we immediately know which >> functions are co-routines. Each co-routine will have a new stack. >> Associate each co-routine with a thread-local global variable (called >> saved_stack here, will have to be mangled with the name of the >> co-routine) which points to the start stack block for that co-routine. >> This will be the first block in the chain of blocks to follow. >> >> The structure of the block will be similar to the structure of a regular >&...

I find this pattern as below from <llvm-source-tree>/test/CodeGen/Mips/alloca.ll. Do you know what front end pattern can be translated into this pattern alloca with variable argument %size as below? Can some one help me? I am writing the llvm backend document --http://jonathan2251.github.com/lbd/index.html now. %tmp1 = alloca i8, i32 %size, align 4 // has %size variable, not pattern,

...ed "yield" to return a value from a >>> co-routine, preserving the state. Thus, we immediately know which >>> functions are co-routines. Each co-routine will have a new stack. >>> Associate each co-routine with a thread-local global variable (called >>> saved_stack here, will have to be mangled with the name of the >>> co-routine) which points to the start stack block for that co-routine. >>> This will be the first block in the chain of blocks to follow. >>> >>> The structure of the block will be similar to the structure of...

On Sun, Apr 10, 2011 at 4:16 PM, Chris Lattner <clattner at apple.com> wrote: > > On Apr 10, 2011, at 2:45 PM, Talin wrote: > > I wonder - would something like this allow for multiple stacks for a single > thread? I'm thinking of something like continuations / fibers / green > threads, which would be very handy. > > > I haven't looked at the proposal, but

On Apr 10, 2011, at 2:45 PM, Talin wrote: > I wonder - would something like this allow for multiple stacks for a single thread? I'm thinking of something like continuations / fibers / green threads, which would be very handy. I haven't looked at the proposal, but yes, this would be very useful functionality for LLVM to provide. -Chris > > On Wed, Mar 23, 2011 at 3:07 AM,

...> Don't think you need vmalloc.h here. > +int kvm_arch_vcpu_ioctl_set_regs(struct kvm_vcpu *vcpu, struct kvm_regs > *regs) > +{ [snip] > + copy_from_user(&vcpu->arch.guest, regs->saved_guest, > + sizeof(union context)); > + copy_from_user(vcpu + 1, regs->saved_stack + sizeof(struct > kvm_vcpu), > + IA64_STK_OFFSET - sizeof(struct kvm_vcpu)); You need to check the return values from copy_from_user() here and deal with possible failure. > + vcpu->arch.apic = kzalloc(sizeof(struct kvm_lapic), GFP_KERNEL); > + vcpu->arch.apic->vcpu = vcpu;...

...> Don't think you need vmalloc.h here. > +int kvm_arch_vcpu_ioctl_set_regs(struct kvm_vcpu *vcpu, struct kvm_regs > *regs) > +{ [snip] > + copy_from_user(&vcpu->arch.guest, regs->saved_guest, > + sizeof(union context)); > + copy_from_user(vcpu + 1, regs->saved_stack + sizeof(struct > kvm_vcpu), > + IA64_STK_OFFSET - sizeof(struct kvm_vcpu)); You need to check the return values from copy_from_user() here and deal with possible failure. > + vcpu->arch.apic = kzalloc(sizeof(struct kvm_lapic), GFP_KERNEL); > + vcpu->arch.apic->vcpu = vcpu;...

Hi Xiantao, Some more nit-picking, though some of this is a bit more important to fixup. Cheers, Jes > +typedef struct thash_data { Urgh! argh! Please avoid typedefs unless you really need them, see Chapter 5 of Documentation/CodingStyle for details. > diff --git a/include/asm-ia64/kvm_host.h b/include/asm-ia64/kvm_host.h > new file mode 100644 > index 0000000..522bde0 > ---

Hi Xiantao, Some more nit-picking, though some of this is a bit more important to fixup. Cheers, Jes > +typedef struct thash_data { Urgh! argh! Please avoid typedefs unless you really need them, see Chapter 5 of Documentation/CodingStyle for details. > diff --git a/include/asm-ia64/kvm_host.h b/include/asm-ia64/kvm_host.h > new file mode 100644 > index 0000000..522bde0 > ---

...32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32" target triple = "i386-pc-linux-gnu" %struct..0f = type { i8, i8 } define i8* @p(i32 %n) nounwind { entry: %n_addr = alloca i32 ; <i32*> [#uses=2] %retval = alloca i8* ; <i8**> [#uses=2] %saved_stack.9 = alloca i8* ; <i8**> [#uses=2] %tmp = alloca i8* ; <i8**> [#uses=2] %F.8 = alloca %struct..0f* ; <%struct..0f**> [#uses=3] %n.0 = alloca i32 ; <i32*> [#uses=9] %"alloca point" = bitcast i32 0 to i32 ; <i32> [#uses=0] store i32 %n, i32* %n_addr %...