Re: [RFC PATCH 0/8] Shared Virtual Memory virtualization for VT-d

Hi Liu Yi, I haven't started to read the code yet, however, could you detail more please? It emulates a SVM capable iommu device in a VM? Or It speeds up device's DMA access in a VM? Or it is a new facility introduced for a VM? Could you please add a bit more for its usage? Thanks! On

Re: [PATCH v5 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges

Hi Oza, [auto build test ERROR on v4.9-rc8] [cannot apply to glikely/devicetree/next iommu/next next-20170505] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5 15/32] efi: Update efi_mem_type() to return an error rather than 0

On Tue, Apr 18, 2017 at 04:19:00PM -0500, Tom Lendacky wrote: > The efi_mem_type() function currently returns a 0, which maps to > EFI_RESERVED_TYPE, if the function is unable to find a memmap entry for > the supplied physical address. Returning EFI_RESERVED_TYPE implies that > a memmap entry

Re: [PATCH v4 3/3] PCI/of fix of_dma_get_range; get PCI specific dma-ranges

/20170507-141549 config: c6x-evmc6678_defconfig (attached as .config) compiler: c6x-elf-gcc (GCC) 6.2.0 reproduce: wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config