search for: val8

...inal file is using merged cell in its first column, which gives the name of the observation. (I am dealing with repeated measurements for the same observation) So when I open the dataframe in R it looks like this Col1 Col2 Col3 name1 val1 val2 val3 val4 .... name2 val5 val6 val7 val8 Everything is fine, except that the name of the observation is on the first line and the following rows are empty. Until a new observation starts, where a new name appears in the respective row and the following rows are empty and so on. The number of rows is fixed for each observation. How can I...

...VPCI_FIELD(bar), cap->bar); + pci_write_config_dword(dev, cfg + VPCI_FIELD(length), length); + pci_write_config_dword(dev, cfg + VPCI_FIELD(offset), offset); + return 0; +} + +static u32 viommu_cread(struct pci_dev *dev, int cfg, + struct viommu_cap_config *cap, u32 length, u32 offset) +{ + u8 val8; + u16 val16; + u32 val32; + int out = cfg + sizeof(struct virtio_pci_cap); + + if (viommu_switch_pci_cfg(dev, cfg, cap, length, offset)) + return 0; + + switch (length) { + case 1: + pci_read_config_byte(dev, out, &val8); + return val8; + case 2: + pci_read_config_word(dev, out, &val16...

...te_config_dword(dev, cfg + VPCI_FIELD(length), length); > + pci_write_config_dword(dev, cfg + VPCI_FIELD(offset), offset); > + return 0; > +} > + > +static u32 viommu_cread(struct pci_dev *dev, int cfg, > + struct viommu_cap_config *cap, u32 length, u32 offset) > +{ > + u8 val8; > + u16 val16; > + u32 val32; > + int out = cfg + sizeof(struct virtio_pci_cap); > + > + if (viommu_switch_pci_cfg(dev, cfg, cap, length, offset)) > + return 0; > + > + switch (length) { > + case 1: > + pci_read_config_byte(dev, out, &val8); > + return val8;...

Hi, when I compile (clang -O3) and optimize (opt -O3) C-code like this: sum1 = val1 + val2; sum2 = val3 + val4; sum3 = val5 + val6; sum4 = val7 + val8; sum5 = sum1 + sum2; sum6 = sum3 + sum4; sum7 = sum5 + sum6; sum += sum7; I get bitcode like this: if.end152: ; preds = %if.then150, %if.else146, %if.end137 %val8.0 = phi i32 [ -2048, %if.then150 ], [ %conv38, %if.else146 ], [ 204...

I'm seeking feedback on multi-platform support for virtio-iommu. At the moment only devicetree (DT) is supported and we don't have a pleasant solution for other platforms. Once we figure out the topology description, x86 support is trivial. Since the IOMMU manages memory accesses from other devices, the guest kernel needs to initialize the IOMMU before endpoints start issuing DMA.

I'm seeking feedback on multi-platform support for virtio-iommu. At the moment only devicetree (DT) is supported and we don't have a pleasant solution for other platforms. Once we figure out the topology description, x86 support is trivial. Since the IOMMU manages memory accesses from other devices, the guest kernel needs to initialize the IOMMU before endpoints start issuing DMA.