Re: uvm_pmemrange.c questions

2011-03-18 Thread Ariane van der Steldt
On Tue, Mar 01, 2011 at 05:37:49PM -0600, Amit Kulkarni wrote: > I found 2 possible null pointers by clang static analyzer and I have > attached it to email later. I was also reading the code in this file > and I found out that > > 1) most of the time in uvm_pmr_getpages(), a newly inserted printf

Re: uvm_pmemrange.c questions

2011-03-02 Thread Ted Unangst
On Tue, Mar 1, 2011 at 6:37 PM, Amit Kulkarni wrote: > 2) another question. Most allocations are either 1 or a power of two. > But there are a few allocations of 3 pages, specifically most > allocations are either 1 page, 2 page, some 16's, some 32's, one > single 128. I printed this info by check

Re: uvm_pmemrange.c questions

2011-03-02 Thread Amit Kulkarni
Hi, They are also inline text in the original email, in case attachments didn't go through. I attached because people have problem with gmail mangling diff files. But still I am putting them up here for download uvm diff https://filestogeaux.lsu.edu/public/download.php?FILE=akulka1/172984cgyg8 dm

Re: uvm_pmemrange.c questions

2011-03-02 Thread Alexander Hall
On 03/02/11 00:37, Amit Kulkarni wrote: > Hi, > > I found 2 possible null pointers by clang static analyzer and I have > attached it to email later. uh-oh... > [demime 1.01d removed an attachment of type application/octet-stream which > had a name of uvm_pmemrange_1.diff] > [demime 1.01d remove

uvm_pmemrange.c questions

2011-03-01 Thread Amit Kulkarni
Hi, I found 2 possible null pointers by clang static analyzer and I have attached it to email later. I was also reading the code in this file and I found out that 1) most of the time in uvm_pmr_getpages(), a newly inserted printf at line 792 is never reached. I put that printf just to check and v