On 10/28/24 00:32, Zhijian Li (Fujitsu) wrote:
On 28/10/2024 14:25, Shuah Khan wrote:
On 10/28/24 00:06, Zhijian Li (Fujitsu) wrote:
linux/tools/testing/selftests/watchdog# make run_tests
TAP version 13
1..1
# timeout set to 45
# selftests: watchdog: watchdog-test
# Watchdog Ticking Away!
# .
On 28/10/2024 14:25, Shuah Khan wrote:
> On 10/28/24 00:06, Zhijian Li (Fujitsu) wrote:
>> linux/tools/testing/selftests/watchdog# make run_tests
>> TAP version 13
>> 1..1
>> # timeout set to 45
>> # selftests: watchdog: watchdog-test
>> # Watchdog Ticking Away!
>> # .
linux/tools/testing/selftests/watchdog# make run_tests
TAP version 13
1..1
# timeout set to 45
# selftests: watchdog: watchdog-test
# Watchdog Ticking Away!
# .#
not ok 1 selftests: watchdog: watchdog-test # TIMEOUT 45 seconds
And i got warning in dmesg
On 10/27/24 23:45, Zhijian Li (Fujitsu) wrote:
On 28/10/2024 13:31, Shuah Khan wrote:
On 10/27/24 22:02, Zhijian Li (Fujitsu) wrote:
On 28/10/2024 11:29, Shuah Khan wrote:
On 10/27/24 18:50, Zhijian Li (Fujitsu) wrote:
On 27/10/2024 08:28, Shuah Khan wrote:
On 10/24/24 19:39, Li Zhijia
On 28/10/2024 13:31, Shuah Khan wrote:
> On 10/27/24 22:02, Zhijian Li (Fujitsu) wrote:
>>
>>
>> On 28/10/2024 11:29, Shuah Khan wrote:
>>> On 10/27/24 18:50, Zhijian Li (Fujitsu) wrote:
On 27/10/2024 08:28, Shuah Khan wrote:
> On 10/24/24 19:39, Li Zhijian wrote:
>> Curren
On 10/27/24 22:02, Zhijian Li (Fujitsu) wrote:
On 28/10/2024 11:29, Shuah Khan wrote:
On 10/27/24 18:50, Zhijian Li (Fujitsu) wrote:
On 27/10/2024 08:28, Shuah Khan wrote:
On 10/24/24 19:39, Li Zhijian wrote:
Currently, watchdog-test keep running until it gets a SIGINT. However,
when watc
Hi Antonio,
kernel test robot noticed the following build errors:
[auto build test ERROR on 03fc07a24735e0be8646563913abf5f5cb71ad19]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonio-Quartulli/netlink-add-NLA_POLICY_MAX_LEN-macro/20241025-173611
base: 03fc07a24735e0be8646563913a
On Sat, 26 Oct 2024 at 07:50, Nicolin Chen wrote:
>
> Now a vIOMMU holds a shareable nesting parent HWPT. So, it can act like
> that nesting parent HWPT to allocate a nested HWPT.
>
> Support that in the IOMMU_HWPT_ALLOC ioctl handler, and update its kdoc.
>
> Also, add an iommufd_hwpt_nested_allo
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Add a new iommufd_viommu FIXTURE and setup it up with a vIOMMU object.
>
> Any new vIOMMU feature will be added as a TEST_F under that.
>
> Signed-off-by: Nicolin Chen
Reviewed-by: Kevin Tian
On 10/27/24 18:50, Zhijian Li (Fujitsu) wrote:
On 27/10/2024 08:28, Shuah Khan wrote:
On 10/24/24 19:39, Li Zhijian wrote:
Currently, watchdog-test keep running until it gets a SIGINT. However,
when watchdog-test is executed from the kselftests framework, where it
launches test via timeout wh
On 28/10/2024 11:29, Shuah Khan wrote:
> On 10/27/24 18:50, Zhijian Li (Fujitsu) wrote:
>>
>>
>> On 27/10/2024 08:28, Shuah Khan wrote:
>>> On 10/24/24 19:39, Li Zhijian wrote:
Currently, watchdog-test keep running until it gets a SIGINT. However,
when watchdog-test is executed from the
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Add a new driver-type for ARM SMMUv3 to enum iommu_viommu_type.
> Implement
> an arm_vsmmu_alloc() with its viommu op
> arm_vsmmu_domain_alloc_nested(),
> to replace arm_smmu_domain_alloc_nesting(). As an initial step, copy the
>
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:51 AM
>
> +
> +/**
> + * struct iommu_vdevice_alloc - ioctl(IOMMU_VDEVICE_ALLOC)
> + * @size: sizeof(struct iommu_vdevice_alloc)
> + * @viommu_id: vIOMMU ID to associate with the virtual device
> + * @dev_id: The pyhsical device to allocat
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Following the previous vIOMMU series, this adds another vDEVICE structure,
> representing the association from an iommufd_device to an
> iommufd_viommu.
> This gives the whole architecture a new "v" layer:
>
> __
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Implement the viommu alloc/free functions to increase/reduce refcount of
> its dependent mock iommu device. User space can verify this loop via the
> IOMMU_VIOMMU_TYPE_SELFTEST.
>
> Signed-off-by: Nicolin Chen
Reviewed-by: Kev
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> For an iommu_dev that can unplug (so far only this selftest does so), the
> viommu->iommu_dev pointer has no guarantee of its life cycle after it is
> copied from the idev->dev->iommu->iommu_dev.
>
> Track the user count of the
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> A nested domain now can be allocated for a parent domain for a vIOMMU
> object. Rework the existing allocators to prepare for the latter case.
>
> Signed-off-by: Nicolin Chen
Reviewed-by: Kevin Tian
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Use these inline helpers to shorten those container_of lines.
>
> Note that one of them goes back and forth between iommu_domain and
> mock_iommu_domain, which isn't necessary. So drop its container_of.
>
> Signed-off-by: Nicol
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> Now a vIOMMU holds a shareable nesting parent HWPT. So, it can act like
> that nesting parent HWPT to allocate a nested HWPT.
>
> Support that in the IOMMU_HWPT_ALLOC ioctl handler, and update its kdoc.
>
> Also, add an iommufd
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> 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 a
> From: Nicolin Chen
> Sent: Saturday, October 26, 2024 7:50 AM
>
> + * @viommu_alloc: Allocate an iommufd_viommu on a physical IOMMU
> instance behind
> + *the @dev, as the set of virtualization resources
> shared/passed
> + *to user space IOMMU instance. And asso
> From: Jason Gunthorpe
> Sent: Friday, October 25, 2024 11:43 PM
>
> On Fri, Oct 25, 2024 at 08:34:05AM +, Tian, Kevin wrote:
> > > The vIOMMU object should be seen as a slice of a physical IOMMU
> instance
> > > that is passed to or shared with a VM. That can be some HW/SW
> resources:
> >
> From: Jason Gunthorpe
> Sent: Friday, October 25, 2024 11:24 PM
>
> On Fri, Oct 25, 2024 at 08:47:40AM +, Tian, Kevin wrote:
> > > From: Jason Gunthorpe
> > > Sent: Tuesday, October 22, 2024 9:16 PM
> > >
> > > On Tue, Oct 22, 2024 at 04:59:07PM +0800, Baolu Lu wrote:
> > >
> > > > Is it f
On 25/10/2024 18:05, Mark Brown wrote:
> On Fri, Oct 25, 2024 at 09:40:04AM +0800, Li Zhijian wrote:
>
>> index 12dc3fcd3456..1407fd24a97b 100644
>> --- a/tools/testing/selftests/alsa/.gitignore
>> +++ b/tools/testing/selftests/alsa/.gitignore
>> @@ -1,3 +1,5 @@
>> mixer-test
>> pcm-test
>>
On 27/10/2024 08:28, Shuah Khan wrote:
> On 10/24/24 19:39, Li Zhijian wrote:
>> Currently, watchdog-test keep running until it gets a SIGINT. However,
>> when watchdog-test is executed from the kselftests framework, where it
>> launches test via timeout which will send SIGTERM in time up. This c
On Sun, Oct 27, 2024 at 11:02:31PM +0800, Zhangfei Gao wrote:
> On Sat, 26 Oct 2024 at 07:51, Nicolin Chen wrote:
> > +/* Caller should xa_lock(&viommu->vdevs) to protect the return value */
> > +struct device *iommufd_viommu_find_dev(struct iommufd_viommu *viommu,
> > +
On Sun, Oct 27, 2024 at 01:09:43AM +0300, Dmitry Baryshkov wrote:
> Document compatible for audio DSP on Qualcomm SAR2130P platform.
>
> Signed-off-by: Dmitry Baryshkov
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,sm8350-pas.yaml | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-
On Sat, 26 Oct 2024 at 07:51, Nicolin Chen wrote:
>
> This avoids a bigger trouble of exposing struct iommufd_device and struct
> iommufd_vdevice in the public header.
>
> Signed-off-by: Nicolin Chen
> ---
> include/linux/iommufd.h| 8
> drivers/iommu/iommufd/driver.c | 13
28 matches
Mail list logo
