Fixed the patch:
vfio/pci: Allow MMIO regions to be exported through dma-buf
Signed-off-by: Xu Yilun
---
drivers/vfio/pci/vfio_pci_config.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci_config.c
b/drivers/vfio/pci/vfio_pci_config.c
index ef
This is to support private device/MMMIO assignment, but is an
incomplete implementation as discussed. In this case, VFIO PCI act as
the exporter for MMIO regions and KVM is the importer. KVM imports the
dma-buf FD and gets MMIO pfn through dma_buf_ops.get_pfn(), then map
the pfn in KVM MMU. KVM sho
On Wed May 28, 2025 at 5:38 AM JST, Joel Fernandes wrote:
> Hello,
> I split this particular patch into 3 patches:
>
> gpu: nova-core: vbios: Add support for FWSEC ucode extraction
> gpu: nova-core: vbios: Add support to look up PMU table in FWSEC
> gpu: nova-core: vbios: Add base support for VBIOS
GUP uses pXX_devmap() calls to see if it needs to a get a reference on
the associated pgmap data structure to ensure the pages won't go
away. However it's a driver responsibility to ensure that if pages are
mapped (ie. discoverable by GUP) that they are not offlined or removed
from the memmap so th
Changes from v2 of the RFC[1]:
- My ZONE_DEVICE refcount series has been merged as commit 7851bf649d42 (Patch
series
"fs/dax: Fix ZONE_DEVICE page reference counts", v9.) which is included in
v6.15 so have rebased on top of that.
- No major changes required for the rebase other than fixi
DAX no longer requires device PTEs as it always has a ZONE_DEVICE page
associated with the PTE that can be reference counted normally. Other users
of pte_devmap are drivers that set PFN_DEV when calling vmf_insert_mixed()
which ensures vm_normal_page() returns NULL for these entries.
There is no r
All PFN_* pfn_t flags have been removed. Therefore there is no longer
a need for the pfn_t type and all uses can be replaced with normal
pfns.
Signed-off-by: Alistair Popple
Reviewed-by: Christoph Hellwig
---
arch/x86/mm/pat/memtype.c| 6 +-
drivers/dax/device.c
It's no longer used so remove it.
Signed-off-by: Alistair Popple
---
mm/memremap.c | 27 ---
1 file changed, 27 deletions(-)
diff --git a/mm/memremap.c b/mm/memremap.c
index 2ea5322..5deb181 100644
--- a/mm/memremap.c
+++ b/mm/memremap.c
@@ -38,30 +38,6 @@ unsigned long
Now that DAX and all other reference counts to ZONE_DEVICE pages are
managed normally there is no need for the special devmap PTE/PMD/PUD
page table bits. So drop all references to these, freeing up a
software defined page table bit on architectures supporting it.
Signed-off-by: Alistair Popple
A
DAX was the only thing that created pmd_devmap and pud_devmap entries
however it no longer does as DAX pages are now refcounted normally and
pXd_trans_huge() returns true for those. Therefore checking both pXd_devmap
and pXd_trans_huge() is redundant and the former can be removed without
changing b
PFN_DEV no longer exists. This means no devmap PMDs or PUDs will be
created, so checking for them is redundant. Instead mappings of pages that
would have previously returned true for pXd_devmap() will return true for
pXd_trans_huge()
Signed-off-by: Alistair Popple
---
arch/powerpc/mm/book3s64/ha
The PFN_MAP flag is no longer used for anything, so remove it. The
PFN_SG_CHAIN and PFN_SG_LAST flags never appear to have been used so
also remove them.
Signed-off-by: Alistair Popple
Reviewed-by: Christoph Hellwig
---
include/linux/pfn_t.h | 31 +++
mm/
PFN_DEV was used by callers of dax_direct_access() to figure out if the
returned PFN is associated with a page using pfn_t_has_page() or
not. However all DAX PFNs now require an assoicated ZONE_DEVICE page so can
assume a page exists.
Other users of PFN_DEV were setting it before calling
vmf_inser
Previously dax pages were skipped by the pagewalk code as pud_special() or
vm_normal_page{_pmd}() would be false for DAX pages. Now that dax pages are
refcounted normally that is no longer the case, so add explicit checks to
skip them.
Signed-off-by: Alistair Popple
---
include/linux/memremap.h
The kernel test robot reported a warning related to the use of "$ref"
type definitions for custom endpoint properties
- "ti,lvds-vod-swing-clock-microvolt" and
- "ti,lvds-vod-swing-data-microvolt".
Using "$ref" with "uint32-array" is not correctly handled in this
context. Removing "$ref" and relyi
Fetch VFIO specific dma-buf data to see if the dma-buf is eligible to
be assigned to CoCo VM as private MMIO.
KVM expects host unaccessible MMIO regions been mapped in private
roots. So need to identify VFIO dma-buf by successfully getting VFIO
specific dma-buf data. VFIO dma-buf also provides the
When device is TSM Bound, some of its MMIO regions are controlled by
secure firmware. E.g. TDX Connect would require these MMIO regions
mappeed in S-EPT and never unmapped until device Unbound. Zapping bars
irrespective of TSM Bound state may cause unexpected secure firmware
errors. It is always sa
Extend KVM_SET_USER_MEMORY_REGION2 to support mapping vfio_dmabuf
backed MMIO region into a guest.
The main purpose of this change is for KVM to map MMIO resources
without firstly mapping into the host, similar to what is done in
guest_memfd. The immediate use case is for CoCo VMs to support priva
Implement TDX Connect enforced sequences for TSM unbind. The enforced
sequences are:
1. STOP TDI via TDISP message STOP_INTERFACE
2. Private MMIO unmap from Secure EPT
3. Trusted Device Context Table cleanup for the TDI
4. TDI ownership reclaim and metadata free
Step 2 is the responsibili
From: Dan Williams
TDX depends on a platform firmware module that is invoked via
instructions similar to vmenter (i.e. enter into a new privileged
"root-mode" context to manage private memory and private device
mechanisms). It is a software construct that depends on the CPU vmxon
state to enable
Add optional PCI driver callbacks to notify TSM events. For now, these
handlers may be called during pci_tsm_unbind(). By calling these
handlers, TSM driver askes for external collaboration to finish entire
TSM unbind flow.
If platform TSM driver could finish TSM bind/unbind all by itself, don't
c
VFIO invalidates MMIOs on disable_mmio() so that KVM could unmap them
from S-EPT. VFIO re-validate MMIOs on recover_mmio() so that KVM could
map them again for shared assigned device.
For now these handlers are mainly for Intel TDX Connect, but should
have no impact since other platform TSM driver
Add basic skeleton for bind()/unbind()/guest_req() handlers.
Specifically, tdx_tdi_devifmt/devif_create() declare the TDI ownership
to TD. tdx_tdi_mmiomt_create() declares the MMIO ownership to TD.
tdx_tdi_request(TDX_TDI_REQ_BIND) locks the TDI.
No detailed TDX Connect implementation.
Signed-of
From: Dan Williams
Recall that a TEE Security Manager (TSM) is a platform agent that speaks
the TEE Device Interface Security Protocol (TDISP) to PCIe devices and
manages private memory resources for the platform. The tdx_tsm driver
loads against a device of the same name registered at TDX Module
From: Alexey Kardashevskiy
Add TSM Guest request uAPI against iommufd_vdevice to forward various
TSM attestation & acceptance requests from guest to TSM driver/secure
firmware. This uAPI takes function only after TSM Bind.
After a vPCI device is locked down by TSM Bind, CoCo VM should attest
and
Move the guest_request_type to IOMMUFD uAPI header file so that
userspace could use it for IOMMUFD uAPI -
IOMMU_VDEVICE_TSM_GUEST_REQUEST.
Add __user marker to all blob pointers to indicate the TSM drivers'
responsibility to read out/fill in user data.
Signed-off-by: Xu Yilun
---
include/linux/
Add handlers for setting up/removing trusted IOMMU configurations
against vdevice. IOMMUFD calls these handlers on TSM bind/unbind. Most
vendors extend the trusted IOMMU engine for private device assignment,
thus require extra IOMMU configuration for TSM bind. E.g. Intel TDX
Connect requires host t
Add new IOCTLs to do TSM based TDI bind/unbind. These IOCTLs are
expected to be called by userspace when CoCo VM issues TDI bind/unbind
command to VMM. Specifically for TDX Connect, these commands are some
secure Hypervisor call named GHCI (Guest-Hypervisor Communication
Interface).
The TSM TDI bi
Sync up the additional struct kvm * parameter.
Signed-off-by: Lu Baolu
Signed-off-by: Xu Yilun
---
drivers/iommu/iommufd/selftest.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/iommufd/selftest.c b/drivers/iommu/iommufd/selftest.c
index d070807757f2..90e6d1d3aa62 100644
---
Add new kAPIs against iommufd_device to support TSM Bind/Unbind
commands issued by CoCo-VM. The TSM bind means VMM does all
preparations for private device assignement, lock down the device by
transiting it to TDISP CONFIG_LOCKED or RUN state (when in RUN state,
TSM could still block any accessing
Track the kvm pointer and its refcount in viommu core. The kvm pointer
will be used later to support TSM Bind feature, which tells the secure
firmware the connection between a vPCI device and a CoCo VM.
There is existing need to reference kvm pointer in viommu [1], but in
that series kvm pointer i
From: Shameer Kolothum
No functional changes.
This will be used in a later patch to add support to use
KVM VMID in ARM SMMUv3 s2 stage configuration.
Signed-off-by: Shameer Kolothum
---
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-iommufd.c | 1 +
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
Export vfio dma-buf specific info by attaching vfio_dma_buf_data in
struct dma_buf::priv. Provide a helper vfio_dma_buf_get_data() for
importers to fetch these data. Exporters identify VFIO dma-buf by
successfully getting these data.
VFIO dma-buf supports disabling host access to these exported MM
Sync up the additional struct kvm * parameter.
Signed-off-by: Zhenzhong Duan
Signed-off-by: Xu Yilun
---
drivers/iommu/iommufd/selftest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/iommufd/selftest.c b/drivers/iommu/iommufd/selftest.c
index 18d9a216eb30..d
Add support for resolving page faults on private MMIO. This is part of
the effort to enable private assigned devices (known as TDI in TDISP
spec).
Private MMIOs are set to KVM as vfio_dmabuf typed memory slot, which is
another type of can-be-private memory slot just like the gmem slot.
Like gmem s
From: Shameer Kolothum
Add a struct kvm * to iommufd_device_bind() fn and associate it
with idev if bind is successful.
Signed-off-by: Shameer Kolothum
Reviewed-by: Jason Gunthorpe
---
This patch and next Shameer's patch are part of the series:
https://lore.kernel.org/all/20250319173202.7
Add support for resolving page faults on vfio_dmabuf backed MMIO. Now
only support setup KVM MMU mapping on shared roots, i.e. vfio_dmabuf
works for shared assigned devices.
Further work is to support private MMIO for private assigned
devices (known as TDI in TDISP spec).
Signed-off-by: Xu Yilun
From: Vivek Kasireddy
There is no need to share the main device pointer (struct vfio_device *)
with all the feature functions as they only need the core device
pointer. Therefore, extract the core device pointer once in the
caller (vfio_pci_core_ioctl_feature) and share it instead.
Signed-off-by
From: Vivek Kasireddy
>From Jason Gunthorpe:
"dma-buf has become a way to safely acquire a handle to non-struct page
memory that can still have lifetime controlled by the exporter. Notably
RDMA can now import dma-buf FDs and build them into MRs which allows for
PCI P2P operations. Extend this to
This is just to illustrate the idea that dma-buf provides a new buffer
sharing mode - importer mapping. Exporter provides the target memory
resource description, importer decides what's the best way to map the
memory based on the information of target memory and importing device.
The get_pfn() kAP
From: Vivek Kasireddy
These helpers are useful for managing additional references taken
on the device from other associated VFIO modules.
Original-patch-by: Jason Gunthorpe
Signed-off-by: Vivek Kasireddy
---
drivers/vfio/vfio_main.c | 2 ++
include/linux/vfio.h | 2 ++
2 files changed, 4
This series is the generic host side (KVM/VFIO/IOMMUFD) support for the
whole life cycle of private device assignment. It follows the
previously discussed flow chart [1], aim to better illustrate the
overall flow of private device assignment, find out and narrow down the
gaps of different vendors,
On Mon, 2025-05-26 at 13:43 +0200, Maarten Lankhorst wrote:
> Hey,
>
> Seems to be just some register definitions.
>
> Acked-by: Maarten Lankhorst
Thank you Maarten and Ankit for checking my patches. These are now
pushed to drm-intel-next.
BR,
Jouni Högander
>
> Best regards,
> ~Maarten
>
i915_pmu.c may fail to build with GCOV and AutoFDO enabled.
../drivers/gpu/drm/i915/i915_pmu.c:116:3: error: call to
'__compiletime_assert_487' declared with 'error' attribute: BUILD_BUG_ON
failed: bit > BITS_PER_TYPE(typeof_member(struct i915_pmu, enable)) - 1
116 | BUILD_BUG_
On Wed, May 28, 2025 at 10:55:03PM -0600, Upadhyay, Tejas wrote:
>
>
> > -Original Message-
> > From: Intel-xe On Behalf Of Lucas
> > De Marchi
> > Sent: 29 May 2025 03:12
> > To: intel...@lists.freedesktop.org
> > Cc: Brost, Matthew ; dri-
> > de...@lists.freedesktop.org; De Marchi, Luc
> -Original Message-
> From: Intel-xe On Behalf Of Lucas
> De Marchi
> Sent: 29 May 2025 03:12
> To: intel...@lists.freedesktop.org
> Cc: Brost, Matthew ; dri-
> de...@lists.freedesktop.org; De Marchi, Lucas ;
> Christian König ; Pierre-Eric Pelloux-Prayer
> ; Philipp Stanner
>
> Subjec
Hi Dmitry,
On 2025/5/29 0:09, Dmitry Baryshkov wrote:
@@ -595,16 +546,41 @@ static bool cdn_dp_check_link_status(struct cdn_dp_device
*dp)
static void cdn_dp_audio_handle_plugged_change(struct cdn_dp_device *dp,
bool plugged)
{
-if (dp->cod
Hi Alice,
On Thu May 29, 2025 at 4:56 AM JST, Alice Ryhl wrote:
> On Wed, May 21, 2025 at 8:45 AM Alexandre Courbot wrote:
>>
>> Introduce the `num` module, featuring the `NumExt` extension trait
>> that expands unsigned integers with useful operations for the kernel.
>>
>> These are to be used b
On Tue, May 27, 2025 at 03:17:43AM -0400, Abdulrasaq Lawani wrote:
> revert promotion of overview diagram title to that
> of previous commit in introduction.rst
>
The patch description doesn't really describe the diff below, which is
to add overview diagram instead. Maybe you can replace that wit
On Thu May 29, 2025 at 5:17 AM JST, Benno Lossin wrote:
> On Wed May 21, 2025 at 8:44 AM CEST, Alexandre Courbot wrote:
>> Introduce the `num` module, featuring the `NumExt` extension trait
>> that expands unsigned integers with useful operations for the kernel.
>>
>> These are to be used by the no
Luca, while you are sending a new revision, the patch subject says dmr
instead of drm. Kindly make that change.
Thanks,
Anusha
On Mon, May 26, 2025 at 7:51 AM Luca Ceresoli
wrote:
> Hi Maxime,
>
> On Thu, 22 May 2025 17:43:37 +0200
> Maxime Ripard wrote:
>
> > On Fri, May 16, 2025 at 06:48:38
On Fri, May 16, 2025 at 12:48 PM Luca Ceresoli
wrote:
> Use the new DRM bridge allocation API, which is the only supported now, for
> the kunit tests.
>
> This change is more massive than for the typical DRM bridge driver because
> struct drm_bridge_init_priv currently embeds a struct drm_bridge,
On Thu, May 29, 2025 at 07:53:55AM +1000, Dave Airlie wrote:
> On Wed, 28 May 2025 at 17:20, Christian König
> wrote:
> >
> > Hi guys,
> >
> > On 5/27/25 01:49, Dave Chinner wrote:
> > > I disagree - specifically ordered memcg traversal is not something
> > > that the list_lru implementation is c
On Mon, May 26, 2025 at 01:27:52PM +, Alessandro Carminati wrote:
> KUnit support is not consistently present across distributions, some
> include it in their stock kernels, while others do not.
> While both KUNIT and KUNIT_SUPPRESS_BACKTRACE can be considered debug
> features, the fact that so
On Mon, May 26, 2025 at 01:27:51PM +, Alessandro Carminati wrote:
> Some unit tests intentionally trigger warning backtraces by passing bad
> parameters to kernel API functions. Such unit tests typically check the
> return value from such calls, not the existence of the warning backtrace.
>
>
On Wed, 28 May 2025 at 17:20, Christian König wrote:
>
> Hi guys,
>
> On 5/27/25 01:49, Dave Chinner wrote:
> > I disagree - specifically ordered memcg traversal is not something
> > that the list_lru implementation is currently doing, nor should it
> > be doing.
>
> I realized over night that I d
On Wed, May 28, 2025 at 02:42:22PM -0700, Lucas De Marchi wrote:
> xef is only valid if it's a job from userspace. For in-kernel jobs it
> causes a NPD like below:
>
> <4> [] RIP: 0010:xe_sched_job_create+0xbd/0x390 [xe]
> ...
> <4> [] Call Trace:
> <4> []
>
On Wed, 28 May 2025 10:34:32 -0400 Jeff Layton wrote:
> Changes in v10:
> - drop the i915 symlink patch
> - Link to v9:
> https://lore.kernel.org/r/20250509-reftrack-dbgfs-v9-0-8ab888a45...@kernel.org
Hm, I reported the refracker warnings at boot on v9 :
ref_tracker: ref_tracker: unable to cre
xef is only valid if it's a job from userspace. For in-kernel jobs it
causes a NPD like below:
<4> [] RIP: 0010:xe_sched_job_create+0xbd/0x390 [xe]
...
<4> [] Call Trace:
<4> []
<4> [] __xe_bb_create_job+0xa2/0x240 [xe]
<4> [] ? find_held_lock+0
Hi,
Le 28/05/2025 à 21:07, Lucas De Marchi a écrit :
On Mon, May 26, 2025 at 02:54:44PM +0200, Pierre-Eric Pelloux-Prayer wrote:
drivers/gpu/drm/xe/xe_sched_job.c | 3 ++-
diff --git a/drivers/gpu/drm/xe/xe_sched_job.c
b/drivers/gpu/drm/xe/xe_sched_job.c
index f0a6ce610948..5921
On Wed, May 28, 2025 at 05:42:30PM +0200, Bram Vlerick wrote:
> Add devicetree parameter to enable or disable the invert feature of the
> ili9341 display
Can't/shouldn't this be done by userspace application? Why would someone
want to invert the color by default.
Also, this driver is built on top
On Wed May 21, 2025 at 8:44 AM CEST, Alexandre Courbot wrote:
> Introduce the `num` module, featuring the `NumExt` extension trait
> that expands unsigned integers with useful operations for the kernel.
>
> These are to be used by the nova-core driver, but they are so ubiquitous
> that other driver
patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Simona-Vetter/drm-gem-Fix-race-in-drm_gem_handle_create_tail/20250528-171524
base: next-20250527
patch link:
On Wed, 2025-05-28 at 18:34 +, Juston Li wrote:
> On Thu, 2025-05-22 at 16:14 +0100, Tvrtko Ursulin wrote:
> >
> > On 22/05/2025 15:50, Lucas De Marchi wrote:
> > > + dri-devel
> > >
> > > On Wed, May 21, 2025 at 10:42:35PM +, Juston Li wrote:
> > > > Add tracepoints behind CONFIG_DRM_XE_
On Wed, May 21, 2025 at 8:45 AM Alexandre Courbot wrote:
>
> Introduce the `num` module, featuring the `NumExt` extension trait
> that expands unsigned integers with useful operations for the kernel.
>
> These are to be used by the nova-core driver, but they are so ubiquitous
> that other drivers
On Wed, May 28, 2025 at 05:42:30PM +0200, Bram Vlerick wrote:
> Add devicetree parameter to enable or disable the invert feature of the
> ili9341 display
>
This commit message is so unclear. The parameter doesn't let you
--and this is a direct quote. LOL-- "disable the invert feature". It
woul
On Mon, May 26, 2025 at 02:54:44PM +0200, Pierre-Eric Pelloux-Prayer wrote:
drivers/gpu/drm/xe/xe_sched_job.c| 3 ++-
diff --git a/drivers/gpu/drm/xe/xe_sched_job.c
b/drivers/gpu/drm/xe/xe_sched_job.c
index f0a6ce610948..5921293b25db 100644
--- a/drivers/gpu/drm/xe/xe_sched_job.c
On Thu, 2025-05-22 at 16:14 +0100, Tvrtko Ursulin wrote:
>
> On 22/05/2025 15:50, Lucas De Marchi wrote:
> > + dri-devel
> >
> > On Wed, May 21, 2025 at 10:42:35PM +, Juston Li wrote:
> > > Add tracepoints behind CONFIG_DRM_XE_GPU_MEM_TRACEPOINTS for
> > > tracking
> > > global and per-proces
On Mon, May 26, 2025 at 05:28:28PM +0800, Jun Nie wrote:
> Currently, SSPPs are assigned to a maximum of two pipes. However,
> quad-pipe usage scenarios require four pipes and involve configuring
> two stages. In quad-pipe case, the first two pipes share a set of
> mixer configurations and enable m
There is a work-in-progress supplement patch. Let's wait and see whether
it fixes the regressions without reverting 46e68dd5066c.
On 5/27/25 11:06, Alex Hung wrote:
This reverts commit 46e68dd5066c9831e9695c1756db017bb9c3762c since it
breaks color enhancement in another OS, indicating these two
On Tue, May 27, 2025 at 06:29:49PM +0800, Yongxing Mou wrote:
>
>
> On 2024/12/6 18:12, Dmitry Baryshkov wrote:
> > On Thu, Dec 05, 2024 at 08:32:02PM -0800, Abhinav Kumar wrote:
> > > Add a new file dp_mst_drm to manage the DP MST bridge operations
> > > similar to the dp_drm file which manages
On 5/28/25 08:42, Jacek Lawrynowicz wrote:
From: Karol Wachowski
Trigger full device recovery when the driver fails to restore device state
via engine reset and resume operations. This is necessary because, even if
submissions from a faulty context are blocked, the NPU may still process
previ
On 5/28/25 08:43, Jacek Lawrynowicz wrote:
This fixes a potential race conditions in:
- ivpu_bo_unbind_locked() where we modified the shmem->sgt without
holding the dma_resv_lock().
- ivpu_bo_print_info() where we read the shmem->pages without
holding the dma_resv_lock().
Using dma
Hi Geert,
On Wed, May 28, 2025 at 1:32 PM Geert Uytterhoeven wrote:
>
> Hi Prabhakar,
>
> On Wed, 28 May 2025 at 11:48, Lad, Prabhakar
> wrote:
> > On Fri, May 23, 2025 at 4:19 PM Geert Uytterhoeven
> > wrote:
> > > On Mon, 12 May 2025 at 20:43, Prabhakar
> > > wrote:
> > > > From: Lad Prab
On Wed, 28 May 2025 at 19:50, Rob Clark wrote:
>
> On Tue, May 27, 2025 at 11:18 AM Dmitry Baryshkov
> wrote:
> >
> > On Tue, May 27, 2025 at 12:55:06PM +0200, Konrad Dybcio wrote:
> > > On 5/26/25 5:28 PM, Rob Clark wrote:
> > > > On Mon, May 26, 2025 at 1:36 AM Dmitry Baryshkov
> > > > wrote:
On 5/28/25 10:12, Jacek Lawrynowicz wrote:
Don't WARN if imported buffers are in use in ivpu_gem_bo_free() as they
can be indeed used in the original context/driver.
Fixes: 647371a6609d ("accel/ivpu: Add GEM buffer object management")
Cc: sta...@vger.kernel.org # v6.3
Signed-off-by: Jacek Lawr
Don't WARN if imported buffers are in use in ivpu_gem_bo_free() as they
can be indeed used in the original context/driver.
Fixes: 647371a6609d ("accel/ivpu: Add GEM buffer object management")
Cc: sta...@vger.kernel.org # v6.3
Signed-off-by: Jacek Lawrynowicz
---
v2: Use drm_gem_is_imported() to c
The pull request you sent on Wed, 28 May 2025 13:51:25 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2025-05-28
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b08494a8f7416e5f09907318c5460ad6f6e2a548
Thank you!
--
Deet-doot-dot, I am a bot.
ht
On Mon, 26 May 2025 at 08:16, Boris Brezillon
wrote:
> On Sat, 24 May 2025 16:03:37 +0100
> Daniel Stone wrote:
> > Unfortunately I have to revoke my T-b as we're seeing a pile of
> > failures in a CI stress test with this, e.g.
> > https://gitlab.freedesktop.org/daniels/mesa/-/jobs/77004047
>
>
Hi,
On 5/28/2025 6:33 PM, Lizhi Hou wrote:
> On 5/28/25 08:42, Jacek Lawrynowicz wrote:
>> Don't WARN if imported buffers are in use in ivpu_gem_bo_free() as they
>> can be indeed used in the original context/driver.
>>
>> Fixes: 647371a6609d ("accel/ivpu: Add GEM buffer object management")
>> Cc:
On 5/28/25 6:50 PM, Rob Clark wrote:
> On Tue, May 27, 2025 at 11:18 AM Dmitry Baryshkov
> wrote:
>>
>> On Tue, May 27, 2025 at 12:55:06PM +0200, Konrad Dybcio wrote:
>>> On 5/26/25 5:28 PM, Rob Clark wrote:
On Mon, May 26, 2025 at 1:36 AM Dmitry Baryshkov
wrote:
>
> On Sun, May
Hi Sean,
mið., 28. maí 2025 kl. 16:24 skrifaði Sean Summers :
>
> Hi Andri,
>
> I've made this patch, but I'm unable to configure the video pipeline for YCC
> 420. I'm using libdrm's modetest to set the output format / colorspace and
> pass a test pattern through. Modetest can see the new "force
On Tue, 27 May 2025 at 20:51, Dave Airlie wrote:
>
> I've put a trial merge result at
> https://github.com/airlied/linux/tree/drm-next-6.16-rc1-merged
I have trivial differences due to picking different line ordering for
some things, but your merge also left in a wrong (but ultimately
harmless) d
On 5/26/25 16:25, Thomas Zimmermann wrote:
> Pin and vmap are two distict operations. Do not mix them.
>
> The helper drm_client_buffer_vmap() maps the pages for fbdev-dma
> and fbdev-shmem. In both cases, the vmap operation ensures that
> the pages are available until the vunmap happens. And as t
On Tue, May 27, 2025 at 11:18 AM Dmitry Baryshkov
wrote:
>
> On Tue, May 27, 2025 at 12:55:06PM +0200, Konrad Dybcio wrote:
> > On 5/26/25 5:28 PM, Rob Clark wrote:
> > > On Mon, May 26, 2025 at 1:36 AM Dmitry Baryshkov
> > > wrote:
> > >>
> > >> On Sun, May 25, 2025 at 09:43:36PM +0200, Aleksand
On 5/28/25 08:42, Jacek Lawrynowicz wrote:
Don't WARN if imported buffers are in use in ivpu_gem_bo_free() as they
can be indeed used in the original context/driver.
Fixes: 647371a6609d ("accel/ivpu: Add GEM buffer object management")
Cc: # v6.3
Signed-off-by: Jacek Lawrynowicz
---
drivers
Whoops, wasn't subscribed to the email list. Resending. Sorry about the spam
Hi Andri,
I've made this patch, but I'm unable to configure the video pipeline for YCC
420. I'm using libdrm's modetest to set the output format / colorspace and pass
a test pattern through. Modetest can see the new "f
Hi Andri,
I've made this patch, but I'm unable to configure the video pipeline for YCC
420. I'm using libdrm's modetest to set the output format / colorspace and pass
a test pattern through. Modetest can see the new "force output format"
property, but it's being rejected and falls back to RGB.
On Mon, May 26, 2025 at 08:26:47PM +0800, Yongxing Mou wrote:
>
>
> On 2024/12/6 16:52, Dmitry Baryshkov wrote:
> > On Thu, Dec 05, 2024 at 08:31:36PM -0800, Abhinav Kumar wrote:
> > > Add a helper to check whether a dp_panel is mst capable.
> > >
> > > Signed-off-by: Abhinav Kumar
> > > ---
>
Hi Dave, Simona
Two documentation fixes this week.
Thanks,
Thomas
drm-xe-next-fixes-2025-05-28:
Driver Changes:
- Two documentation fixes (Rodrigo)
The following changes since commit 879ede53958f7bab79a8f77e0ca91f0f77da:
drm/xe: Default auto_link_downgrade status to false (2025-05-23 09:
On Mon, May 26, 2025 at 08:57:35PM +0800, Yongxing Mou wrote:
>
>
> On 2024/12/8 13:42, Dmitry Baryshkov wrote:
> > On Thu, Dec 05, 2024 at 08:31:48PM -0800, Abhinav Kumar wrote:
> > > Use the dp_panel's stream_id to adjust the offsets for stream 1
> > > which will be used for MST in the dp_catal
On Mon, May 26, 2025 at 08:47:22PM +0800, Yongxing Mou wrote:
>
>
> On 2024/12/6 17:14, Dmitry Baryshkov wrote:
> > On Thu, Dec 05, 2024 at 08:31:42PM -0800, Abhinav Kumar wrote:
> > > Split dp_ctrl_off() into stream and link parts so that for MST
> > > cases we can control the link and pixel par
On Wed, 28 May 2025 at 04:57, Chaoyi Chen wrote:
>
> Hi Dmitry,
>
> On 2025/5/28 4:25, Dmitry Baryshkov wrote:
> > On Tue, May 27, 2025 at 04:14:47PM +0800, Chaoyi Chen wrote:
> >> From: Chaoyi Chen
> >>
> >> Convert it to drm bridge driver, it will be convenient for us to
> >> migrate the connec
This fixes a potential race conditions in:
- ivpu_bo_unbind_locked() where we modified the shmem->sgt without
holding the dma_resv_lock().
- ivpu_bo_print_info() where we read the shmem->pages without
holding the dma_resv_lock().
Using dma_resv_lock() also protects against future syncronis
Don't WARN if imported buffers are in use in ivpu_gem_bo_free() as they
can be indeed used in the original context/driver.
Fixes: 647371a6609d ("accel/ivpu: Add GEM buffer object management")
Cc: # v6.3
Signed-off-by: Jacek Lawrynowicz
---
drivers/accel/ivpu/ivpu_gem.c | 3 ++-
1 file changed,
From: Karol Wachowski
Trigger full device recovery when the driver fails to restore device state
via engine reset and resume operations. This is necessary because, even if
submissions from a faulty context are blocked, the NPU may still process
previously submitted faulty jobs if the engine reset
Hi Dave, Sima,
this is the weekly PR for drm-misc-fixes. Besides DRM, the bugfix
for dummycon possibly affects fbcon and fbdev output as well.
Best regards
Thomas
drm-misc-fixes-2025-05-28:
Short summary of fixes pull:
drm-scheduler:
- signal scheduled fence when killing job
dummycon:
- trigge
On Wed, May 28, 2025 at 3:41 PM Rob Herring wrote:
>
> On Tue, May 20, 2025 at 5:27 AM Tomeu Vizoso wrote:
> >
> > Add the bindings for the Neural Processing Unit IP from Rockchip.
> >
> > v2:
> > - Adapt to new node structure (one node per core, each with its own
> > IOMMU)
> > - Several misc.
On Wed May 28, 2025 at 12:36 PM CEST, Alice Ryhl wrote:
> On Mon, May 26, 2025 at 06:29:46PM -0400, Tamir Duberstein wrote:
>> On Mon, May 26, 2025 at 11:04 AM Benno Lossin wrote:
>> >
>> > On Sat May 24, 2025 at 10:33 PM CEST, Tamir Duberstein wrote:
>> > > +macro_rules! c_str_avoid_literals {
>>
On 5/28/2025 3:13 AM, Simona Vetter wrote:
Handles are per-file, not global, so this makes no sense. Plus it's
set only after calling drm_gem_handle_create(), and drivers are not
allowed to further intialize a bo after that function has published it
already.
intialize -> initialize
It is also
1 - 100 of 226 matches
Mail list logo
