search for: mb2

...that the sizes of the memoperands for each + // MI are the same. The values can be different, so lets only check the sizes. + // If the sizes between one of the memoperands differ, then the instructions are + // not identical. + for (MachineInstr::mmo_iterator mb1 = memoperands_begin(), mb2 = Other->memoperands_begin() + me = memoperands_end(); mb1 != me; ++mb1, ++mb2) { + if (mb1->getSize() != mb2->getSize() || + mb1->getFlags() != mb2->getFlags() || + mb1->getOffset() != mb2->getOffset()) { + return false; + } + } +...

...: $namespace $namespace folder $namespace folder folder1a $namespace folder folder1b $namespace folder folder1c The resulting IMAPv4 session is: mb1 LIST "" "#mbox.%" * LIST (\Noselect \HasChildren) "." "#mbox.folder" mb1 OK List completed. mb2 LIST "" "#mbox.folder.%" * LIST (\Noselect \HasChildren) "." "#mbox.folder." * LIST (\NoInferiors \UnMarked) "." "#mbox.folder.folder1a" * LIST (\NoInferiors \UnMarked) "." "#mbox.folder.folder1b" * LIST (\NoInf...

...e memoperands for each > + // MI are the same. The values can be different, so lets only check the sizes. > + // If the sizes between one of the memoperands differ, then the instructions are > + // not identical. > + for (MachineInstr::mmo_iterator mb1 = memoperands_begin(), mb2 = Other->memoperands_begin() > + me = memoperands_end(); mb1 != me; ++mb1, ++mb2) { > + if (mb1->getSize() != mb2->getSize() || > + mb1->getFlags() != mb2->getFlags() || > + mb1->getOffset() != mb2->getOffset()) { > + return...

Dear All, I am analysing some data for a colleague (not my data, gotta be published so I cannot divulge). My response variable is the number of matings observed per day for some fruitlies. My factors are: Day: the observations were taken on 9 days Regime: 3 selection regimes Line: 3 replicates per selection regime. I have 81 observations in total The lines are coded A to I, so I do not need

Is there any way to get printf type functionality inside the kernel from dtrace probes. Basically I want to dump progress through flow in my device driver. Something like: DTRACE_PRINTF("Inside chip reset, mailboxes %x %x %x %x %x %x %x %x", mb1, mb2, .....); ... ... DTRACE_PRINTF("reset failed: reason %s", failure_reasons[err]); I may have several such probes and they may change very frequently during the development. The dtrace script to enable these probes and dump values can be very simple and will just enable all the probes in...

Hi, I have some problems with my repeated measures analysis. When I compute it with SPSS I get different results than with R. Probably I am doing something wrong in R. I have two groups (1,2) both having to solve a task under two conditions (1,2). That is one between subject factor (group) and one within subject factor (task). I tried the following: aov(Score

..._syscall () #22 0x804849b in ?? () #23 0x804813e in ?? () (kgdb) list 1577 register caddr_t cp; 1578 register int32_t t1, t2; 1579 caddr_t bpos, dpos, cp2; 1580 int error = 0, wccflag = NFSV3_WCCRATTR; 1581 struct mbuf *mreq, *mrep, *md, *mb, *mb2; 1582 int v3 = NFS_ISV3(dvp); 1583 1584 nfsstats.rpccnt[NFSPROC_REMOVE]++; 1585 nfsm_reqhead(dvp, NFSPROC_REMOVE, 1586 NFSX_FH(v3) + NFSX_UNSIGNED + nfsm_rndup(namelen)); (kgdb) p *proc Cannot access memory at address 0x0. (kgdb) p *dvp $3 = {v_...

...const char *name, uint64_t tgt, uint64_t size) "%s tgt=0x%"PRIx64" size=0x%"PRIx64 > vfio_pci_nvlink2_setup_quirk_lnkspd(const char *name, uint32_t link_speed) "%s link_speed=0x%x" > > +vfio_pci_vmd_quirk_shadow_regs(const char *name, uint64_t mb1, uint64_t mb2) "%s membar1_phys=0x%"PRIx64" membar2_phys=0x%"PRIx64 > +vfio_pci_vmd_quirk_vmlock(const char *name, uint8_t vmlock) "%s vmlock=0x%x" > + > # common.c > vfio_region_write(const char *name, int index, uint64_t addr, uint64_t data, unsigned size) " (%s...

...ffff : PCI Bus 10000:02 > > > The VMD guest driver does the translation on the supplied address using > pci_add_resource_offset prior to creating the root bus and enumerating > the domain: > > offset[0] = vmd->dev->resource[VMD_MEMBAR1].start - > readq(membar2 + MB2_SHADOW_OFFSET); > offset[1] = vmd->dev->resource[VMD_MEMBAR2].start - > readq(membar2 + MB2_SHADOW_OFFSET + 8); > ... > pci_add_resource(&resources, &vmd->resources[0]); > pci_add_resource_offset(&resources, &vmd->resources[1], offset[0]); > pci_...

...p(tdev->iommu.domain, tdev->iommu.group); > iommu_domain_free(tdev->iommu.domain); > + iommu_group_put(tdev->iommu.group); > } > #endif > } > -- > 2.15.1 > -------------- next part -------------- [0000.235] I> Welcome to MB2(TBoot-BPMP)(version: 01.00.160913-t186-M-00.00-mobile-f4c42291) [0000.244] I> Default Heap @ [0xd486400 - 0xd488400] [0000.248] I> DMA Heap @ [0x84900000 - 0x85300000] [0000.253] I> bit @ 0xd480000 [0000.256] I> BR-BCT relocated to 0xf7f20000 [0000.260] I> Boot-device: eMMC [0000.264...

On 9/7/2012 12:12 PM, Krzysztof Parzyszek wrote: > On 9/7/2012 7:20 AM, Matthew Curtis wrote: >> >> The attached patch implements one possible solution. It introduces a >> position stack and a couple of directives: >> >> * 'CHECK-PUSH:' pushes the current match position onto the stack. >> * 'CHECK-POP:' pops the top value off of the stack

With linux-next-2017-12-14, I get a crash when nouveau is loaded by systemd-udevd. [ 12.050625] Unable to handle kernel NULL pointer dereference at virtual address 00000058 [ 12.050627] Mem abort info: [ 12.050628] ESR = 0x96000004 [ 12.050630] Exception class = DABT (current EL), IL = 32 bits [ 12.050631] SET = 0, FnV = 0 [ 12.050632] EA = 0, S1PTW = 0 [ 12.050633] Data

...n files are added > (presumable because git doesn't have a hash yet to use for guessing the > right file). > > Worst case you could try applying the changes manually, they're fairly > small. > > Thierry -------------- next part -------------- [0000.231] I> Welcome to MB2(TBoot-BPMP)(version: 01.00.160913-t186-M-00.00-mobile-f4c42291) [0000.239] I> Default Heap @ [0xd486400 - 0xd488400] [0000.244] I> DMA Heap @ [0x84900000 - 0x85300000] [0000.249] I> bit @ 0xd480000 [0000.252] I> BR-BCT relocated to 0xf7f20000 [0000.256] I> Boot-device: eMMC [0000.260...