search for: urk

...Ben Bolker conjectured that boot() might be able to handle this. Getting the NAs into the coefficients is a bit of a fag, but. I tried: func <- function(data, idx) { clyde <- coef(lm(Score~ Time + factor(Country),data=data)) ccc <- coef(lm(Score~ Time + factor(Country),data=data[idx,])) urk <- rep(NA,length(clyde)) names(urk) <-names(clyde) urk[names(ccc)] <- ccc urk } It produced a result: > > set.seed(42) > > B= boot(e, func, R=1000) > B > > ORDINARY NONPARAMETRIC BOOTSTRAP > > > Call: > boot(data = e, statistic = func, R = 1000) >...

...ble intervals, and those aren't the same thing even if they are sometimes numerically similar. Duncan Murdoch > func <- function(data, idx) { > clyde <- coef(lm(Score~ Time + factor(Country),data=data)) > ccc <- coef(lm(Score~ Time + factor(Country),data=data[idx,])) > urk <- rep(NA,length(clyde)) > names(urk) <-names(clyde) > urk[names(ccc)] <- ccc > urk > } > > It produced a result: > >>> set.seed(42) >>> B= boot(e, func, R=1000) >> B >> >> ORDINARY NONPARAMETRIC BOOTSTRAP >> >> >&gt...

...unt. I use 266 to describe the root cause. ``` 49 _dmerror_unmount 50 _dmerror_mount 51 52 echo "Compare files" 53 md5sum $testdir/file1 | _filter_scratch 54 md5sum $testdir/file2 | _filter_scratch 55 56 echo "CoW and unmount" 57 sync 58 _dmerror_load_error_table 59 urk=$($XFS_IO_PROG -f -c "pwrite -S 0x63 -b $bufsize 0 $filesize" \ 60 -c "fdatasync" $testdir/file2 2>&1) 61 echo $urk >> $seqres.full 62 echo "$urk" | grep -q "error" || _fail "pwrite did not fail" 63 64 echo "Clean up the m...

...r_unmount > 50 _dmerror_mount > 51 > 52 echo "Compare files" > 53 md5sum $testdir/file1 | _filter_scratch > 54 md5sum $testdir/file2 | _filter_scratch > 55 > 56 echo "CoW and unmount" > 57 sync > 58 _dmerror_load_error_table > 59 urk=$($XFS_IO_PROG -f -c "pwrite -S 0x63 -b $bufsize 0 $filesize" \ > 60 -c "fdatasync" $testdir/file2 2>&1) > 61 echo $urk >> $seqres.full > 62 echo "$urk" | grep -q "error" || _fail "pwrite did not fail" > 63 >...

...e is not a multiple of replacement length > > > ########################################## > Score=c(345,564,467,675,432,346,476,512,567,543,234,435,654,411,356,658,432,345,432,345, 345,456,543,501) > > Country=c("Italy", "Italy", "Italy", "Turkey", "Turkey", "Turkey", "USA", "USA", "USA", "Korea", "Korea", "Korea", "Portugal", "Portugal", "Portugal", "UK", "UK", "UK", "Poland", "Po...

...unt. I use 266 to describe the root cause. ``` 49 _dmerror_unmount 50 _dmerror_mount 51 52 echo "Compare files" 53 md5sum $testdir/file1 | _filter_scratch 54 md5sum $testdir/file2 | _filter_scratch 55 56 echo "CoW and unmount" 57 sync 58 _dmerror_load_error_table 59 urk=$($XFS_IO_PROG -f -c "pwrite -S 0x63 -b $bufsize 0 $filesize" \ 60 -c "fdatasync" $testdir/file2 2>&1) 61 echo $urk >> $seqres.full 62 echo "$urk" | grep -q "error" || _fail "pwrite did not fail" 63 64 echo "Clean up the m...

...rands haven't been added to the machieninstrs yet, then they > > won't be returned. > > Hmm...this is definitely NOT true in my copy. During register allocation > these implicit defs are not returned. By then the instructions are most > definitely fully constructed. :) Urk. It seems things are worse than that, even. By the time things hit regalloc, the def/use lists seem to be completely out of date. Instructions that exist in the function are not reflected in the def lists, for example. Simple register-to-register copies are completely missed. So far I've o...

...> As far as I can see, this is an issue of the BIOS firmware not handling > things at all - there is not even a code path to the function that boots > Linux via BIOS. I can only guess that this is a result of a failed merge > followed by not testing 6.00 on BIOS before releasing it. Urk, sorry about that. This is fixed in 6.01-pre1, which I just released. This isn't the result of a failed merge, but I did (clearly) fail to remember to test booting a kernel under BIOS before releasing 6.00. Apologies. -- Matt Fleming, Intel Open Source Technology Center

