Re: [PATCH v6 01/10] iommufd/viommu: Add IOMMUFD_OBJ_VDEVICE and IOMMU_VDEVICE_ALLOC ioctl

2024-11-07 Thread Alexey Kardashevskiy
On 31/10/24 08:35, Nicolin Chen wrote: Introduce a new IOMMUFD_OBJ_VDEVICE to represent a physical device (struct device) against a vIOMMU (struct iommufd_viommu) object in a VM. This vDEVICE object (and its structure) holds all the infos and attributes in the VM, regarding the device related to

Re: [PATCH v6 05/13] iommufd/viommu: Add IOMMU_VIOMMU_ALLOC ioctl

2024-11-06 Thread Alexey Kardashevskiy
On 31/10/24 08:34, Nicolin Chen wrote: Add a new ioctl for user space to do a vIOMMU allocation. It must be based on a nesting parent HWPT, so take its refcount. IOMMU driver wanting to support vIOMMUs must define its IOMMU_VIOMMU_TYPE_ in the uAPI header and implement a viommu_alloc op in its i

Re: PCI: Correct the resource_alignment parameter example

2019-06-05 Thread Alexey Kardashevskiy
Argh, it should have had "PATCH" in the subject, I broke my scripts so they run git format-patch --subject-prefix="". Sorry. Repost? On 06/06/2019 13:25, Alexey Kardashevskiy wrote: > The option description requires an order and so does the option > parsing code, howev

PCI: Correct the resource_alignment parameter example

2019-06-05 Thread Alexey Kardashevskiy
The option description requires an order and so does the option parsing code, however the example uses a size, fix this. Fixes: 8b078c603249 ("PCI: Update "pci=resource_alignment" documentation") Signed-off-by: Alexey Kardashevskiy --- Documentation/admin-guide/kernel-param

Re: [PATCH v3 -next 1/2] ARM: sunxi: add support for H2+ SoC

2016-12-05 Thread Alexey Kardashevskiy
On 05/12/16 20:19, Maxime Ripard wrote: > On Fri, Dec 02, 2016 at 11:05:12PM +0800, Icenowy Zheng wrote: >> Allwinner H2+ is a quad-core Cortex-A7 SoC. >> >> It is very like H3, that they share the same SoC ID (0x1680), and H3 >> memory maps as well as drivers works well on the SoC. >> >> Signed-of

Re: [PATCH v3 -next 2/2] ARM: dts: sunxi: add support for Orange Pi Zero board

2016-12-05 Thread Alexey Kardashevskiy
On 03/12/16 02:05, Icenowy Zheng wrote: > Orange Pi Zero is a board that came with the new Allwinner H2+ SoC and a > SDIO Wi-Fi chip by Allwinner (XR819). > > Add a device tree file for it. > > Signed-off-by: Icenowy Zheng > --- > Changes since v2: > - Merged SDIO Wi-Fi patch into it. > - SDIO W

Re: [PATCH v3 -next 1/2] ARM: sunxi: add support for H2+ SoC

2016-12-04 Thread Alexey Kardashevskiy
On 03/12/16 02:05, Icenowy Zheng wrote: > Allwinner H2+ is a quad-core Cortex-A7 SoC. > > It is very like H3, that they share the same SoC ID (0x1680), and H3 > memory maps as well as drivers works well on the SoC. What git tree is this made against of? Thanks. > > Signed-off-by: Icenowy Zhen

Re: [linux-sunxi] [PATCH v3 -next 2/2] ARM: dts: sunxi: add support for Orange Pi Zero board

2016-12-04 Thread Alexey Kardashevskiy
On 03/12/16 03:41, Chen-Yu Tsai wrote: > Hi, > > On Fri, Dec 2, 2016 at 11:05 PM, Icenowy Zheng wrote: >> Orange Pi Zero is a board that came with the new Allwinner H2+ SoC and a >> SDIO Wi-Fi chip by Allwinner (XR819). >> >> Add a device tree file for it. >> >> Signed-off-by: Icenowy Zheng >> -

Re: [PATCH 3/3] ARM: dts: sunxi: enable SDIO Wi-Fi on Orange Pi Zero

2016-11-29 Thread Alexey Kardashevskiy
On 29/11/16 21:19, Icenowy Zheng wrote: > > 2016年11月29日 15:16于 Alexey Kardashevskiy 写道: >> >> >> >> On Wed, Nov 23, 2016 at 6:59 PM, Maxime Ripard > wrote: >>> >>> Hi, >>> >>> On Tue, Nov 22, 2016 at 12:24:21AM +0800, Ice

Re: [RFC v6 04/10] PCI: Add support for enforcing all MMIO BARs to be page aligned

2016-04-25 Thread Alexey Kardashevskiy
On 04/18/2016 08:56 PM, Yongji Xie wrote: When vfio passthrough a PCI device of which MMIO BARs are smaller than PAGE_SIZE, guest will not handle the mmio accesses to the BARs which leads to mmio emulations in host. This is because vfio will not allow to passthrough one BAR's mmio page which may

Re: [RFC PATCH v4 1/7] PCI: Add a new option for resource_alignment to reassign alignment

2016-03-09 Thread Alexey Kardashevskiy
On 03/07/2016 06:48 PM, Yongji Xie wrote: When using resource_alignment kernel parameter, the current implement reassigns the alignment by changing resources' size which can potentially break some drivers. How can this possibly break any driver?... It rounds up, not down, what do I miss here?