search for: baolu

...__phys_to_dma(dev, io_tlb_start), ^~~~~~~~~~~~ swiotlb_start drivers/iommu/intel-iommu.c:3990:24: note: each undeclared identifier is reported only once for each function it appears in vim +3990 drivers/iommu/intel-iommu.c cfb94a372f2d4e Lu Baolu 2019-09-06 3941 cfb94a372f2d4e Lu Baolu 2019-09-06 3942 static dma_addr_t cfb94a372f2d4e Lu Baolu 2019-09-06 3943 bounce_map_single(struct device *dev, phys_addr_t paddr, size_t size, cfb94a372f2d4e Lu Baolu 2019-09-06 3944 enum dma_data_direction dir, unsigned long att...

...not be visible outside of this definition or declaration int (*mmap)(struct mdev_device *mdev, struct vm_area_struct *vma); ^~~~~~~~~~~~~~ vim +/attr +69 include/linux/mdev.h 7b96953bc640b6 Kirti Wankhede 2016-11-17 14 8ac13175cbe985 Lu Baolu 2019-04-12 15 /* 8ac13175cbe985 Lu Baolu 2019-04-12 16 * Called by the parent device driver to set the device which represents 8ac13175cbe985 Lu Baolu 2019-04-12 17 * this mdev in iommu protection scope. By default, the iommu device is 8ac13175cbe985 Lu Baolu...

...not be visible outside of this definition or declaration int (*mmap)(struct mdev_device *mdev, struct vm_area_struct *vma); ^~~~~~~~~~~~~~ vim +/attr +69 include/linux/mdev.h 7b96953bc640b6 Kirti Wankhede 2016-11-17 14 8ac13175cbe985 Lu Baolu 2019-04-12 15 /* 8ac13175cbe985 Lu Baolu 2019-04-12 16 * Called by the parent device driver to set the device which represents 8ac13175cbe985 Lu Baolu 2019-04-12 17 * this mdev in iommu protection scope. By default, the iommu device is 8ac13175cbe985 Lu Baolu...

...inition or declaration > int (*mmap)(struct mdev_device *mdev, struct vm_area_struct *vma); > ^~~~~~~~~~~~~~ > > vim +/attr +69 include/linux/mdev.h > > 7b96953bc640b6 Kirti Wankhede 2016-11-17 14 > 8ac13175cbe985 Lu Baolu 2019-04-12 15 /* > 8ac13175cbe985 Lu Baolu 2019-04-12 16 * Called by the parent device driver to set the device which represents > 8ac13175cbe985 Lu Baolu 2019-04-12 17 * this mdev in iommu protection scope. By default, the iommu device is > 8ac13175cbe985 L...

From: Thierry Reding <treding at nvidia.com> Most IOMMU drivers only need to free the memory allocated for each reserved region. Instead of open-coding the loop to do this in each driver, extract the code into a common function that can be used by all these drivers. Changes in v3: - add Reviewed-by from Jean-Philippe Brucker on virtio patch - add Acked-by from Will Deacon on ARM SMMU patch

On Thu, Dec 19, 2019 at 09:53:22AM +0800, Lu Baolu wrote: > Please tweak the title to > > "iommu/vt-d: Use generic_iommu_put_resv_regions()" > > then, > > Acked-by: Lu Baolu <baolu.lu at linux.intel.com> > > Best regards, > baolu Joerg, do you want me to resend with this change or is it more effici...

On Wed, Apr 29, 2020 at 01:42:13PM +0800, Lu Baolu wrote: > On 2020/4/29 12:57, Michael S. Tsirkin wrote: > > On Wed, Apr 29, 2020 at 10:22:32AM +0800, Lu Baolu wrote: > > > On 2020/4/29 4:41, Michael S. Tsirkin wrote: > > > > On Tue, Apr 28, 2020 at 11:19:52PM +0530, Srivatsa Vaddagiri wrote: > > > > >...

Hi Dave, I built successfully an xvm 3.3 system. However, I found virt-manager and virt-install don''t work. I attached the error messages of both as below. xm tool seems to work. I can run OpenSolaris200811 LiveCD and install it onto file based disk. The error messages of virt-manager: ====start of error message==== Unable to open connection to hypervisor URI ''xen'':

Hi Baolu, On Wed, Apr 15, 2020 at 02:10:03PM +0800, Lu Baolu wrote: > On 2020/4/14 21:15, Joerg Roedel wrote: > > > + /* Device is probed already if in a group */ > > + if (iommu_group_get(dev) != NULL) > > Same as > if (iommu_group_get(dev)) > ? > > By the way, do we...

On Wed, Apr 29, 2020 at 10:22:32AM +0800, Lu Baolu wrote: > On 2020/4/29 4:41, Michael S. Tsirkin wrote: > > On Tue, Apr 28, 2020 at 11:19:52PM +0530, Srivatsa Vaddagiri wrote: > > > * Michael S. Tsirkin<mst at redhat.com> [2020-04-28 12:17:57]: > > > > > > > Okay, but how is all this virtio specific?...

I am trying to build Xen from on-src-b79. According to opensolaris website, all xVM sources should be in the on-src-b79 tree, and no additional sources are required. I followed the procedure for doing the nightly build, and I expected that, as a result I will build, along with the Solaris kernel, the xen.gz image. I was hoping to copy that xen.gz image to my test machine, so I can boot with my own

On Thu, Oct 26, 2023 at 10:49:24AM +0800, Lu Baolu wrote: > Hi folks, > > This series implements the functionality of delivering IO page faults to > user space through the IOMMUFD framework for nested translation. Nested > translation is a hardware feature that supports two-stage translation > tables for IOMMU. The second-stage t...

> From: Jason Gunthorpe <jgg at ziepe.ca> > Sent: Thursday, November 2, 2023 8:48 PM > > On Thu, Oct 26, 2023 at 10:49:24AM +0800, Lu Baolu wrote: > > Hi folks, > > > > This series implements the functionality of delivering IO page faults to > > user space through the IOMMUFD framework for nested translation. > Nested > > translation is a hardware feature that supports two-stage translation > > ta...

Hi Baolu, On Tue, May 30, 2023 at 01:37:07PM +0800, Lu Baolu wrote: > - The timeout value for the pending page fault messages. Ideally we > should determine the timeout value from the device configuration, but > I failed to find any statement in the PCI specification (version 6.x). > A de...

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

iommufd follows the same design as KVM and uses memory cgroups to limit the amount of kernel memory a iommufd file descriptor can pin down. The various internal data structures already use GFP_KERNEL_ACCOUNT to charge its own memory. However, one of the biggest consumers of kernel memory is the IOPTEs stored under the iommu_domain and these allocations are not tracked. This series is the first

On Wed, Apr 15, 2020 at 02:36:20PM +0800, Lu Baolu wrote: > On 2020/4/14 21:15, Joerg Roedel wrote: > > From: Joerg Roedel<jroedel at suse.de> > > > > Add call-backs to 'struct iommu_ops' as an alternative to the > > add_device() and remove_device() call-backs, which will be removed when > > all drive...

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

I''m happy to announce that we have moved the xen-unstable.hg Solaris dom0 development out to the OpenSolaris community. For hard core developers, you can download, build, and run Solaris dom0 and xen-unstable bits following the instructions at the end of this post. We are currently sync''d up to changeset #17644 (~May 15th). Hopefully we will sync up with xen-unstable.hg every