search for: ccv

Dear R-List members, I want to check if a set of measurements follows better a gamma or a lognormal distribution (see data below). Using shapiro.test I can test for normality (shapiro.test(log (Lt)). To test for gamma (and normal) distribution I would use ks.test but I need to specify its shape and scale. How should I calculate these values in R? I tried > Lt.fit <- glm(Lt ~ 1,

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

...m my Rails application. I am doing this in my action require ''soap/wsdlDriver'' factory = SOAP::WSDLDriverFactory.new(TRANSIDIOM_WSDL_URL) soap = factory.create_rpc_driver soap.wiredump_file_base="#{RAILS_ROOT}/log/transidiom.log" param = %(<Request name="com.wm.ccv.rpgrouter.seagull.CustomerProfileResCom"> <Input> <CompanyCode>110</CompanyCode> <CustomerNumber>2442</CustomerNumber> <UserName>ccvdev2</UserName> <Password>ccvdev2</Password> <LibrarySuffix>ORC</LibrarySuffix> <targetHos...

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place

Hi. I rewrote the patch according to the comments. I adopted generating in-place code because it looks the quickest way. The point Eddie wanted to discuss is how to generate code and its ABI. i.e. in-place generating v.s. direct jump v.s. indirect function call Indirect function call doesn't make sense because ivt.S is compiled multi times. And it is up to pv instances to choose in-place

Hi, Has anyone succeeded in building llvm on AIX? Currently I am investigating several tools for code analyses and I came upon Clang. We at CCV run our core business applications on RS6000/AIX. At our department we develop those applications. The reviews on clang look very promising. I was able to build and run it on Linux (SuSE 12.1) without any problems. I tested it with valgrind sources and was impressed by the issues it found. Buildin...

...8 ifs : 8000000000000a98 ip : >[<f0000000040375a0>] >(XEN) ip is at csched_schedule+0x970/0xf70 >(XEN) unat: 0000000000000000 pfs : 0000000000000a98 rsc : 0000000000000003 >(XEN) rnat: 0000121008226018 bsps: f00000000405a6c0 pr : 000000000001aaa9 >(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70033f >(XEN) csd : 0000000000000000 ssd : 0000000000000000 >(XEN) b0 : f0000000040375a0 b6 : f000000004049c80 b7 : e000000000100800 >(XEN) f6 : 0fffbccccccccc8c00000 f7 : 0ffd9a200000000000000 >(XEN) f8 : 0ffff8000000000000000 f9 : 10002a000000...

Hi Alex: I was looking at an ia64 bug report and noticed that we don''t actually free IRQs in the free_irq_vector hypercall. This would eventually lead to alloc_irq_vector failing. Unless I''m mistaken something like calling pci_disable_device and pci_enable_device can lead to this situation. So I''m wondering what the original problem was and how could we resolve it

...6]=r15,16 >+.mem.offset 8,0; st8.spill [r17]=r14,16 >+ dep r14=-1,r0,60,4 >+ ;; >+.mem.offset 0,0; st8.spill [r16]=r2,16 >+.mem.offset 8,0; st8.spill [r17]=r3,16 >+ adds r2=VMM_PT_REGS_R16_OFFSET,r1 >+ adds r14 = VMM_VCPU_GP_OFFSET,r13 >+ ;; >+ mov r8=ar.ccv >+ ld8 r14 = [r14] >+ ;; >+ mov r1=r14 /* establish kernel global pointer */ >+ ;; \ >+ bsw.1 >+ ;; >+ alloc r14=ar.pfs,0,0,1,0 // must be first in an insn group >+ mov out0=r13 >+ ;; >+ ssm p...

...6]=r15,16 >+.mem.offset 8,0; st8.spill [r17]=r14,16 >+ dep r14=-1,r0,60,4 >+ ;; >+.mem.offset 0,0; st8.spill [r16]=r2,16 >+.mem.offset 8,0; st8.spill [r17]=r3,16 >+ adds r2=VMM_PT_REGS_R16_OFFSET,r1 >+ adds r14 = VMM_VCPU_GP_OFFSET,r13 >+ ;; >+ mov r8=ar.ccv >+ ld8 r14 = [r14] >+ ;; >+ mov r1=r14 /* establish kernel global pointer */ >+ ;; \ >+ bsw.1 >+ ;; >+ alloc r14=ar.pfs,0,0,1,0 // must be first in an insn group >+ mov out0=r13 >+ ;; >+ ssm p...

...10 ifs : 8000000000000307 ip : [<a0000001004c2ca0>] Not tainted (2.6.26-rc4xen-ia64-dirty) ip is at dev_kfree_skb_irq+0x20/0x1a0 unat: 0000000000000000 pfs : 400000000000040b rsc : 0000000000000007 rnat: 0000000000000000 bsps: 0000000000000000 pr : 000000000000a941 ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f csd : 0000000000000000 ssd : 0000000000000000 b0 : a0000001003efb70 b6 : a000000100070e40 b7 : a000000100070e40 f6 : 1003e000000fcb75352b1 f7 : 1003e000000000014ff97 f8 : 1003e00fcb74fc3454d80 f9 : 1003e0000000080000000 f10 : 1003e0000000000001431 f1...