search for: address_

Displaying 12 results from an estimated 12 matches for "address_".

Did you mean: address
2008 Mar 13
3
newbie question: pxelinux.cfg/default question
Hello all, I understand that during PXE boot, it goes into the pxelinux.cfg and it states: 1. "it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for any host.) If that file is not found, it will remove one hex digit and try
2008 Jun 28
2
[LLVMdev] need to store the address of a variable
...I get the following LLVM Code %a_addr = alloca i32 ; <i32*> [#uses=2] %d = alloca i32* ; <i32**> [#uses=2] store i32 %a, i32* %a_addr store i32* %a_addr, i32** %d, align 4 how can I generate such an Instruction? When I use name = variables.inst[i]->getName() + "address_"; Instruction *AD = new AllocaInst(Type::Int32Ty, ConstantInt::get(Type::Int32Ty, 1), name, alloca_point); StoreInst *SI = new StoreInst(variables.inst[i], AD, alloca_point); StoreInst(SI, GEP, alloca_point); the compiler is happy, but I get the following error at run time: Instructions.cpp...
2003 Nov 25
1
About sound modules in Asterisk. And call gnophone-asterisk-h323
...66 10.16.96.148.5036 > 10.16.96.149.5036: udp 37 (DF) [tos 0x10] 17:37:00.957994 10.16.96.149.5036 > 10.16.96.148.5036: udp 37 (DF) [tos 0x10] ............................................................................. But un the gatekeeper communication process I only see packets in one address_ namor:/home/sanz# tcpdumpatm -n -i atm0 tcpdumpatm: listening on atm0 17:56:13.659867 80.98.102.206.10004 > 80.98.105.178.1720: S 1165965604:1165965604(0) win 18280 <mss 9140,sackOK,timestamp 4428183360,nop,wscale 0> (DF) 17:56:13.660000 80.98.105.178.1720 > 80.98.102.206.10004: S421...
2008 Jun 28
0
[LLVMdev] need to store the address of a variable
...%a */, ptr_a_addr, false, label_4); StoreInst* void_6 = new StoreInst(ptr_a_addr, ptr_d, false, label_4); void_5 is putting the argument %a into the locally allocated %a_addr. void_6 is taking %a_addr and storing it into %d. > When I use > > name = variables.inst[i]->getName() + "address_"; > Instruction *AD = new AllocaInst(Type::Int32Ty, > ConstantInt::get(Type::Int32Ty, 1), name, alloca_point); > StoreInst *SI = new StoreInst(variables.inst[i], AD, alloca_point); > StoreInst(SI, GEP, alloca_point); > That looks wrong. The last line, "StoreInst(SI, GEP...
2003 Nov 16
0
[LLVMdev] Packages
On Sun, 2003-11-16 at 17:13, Chris Lattner wrote: > > The point here is that XPL needs to keep track of what a given variable > > represents at the source level. If the compiler sees a map that is > > initially small it might represent it in LLVM assembly as a vector of > > pairs. Later on, it gets optimized into being a hash table. In order to > > do that and keep
2003 Nov 16
3
[LLVMdev] Packages
> The point here is that XPL needs to keep track of what a given variable > represents at the source level. If the compiler sees a map that is > initially small it might represent it in LLVM assembly as a vector of > pairs. Later on, it gets optimized into being a hash table. In order to > do that and keep track of things, I need to know that the vector of > pairs is
2007 Apr 18
4
[patch 3/9] Guest page hinting: volatile page cache.
...d_debug_level; * sure the page is locked and that nobody else uses it - or that usage * is safe. The caller must hold a write_lock on the mapping's tree_lock. */ -void __remove_from_page_cache(struct page *page) +void inline __remove_from_page_cache_nocheck(struct page *page) { struct address_space *mapping = page->mapping; @@ -127,6 +127,28 @@ void __remove_from_page_cache(struct pag mapping->nrpages--; __dec_zone_page_state(page, NR_FILE_PAGES); } + +void __remove_from_page_cache(struct page *page) +{ + /* + * Check if the discard fault handler already removed + * the pa...
2007 Apr 18
4
[patch 3/9] Guest page hinting: volatile page cache.
...d_debug_level; * sure the page is locked and that nobody else uses it - or that usage * is safe. The caller must hold a write_lock on the mapping's tree_lock. */ -void __remove_from_page_cache(struct page *page) +void inline __remove_from_page_cache_nocheck(struct page *page) { struct address_space *mapping = page->mapping; @@ -127,6 +127,28 @@ void __remove_from_page_cache(struct pag mapping->nrpages--; __dec_zone_page_state(page, NR_FILE_PAGES); } + +void __remove_from_page_cache(struct page *page) +{ + /* + * Check if the discard fault handler already removed + * the pa...
2007 Jun 28
6
[patch 0/6] resend: guest page hinting version 5.
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.
2007 Jun 28
6
[patch 0/6] resend: guest page hinting version 5.
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.
2007 May 11
6
[patch 0/6] [rfc] guest page hinting version 5
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
2007 May 11
6
[patch 0/6] [rfc] guest page hinting version 5
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