What's a reliable way to prefer one patterns over another? I have two patterns with different predicates. Pattern A has a very general predicate to catch a wide variety of store instructions. Pattern B has a narrower predicate meant to catch very specific store instructions that would also satisfy the predicate for Pattern A. We used to match Pattern B just fine but after changing .td

...ate meant to catch very specific store instructions that would also > satisfy the predicate for Pattern A. > > We used to match Pattern B just fine but after changing .td files a bit the > selector is always picking Pattern A. > > Setting AddedComplexity doesn't seem to help. Urk. I set AddedComplexity on the wrong thing. Seems to work now. -Dave

...to the machieninstrs yet, then they >>> won't be returned. >> >> Hmm...this is definitely NOT true in my copy. During register allocation >> these implicit defs are not returned. By then the instructions are most >> definitely fully constructed. :) > > Urk. It seems things are worse than that, even. You should try updating to mainline. I have no idea what snapshot you have. Barring a serious bug, the use/def chains cannot get out of date. When a machineinstr is inserted into a function or when an operand is added to the instr, it is automatic...

...am expecting AMD to release the proper driver for my card but the thing that has me is that this odd "CPU overload" only started happening on the 8.41.7 drivers. Before that WoW ran ok, FPS was too low to really play properly but it ran. hoping some other WoWers can comment. regards, Burkey -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20071005/f205e75e/attachment.htm

On Thu, Apr 25, 2019 at 10:03 PM Pankaj Gupta <pagupta at redhat.com> wrote: > > Dont support 'MAP_SYNC' with non-DAX files and DAX files > with asynchronous dax_device. Virtio pmem provides > asynchronous host page cache flush mechanism. We don't > support 'MAP_SYNC' with virtio pmem and xfs. > > Signed-off-by: Pankaj Gupta <pagupta at

On Thu, Apr 25, 2019 at 10:03 PM Pankaj Gupta <pagupta at redhat.com> wrote: > > Dont support 'MAP_SYNC' with non-DAX files and DAX files > with asynchronous dax_device. Virtio pmem provides > asynchronous host page cache flush mechanism. We don't > support 'MAP_SYNC' with virtio pmem and xfs. > > Signed-off-by: Pankaj Gupta <pagupta at

On Thu, July 20, 2017 8:07 am, Peter Larsen wrote: > On 07/16/2017 12:30 PM, Andreas Benzler wrote: >> - The firewall is placed in front of the cluster. >> - After you have found a safe base for this, you freeze it. > > Sorry, but this statement really urks me in a wrong way. Why do you > think a firewall is the ONLY part that needs to be provide security? > That's the way I read this statement - that it doesn't matter anywhere > else. In addition, the majority of attacks and compromises come from > INSIDE the firewall - ie. the...

Halo Valeri, let's think about what a hpc cluster is for. Second, one should always ask the question where security is to be applied,then one can come to the following decision: - The firewall is placed in front of the cluster. - After you have found a safe base for this, you freeze it. - We have a rsync of centos and epel on the head node. >From here, we can always reinstall a node

...red into map, to > > keep the size of the map low. The first time a query is made within a > > large block, it would compute the indices of all loads and stores > > within the block. > > This is a simpler approach and should have the same effect. I'll code it > up. Urk. After looking at doing this today, I realized it won't work. The problem is that RewriteSingleStoreAlloca has this loop: for (; &*I != OnlyStore; ++I) { // scan block for store. if (isa<LoadInst>(I) && I->getOperand(0) == AI) break; It's lo...

...kernel because in that situation the dpkg starts a qemu which cannot attach > properly and in the end both hang and qemu has to be killed hard(er). All a bit > ugly. So this is likely nothing you need but just in case: > > (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763831) Urk. I wonder if this explains some of the bugs about the initscript hanging we had around earlier. Anyway, your diff seems to only add some code to xenstored_start, I was expecting a change to qemu_start -- did you find that code was OK in the end? Or did you end up switching to --exec? Thanks, Ian....

...uctions that would also > > satisfy the predicate for Pattern A. > > > > We used to match Pattern B just fine but after changing .td files a bit > the > > selector is always picking Pattern A. > > > > Setting AddedComplexity doesn't seem to help. > > Urk. I set AddedComplexity on the wrong thing. Seems to work now. > > -Dave > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc...

...39; with virtio pmem and xfs. > > > > Signed-off-by: Pankaj Gupta <pagupta at redhat.com> > > --- > > fs/xfs/xfs_file.c | 9 ++++++--- > > 1 file changed, 6 insertions(+), 3 deletions(-) > > Darrick, does this look ok to take through the nvdimm tree? <urk> forgot about this, sorry. :/ > > > > diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c > > index a7ceae90110e..f17652cca5ff 100644 > > --- a/fs/xfs/xfs_file.c > > +++ b/fs/xfs/xfs_file.c > > @@ -1203,11 +1203,14 @@ xfs_file_mmap( > > struct fi...