Hi,
On 2/23/23 19:50, Alex Deucher wrote:
On Thu, Feb 23, 2023 at 10:03 AM Thomas Hellström
wrote:
Hi, Daniel,
On 2/16/23 21:18, Daniel Vetter wrote:
On Thu, Feb 16, 2023 at 05:27:28PM +0100, Thomas Hellström wrote:
A slightly unusual cover letter for a single patch.
The page table walker
Hi, Oded.
On 2/26/23 19:56, Oded Gabbay wrote:
On Thu, Feb 23, 2023 at 8:50 PM Alex Deucher wrote:
On Thu, Feb 23, 2023 at 10:03 AM Thomas Hellström
wrote:
Hi, Daniel,
On 2/16/23 21:18, Daniel Vetter wrote:
On Thu, Feb 16, 2023 at 05:27:28PM +0100, Thomas Hellström wrote:
A slightly unusu
Daniel, Dave
Ack to merge this to drm through drm-misc-next?
/Thomas
On 2/24/23 10:51, Thomas Hellström wrote:
This series (or at least the suballocator helper) is a prerequisite
for the new Xe driver.
There was an unresolved issue when the series was last up for review,
and that was the per
Hi, Maarten,
On 2/27/23 09:55, Maarten Lankhorst wrote:
Hey,
I can push this to drm-misc-next, I don't think a drm maintainer ack
is needed, as long as we have the acks from the amd folk for merging
through drm-misc-next.
OK, sound good, we have that ack so please go ahead!
/Thomas
~Ma
Display to communicate display pipe count/CDCLK/voltage configuration
to Pcode for more accurate power accounting for gen >= 12.
Existing sequence is only sending the voltage value to the Pcode.
Adding new sequence with current cdclk associate with voltage value masking.
Adding pcode request when a
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:44PM +0100, Andrzej Hajda wrote:
> __xchg will be used for non-atomic xchg macro.
>
> Signed-off-by: Andrzej Hajda
> Reviewed-by: Arnd Bergmann
> Acked-by: Geert Uytterhoeven [m68k]
> Acked-by: Palmer Dabbelt [riscv]
Reviewed-by: Andi Shyti
Thanks,
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:45PM +0100, Andrzej Hajda wrote:
> The pattern of setting variable with new value and returning old
> one is very common in kernel. Usually atomicity of the operation
> is not required, so xchg seems to be suboptimal and confusing in
> such cases.
>
> Sig
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:46PM +0100, Andrzej Hajda wrote:
> In all architectures, except x86, arch_uretprobe_hijack_return_addr
> is just __xchg.
>
> Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
Thanks,
Andi
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:47PM +0100, Andrzej Hajda wrote:
> llist_del_all uses xchg, let's use __xchg here.
>
> Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
Thanks,
Andi
On Tue, 14 Feb 2023, Arun R Murthy wrote:
> Enable SDP error detection configuration, this will set CRC16 in
> 128b/132b link layer.
> For Display version 13 a hardware bit31 in register VIDEO_DIP_CTL is
> added to enable/disable SDP CRC applicable for DP2.0 only, but the
> default value of this b
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:49PM +0100, Andrzej Hajda wrote:
> Recently introduced helper simplifies the code.
>
> Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
Thanks,
Andi
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:50PM +0100, Andrzej Hajda wrote:
> Prefer core helper if available.
>
> Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
Thanks,
Andi
Hi Andrzej,
On Wed, Jan 18, 2023 at 04:44:48PM +0100, Andrzej Hajda wrote:
> Recently introduced helper simplifies the code.
>
> Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
Thanks,
Andi
== Series Details ==
Series: drm/i915/display: Communicate display power demands to pcode more
accurately
URL : https://patchwork.freedesktop.org/series/114401/
State : failure
== Summary ==
Error: make failed
CALLscripts/checksyscalls.sh
DESCEND objtool
CC [M] drivers/gpu/drm/i915
Hi Dave & Daniel -
Some more fixes for v6.3-rc1.
drm-intel-next-fixes-2023-02-27:
drm/i915 fixes for v6.3-rc1:
- Don't use stolen memory or BAR mappings for ring buffers with LLC
- Add inverted backlight quirk for HP 14-r206nv
- Fix GSI offset for MCR lookups
- GVT fixes (memleak, debugfs attri
Add a suballocator test to get some test coverage for the new drm
suballocator, and perform some basic timing (elapsed time).
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/Kconfig | 1 +
drivers/gpu/drm/tests/Makefile| 3 +-
drivers/gpu/drm/tests/drm_subal
This is preparation for adding vfio device cdev support. vfio device
cdev requires:
1) a per device file memory to store the kvm pointer set by KVM. It will
be propagated to vfio_device:kvm after the device cdev file is bound
to an iommufd
2) a mechanism to block device access through device
Existing VFIO provides group-centric user APIs for userspace. Userspace
opens the /dev/vfio/$group_id first before getting device fd and hence
getting access to device. This is not the desired model for iommufd. Per
the conclusion of community discussion[1], iommufd provides device-centric
kAPIs an
This avoids passing too much parameters in multiple functions.
Signed-off-by: Yi Liu
Reviewed-by: Kevin Tian
---
drivers/vfio/group.c | 19 +--
drivers/vfio/vfio.h | 8
drivers/vfio/vfio_main.c | 25 +++--
3 files changed, 32 insertions(+),
Allow the vfio_device file to be in a state where the device FD is
opened but the device cannot be used by userspace (i.e. its .open_device()
hasn't been called). This inbetween state is not used when the device
FD is spawned from the group FD, however when we create the device FD
directly by openi
This prepares for making the below kAPIs to accept both group file
and device file instead of only vfio group file.
bool vfio_file_enforced_coherent(struct file *file);
void vfio_file_set_kvm(struct file *file, struct kvm *kvm);
Besides the above change, vfio_file_is_valid() is added to check
This makes the vfio file kAPIs to accepte vfio device files, also a
preparation for vfio device cdev support.
For the kvm set with vfio device file, kvm pointer is stored in struct
vfio_device_file, and use kvm_ref_lock to protect kvm set and kvm
pointer usage within VFIO. This kvm pointer will be
to indicate kernel to use the device's bound iommufd_ctx for the device
ownership check. Kernel should loop all the opened devices in the dev_set,
and check if they are bound to the same iommufd_ctx. For the devices that
has not been opened yet but affected, they can be reset by the current
users a
this prepares for adding DETACH ioctl for emulated VFIO devices.
Signed-off-by: Yi Liu
Reviewed-by: Kevin Tian
---
drivers/gpu/drm/i915/gvt/kvmgt.c | 1 +
drivers/s390/cio/vfio_ccw_ops.c | 1 +
drivers/s390/crypto/vfio_ap_ops.c | 1 +
drivers/vfio/iommufd.c| 18 +++
For the device fd opened from cdev, userspace needs to bind it to an
iommufd and attach it to IOAS managed by iommufd. With such operations,
userspace can set up a secure DMA context and hence access device.
This changes the existing vfio_iommufd_bind() to accept a pt_id pointer
as an optional inp
This defines KVM_DEV_VFIO_FILE* and make alias with KVM_DEV_VFIO_GROUP*.
Old userspace uses KVM_DEV_VFIO_GROUP* works as well.
Signed-off-by: Yi Liu
---
Documentation/virt/kvm/devices/vfio.rst | 52 +
include/uapi/linux/kvm.h| 16 ++--
virt/kvm/vfio.c
This adds ioctl for userspace to attach device cdev fd to and detach
from IOAS/hw_pagetable managed by iommufd.
VFIO_DEVICE_ATTACH_IOMMUFD_PT: attach vfio device to IOAS, hw_pagetable
managed by iommufd. Attach can be
undo b
this suits more on what the code does.
Signed-off-by: Yi Liu
Reviewed-by: Kevin Tian
---
drivers/vfio/pci/vfio_pci_core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
index a6492a25ff6a..1bf54beeaef2
This allows user to directly open a vfio device w/o using the legacy
container/group interface, as a prerequisite for supporting new iommu
features like nested translation.
The device fd opened in this manner doesn't have the capability to access
the device as the fops open() doesn't open the devi
Meanwhile, rename related helpers. No functional change is intended.
Signed-off-by: Yi Liu
Reviewed-by: Kevin Tian
Reviewed-by: Eric Auger
---
virt/kvm/vfio.c | 115
1 file changed, 58 insertions(+), 57 deletions(-)
diff --git a/virt/kvm/vfio.c
this prepares for adding DETACH ioctl for physical VFIO devices.
Signed-off-by: Yi Liu
Reviewed-by: Kevin Tian
---
Documentation/driver-api/vfio.rst | 8 +---
drivers/vfio/fsl-mc/vfio_fsl_mc.c | 1 +
drivers/vfio/iommufd.c| 20 ++
This adds ioctl for userspace to bind device cdev fd to iommufd.
VFIO_DEVICE_BIND_IOMMUFD: bind device to an iommufd, hence gain DMA
control provided by the iommufd. open_device
op is called after bind_iommufd op.
for counting the devices that are opened via the cdev path. This count
is increased and decreased by the cdev path. The group path checks it
to achieve exclusion with the cdev path. With this, only one path (group
path or cdev path) will claim DMA ownership. This avoids scenarios in
which devices w
group code is not needed for vfio device cdev, so with vfio device cdev
introduced, the group infrastructures can be compiled out if only cdev
is needed.
Signed-off-by: Yi Liu
---
drivers/vfio/Kconfig | 14 +
drivers/vfio/Makefile | 2 +-
drivers/vfio/vfio.h | 72
VFIO group has historically allowed multi-open of the device FD. This
was made secure because the "open" was executed via an ioctl to the
group FD which is itself only single open.
However, no known use of multiple device FDs today. It is kind of a
strange thing to do because new device FDs can na
This gives notes for userspace applications on device cdev usage.
Signed-off-by: Yi Liu
---
Documentation/driver-api/vfio.rst | 125 ++
1 file changed, 125 insertions(+)
diff --git a/Documentation/driver-api/vfio.rst
b/Documentation/driver-api/vfio.rst
index 4452742
On 24/02/2023 17:40, Jonathan Cavitt wrote:
MTL currently uses gen8_ppgtt_insert_huge when managing huge pages. This is
because
MTL reports as not supporting 64K pages, or more accurately, the system that
reports
whether a platform has 64K pages reports false for MTL. This is only half
corre
According to spec, we should check if output_bpp * pixel_rate is less
than DDI clock * 72, if UHBR is used.
v2: - s/pipe_config/crtc_state/ (Jani Nikula)
- Merged previous patch into that one, to remove empty function(Jani Nikula)
HSDES: 1406899791
BSPEC: 49259
Signed-off-by: Stanislav Lisov
On Fri, 24 Feb 2023, Zhanjun Dong wrote:
> Add err code check for enable_communication on resume path, set wedged if
> failed.
I can see that this is *what* the code does, but the commit message
should answer the question *why*.
>
> Signed-off-by: Zhanjun Dong
> ---
> drivers/gpu/drm/i915/gt/
== Series Details ==
Series: Add vfio_device cdev for iommufd support (rev5)
URL : https://patchwork.freedesktop.org/series/113696/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/113696/revisions/5/mbox/ not
applied
Applying: vfio: Allocate per de
On Fri, 24 Feb 2023, Andrzej Hajda wrote:
> From: Chris Wilson
>
> Extract the callstack tracking of intel_runtime_pm.c into its own
> utility so that that we can reuse it for other online debugging of
> scoped wakerefs.
>
> Signed-off-by: Chris Wilson
> Signed-off-by: Andrzej Hajda
> ---
> dr
Hi Stanislav,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Stanislav-Lisovskiy/drm-i915-display-Communicate-display-power-demands-to-pcode-more-accurately/20230227-175404
base: git
Hi Stanislav,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Stanislav-Lisovskiy/drm-i915-display-Communicate-display-power-demands-to-pcode-more-accurately/20230227-175404
base: git
On Thu, 23 Feb 2023, Ville Syrjälä wrote:
> On Thu, Feb 23, 2023 at 05:01:11PM +, Shankar, Uma wrote:
>>
>>
>> > -Original Message-
>> > From: Ville Syrjälä
>> > Sent: Thursday, February 23, 2023 8:37 PM
>> > To: Shankar, Uma
>> > Cc: intel-gfx@lists.freedesktop.org
>> > Subject: R
On Mon, 27 Feb 2023 at 01:49, Abhinav Kumar wrote:
>
>
>
> On 2/26/2023 5:09 AM, Dmitry Baryshkov wrote:
> > On 26/02/2023 02:47, Abhinav Kumar wrote:
> >> Hi Dmitry
> >>
> >> On 2/25/2023 7:23 AM, Dmitry Baryshkov wrote:
> >>> On 25/02/2023 02:36, Abhinav Kumar wrote:
>
>
> On 2/24
On Fri, Feb 17, 2023 at 10:51 PM Daniel Vetter wrote:
>
> Hi all,
>
> [I thought I've sent this out earlier this week, but alas got stuck, kinda
> bad timing now since I'm out next week but oh well]
>
> So xe is a quite substantial thing, and I think we need a clear plan how to
> land
> this or i
On Sun, 26 Feb 2023, Abhinav Kumar wrote:
> On 2/26/2023 5:09 AM, Dmitry Baryshkov wrote:
>> On 26/02/2023 02:47, Abhinav Kumar wrote:
>>> Hi Dmitry
>>>
>>> On 2/25/2023 7:23 AM, Dmitry Baryshkov wrote:
On 25/02/2023 02:36, Abhinav Kumar wrote:
>
>
> On 2/24/2023 3:53 PM, Dmitry B
Hi Stanislav,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Stanislav-Lisovskiy/drm-i915-display-Communicate-display-power-demands-to-pcode-more-accurately/20230227-175404
base: git
> -Original Message-
> From: Jani Nikula
> Sent: Monday, February 27, 2023 6:07 PM
> To: Ville Syrjälä ; Shankar, Uma
>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix audio ELD handling for DP
> MST
>
> On Thu, 23 Feb 2023, Ville Syrjälä wr
Am 27.02.23 um 10:00 schrieb Thomas Hellström:
Hi, Maarten,
On 2/27/23 09:55, Maarten Lankhorst wrote:
Hey,
I can push this to drm-misc-next, I don't think a drm maintainer ack
is needed, as long as we have the acks from the amd folk for merging
through drm-misc-next.
OK, sound good, we h
== Series Details ==
Series: drm/tests: Suballocator test
URL : https://patchwork.freedesktop.org/series/114410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779 -> Patchwork_114410v1
Summary
---
**SUCCESS**
No
== Series Details ==
Series: drm/i915: Implement UHBR bandwidth check (rev2)
URL : https://patchwork.freedesktop.org/series/112806/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779 -> Patchwork_112806v2
Summary
---
Display to communicate display pipe count/CDCLK/voltage configuration
to Pcode for more accurate power accounting for gen >= 12.
Existing sequence is only sending the voltage value to the Pcode.
Adding new sequence with current cdclk associate with voltage value masking.
Adding pcode request when a
== Series Details ==
Series: drm/i915/display: Communicate display power demands to pcode more
accurately (rev2)
URL : https://patchwork.freedesktop.org/series/114401/
State : warning
== Summary ==
Error: dim checkpatch failed
5390f300e150 drm/i915/display: Communicate display power demands t
On Thu, Feb 23, 2023 at 10:24:19PM +0100, Andrzej Hajda wrote:
> On 22.02.2023 18:04, Peter Zijlstra wrote:
> > On Wed, Jan 18, 2023 at 04:35:22PM +0100, Andrzej Hajda wrote:
> >
> > > Andrzej Hajda (7):
> > >arch: rename all internal names __xchg to __arch_xchg
> > >linux/include: add non
== Series Details ==
Series: drm/i915/display: Communicate display power demands to pcode more
accurately (rev2)
URL : https://patchwork.freedesktop.org/series/114401/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779 -> Patchwork_114401v2
==
Hi Thomas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Hellstr-m/drm-tests-Suballocator-test/20230227-184044
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link
From: Ville Syrjälä
Remove the bogus csync check and replace it with something that:
- triggers for all forms of csync, not just the basic analog variant
- actually populates the mode csync flags so that drivers can
decide what to do with the mode
Originally the code tried to outright reject c
== Series Details ==
Series: drm/tests: Suballocator test
URL : https://patchwork.freedesktop.org/series/114410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779_full -> Patchwork_114410v1_full
Summary
---
**SUCCE
Hi Thomas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Hellstr-m/drm-tests-Suballocator-test/20230227-184044
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link
On Mon, 27 Feb 2023, Dmitry Osipenko wrote:
> On 2/21/23 19:29, Dmitry Osipenko wrote:
>> On 2/20/23 18:44, Dmitry Osipenko wrote:
>>> On 2/16/23 23:44, Jani Nikula wrote:
Mostly this is prep work and plumbing for easier use of displayid
structure version and primary use case for parsing
On Mon, Feb 27, 2023 at 8:04 AM Christian König
wrote:
>
> Am 27.02.23 um 10:00 schrieb Thomas Hellström:
> > Hi, Maarten,
> >
> > On 2/27/23 09:55, Maarten Lankhorst wrote:
> >> Hey,
> >>
> >> I can push this to drm-misc-next, I don't think a drm maintainer ack
> >> is needed, as long as we have
-Original Message-
From: Auld, Matthew
Sent: Monday, February 27, 2023 3:20 AM
To: Cavitt, Jonathan ;
intel-gfx@lists.freedesktop.org
Cc: Dutt, Sudeep ; thomas.hellst...@linux.intel.com;
maarten.lankho...@linux.intel.com; Vetter, Daniel ; De
Marchi, Lucas ; chris.p.wil...@linux.intel.c
On Mon, Feb 27, 2023 at 09:09:14AM +0100, Thomas Hellström wrote:
> Hi, Oded.
>
> On 2/26/23 19:56, Oded Gabbay wrote:
> > On Thu, Feb 23, 2023 at 8:50 PM Alex Deucher wrote:
> > > On Thu, Feb 23, 2023 at 10:03 AM Thomas Hellström
> > > wrote:
> > > > Hi, Daniel,
> > > >
> > > > On 2/16/23 21:1
On 27/02/2023 15:06, Cavitt, Jonathan wrote:
-Original Message-
From: Auld, Matthew
Sent: Monday, February 27, 2023 3:20 AM
To: Cavitt, Jonathan ;
intel-gfx@lists.freedesktop.org
Cc: Dutt, Sudeep ; thomas.hellst...@linux.intel.com;
maarten.lankho...@linux.intel.com; Vetter, Daniel ; De
== Series Details ==
Series: drm/i915: Implement UHBR bandwidth check (rev2)
URL : https://patchwork.freedesktop.org/series/112806/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779_full -> Patchwork_112806v2_full
Summary
Hi all,
As suggested by Rodrigo added CC: Tvrtko and Joonas, see below.
On 22.02.2023 21:48, Rodrigo Vivi wrote:
On Wed, Feb 22, 2023 at 01:05:16PM +0100, Andrzej Hajda wrote:
Hi all,
Gently ping on the patch. CI pollution is quite high:
$ grep 'PTE Read access' CI/drm-tip/CI_DRM_12768/*/dm
MTL currently uses gen8_ppgtt_insert_huge when managing huge pages. This is
because
MTL reports as not supporting 64K pages, or more accurately, the system that
reports
whether a platform has 64K pages reports false for MTL. This is only half
correct,
as the 64K page support reporting system o
Convert the igt_mock_ppgtt_huge_fill and igt_mock_ppgtt_64K mock selftests into
live selftests as their requirements have recently become platform-dependent.
Additionally, apply necessary platform dependency checks to these tests.
Signed-off-by: Jonathan Cavitt
---
.../gpu/drm/i915/gem/selftests
== Series Details ==
Series: drm/edid: Fix csync detailed mode parsing
URL : https://patchwork.freedesktop.org/series/114424/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12786 -> Patchwork_114424v1
Summary
---
**SU
== Series Details ==
Series: series starting with [v4,1/2] drm/i915: Use correct huge page manager
for MTL
URL : https://patchwork.freedesktop.org/series/114428/
State : warning
== Summary ==
Error: dim checkpatch failed
39e49179dfa7 drm/i915: Use correct huge page manager for MTL
-:6: WARNIN
== Series Details ==
Series: series starting with [v4,1/2] drm/i915: Use correct huge page manager
for MTL
URL : https://patchwork.freedesktop.org/series/114428/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12786 -> Patchwork_114428v1
On Tue, Feb 21, 2023 at 12:18:36PM -0800, Matt Roper wrote:
> The bspec was updated with a minor change to the 'DCC mode select'
> setting to be programmed during combo PHY initialization.
>
> v2:
> - Keep the opencoded rmw behavior instead of switching to
>intel_de_rmw(). We need to read fr
On Tue, Feb 21, 2023 at 11:26:58PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/gen12: Update combo PHY init sequence (rev2)
> URL : https://patchwork.freedesktop.org/series/114233/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_12768_full -> Pa
On 27/02/2023 16:21, Jonathan Cavitt wrote:
Convert the igt_mock_ppgtt_huge_fill and igt_mock_ppgtt_64K mock selftests into
live selftests as their requirements have recently become platform-dependent.
Additionally, apply necessary platform dependency checks to these tests.
Signed-off-by: Jonath
There's only one reference to the struct intel_dmc members dc_state,
target_dc_state, and allowed_dc_mask within intel_dmc.c, begging the
question why they are under struct intel_dmc to begin with.
Moreover, the only references to i915->display.dmc outside of
intel_dmc.c are to these members.
The
Convert the igt_mock_ppgtt_huge_fill and igt_mock_ppgtt_64K mock selftests into
live selftests as their requirements have recently become platform-dependent.
Additionally, apply necessary platform dependency checks to these tests.
v2: Reorder
Signed-off-by: Jonathan Cavitt
---
.../gpu/drm/i915/
MTL currently uses gen8_ppgtt_insert_huge when managing huge pages. This is
because
MTL reports as not supporting 64K pages, or more accurately, the system that
reports
whether a platform has 64K pages reports false for MTL. This is only half
correct,
as the 64K page support reporting system o
This will help in follow-up changes.
Cc: Imre Deak
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/intel_dmc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c
b/drivers/gpu/drm/i915/display/intel_dmc.c
index ab4fdedd4
Start preparing for dynamically allocated struct intel_dmc by adding
i915_to_dmc() and dmc->i915, and using them. Take the future NULL dmc
pointer into account already now, and add separate logging for
initialization in the DMC debugfs.
v2:
- Don't reduce debugfs output (Imre)
Cc: Imre Deak
Sign
sizeof(struct intel_dmc) > 1024 bytes, allocated on all platforms as
part of struct drm_i915_private, whether they have DMC or not.
Allocate struct intel_dmc dynamically, and hide all the dmc details
behind an opaque pointer in intel_dmc.c.
Care must be taken to take into account all cases: DMC n
On Fri, 17 Feb 2023, Imre Deak wrote:
> On Fri, Feb 17, 2023 at 12:04:14PM +0200, Jani Nikula wrote:
>> On Thu, 16 Feb 2023, Imre Deak wrote:
>> > On Thu, Feb 16, 2023 at 06:17:39PM +0200, Jani Nikula wrote:
>> >> sizeof(struct intel_dmc) > 1024 bytes, allocated on all platforms as
>> >> part of
On 2/27/2023 4:45 AM, Dmitry Baryshkov wrote:
On Mon, 27 Feb 2023 at 01:49, Abhinav Kumar wrote:
On 2/26/2023 5:09 AM, Dmitry Baryshkov wrote:
On 26/02/2023 02:47, Abhinav Kumar wrote:
Hi Dmitry
On 2/25/2023 7:23 AM, Dmitry Baryshkov wrote:
On 25/02/2023 02:36, Abhinav Kumar wrote:
== Series Details ==
Series: series starting with [v5,1/2] drm/i915: Migrate platform-dependent mock
hugepage selftests to live
URL : https://patchwork.freedesktop.org/series/114432/
State : warning
== Summary ==
Error: dim checkpatch failed
8e94821ec3ff drm/i915: Migrate platform-dependent m
== Series Details ==
Series: drm/i915/display: Communicate display power demands to pcode more
accurately (rev2)
URL : https://patchwork.freedesktop.org/series/114401/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12779_full -> Patchwork_114401v2_full
== Series Details ==
Series: series starting with [v5,1/2] drm/i915: Migrate platform-dependent mock
hugepage selftests to live
URL : https://patchwork.freedesktop.org/series/114432/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12787 -> Patchwork_114432v1
===
On Mon, Feb 27, 2023 at 03:11:25AM -0800, Yi Liu wrote:
> to indicate kernel to use the device's bound iommufd_ctx for the device
> ownership check. Kernel should loop all the opened devices in the dev_set,
> and check if they are bound to the same iommufd_ctx. For the devices that
> has not been o
On Mon, Feb 27, 2023 at 03:11:26AM -0800, Yi Liu wrote:
> For the device fd opened from cdev, userspace needs to bind it to an
> iommufd and attach it to IOAS managed by iommufd. With such operations,
> userspace can set up a secure DMA context and hence access device.
>
> This changes the existin
On Mon, Feb 27, 2023 at 03:11:33AM -0800, Yi Liu wrote:
> This adds ioctl for userspace to attach device cdev fd to and detach
> from IOAS/hw_pagetable managed by iommufd.
>
> VFIO_DEVICE_ATTACH_IOMMUFD_PT: attach vfio device to IOAS, hw_pagetable
> managed by
On Mon, Feb 27, 2023 at 03:11:27AM -0800, Yi Liu wrote:
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index c89a047a4cd8..d540cf683d93 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -594,6 +594,7 @@ static
On Mon, Feb 27, 2023 at 03:11:28AM -0800, Yi Liu wrote:
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> index bfaa9876499b..faf2516b0f06 100644
> --- a/drivers/vfio/iommufd.c
> +++ b/drivers/vfio/iommufd.c
> @@ -165,6 +165,12 @@ int vfio_iommufd_emulated_attach_ioas(struct vfio_dev
On Mon, Feb 27, 2023 at 03:11:17AM -0800, Yi Liu wrote:
> This is preparation for adding vfio device cdev support. vfio device
> cdev requires:
> 1) a per device file memory to store the kvm pointer set by KVM. It will
>be propagated to vfio_device:kvm after the device cdev file is bound
>t
On Mon, Feb 27, 2023 at 03:11:18AM -0800, Yi Liu wrote:
> This prepares for making the below kAPIs to accept both group file
> and device file instead of only vfio group file.
>
> bool vfio_file_enforced_coherent(struct file *file);
> void vfio_file_set_kvm(struct file *file, struct kvm *kvm);
On Mon, Feb 27, 2023 at 03:11:19AM -0800, Yi Liu wrote:
> This makes the vfio file kAPIs to accepte vfio device files, also a
> preparation for vfio device cdev support.
>
> For the kvm set with vfio device file, kvm pointer is stored in struct
> vfio_device_file, and use kvm_ref_lock to protect k
On Mon, Feb 27, 2023 at 03:11:20AM -0800, Yi Liu wrote:
> Meanwhile, rename related helpers. No functional change is intended.
>
> Signed-off-by: Yi Liu
> Reviewed-by: Kevin Tian
> Reviewed-by: Eric Auger
> ---
> virt/kvm/vfio.c | 115
> 1 file
On Mon, Feb 27, 2023 at 03:11:21AM -0800, Yi Liu wrote:
> This defines KVM_DEV_VFIO_FILE* and make alias with KVM_DEV_VFIO_GROUP*.
> Old userspace uses KVM_DEV_VFIO_GROUP* works as well.
>
> Signed-off-by: Yi Liu
> ---
> Documentation/virt/kvm/devices/vfio.rst | 52 +
> i
On Mon, Feb 27, 2023 at 03:11:22AM -0800, Yi Liu wrote:
> This avoids passing too much parameters in multiple functions.
>
> Signed-off-by: Yi Liu
> Reviewed-by: Kevin Tian
> ---
> drivers/vfio/group.c | 19 +--
> drivers/vfio/vfio.h | 8
> drivers/vfio/vfio_m
On Mon, Feb 27, 2023 at 03:11:23AM -0800, Yi Liu wrote:
> Allow the vfio_device file to be in a state where the device FD is
> opened but the device cannot be used by userspace (i.e. its .open_device()
> hasn't been called). This inbetween state is not used when the device
> FD is spawned from the
On Mon, Feb 27, 2023 at 03:11:24AM -0800, Yi Liu wrote:
> this suits more on what the code does.
>
> Signed-off-by: Yi Liu
> Reviewed-by: Kevin Tian
> ---
> drivers/vfio/pci/vfio_pci_core.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
Reviewed-by: Jason Gunthorpe
Jason
On Mon, Feb 27, 2023 at 03:11:30AM -0800, Yi Liu wrote:
> @@ -535,7 +542,8 @@ static int vfio_device_fops_release(struct inode *inode,
> struct file *filep)
> struct vfio_device_file *df = filep->private_data;
> struct vfio_device *device = df->device;
>
> - vfio_device_group_clo
1 - 100 of 167 matches
Mail list logo
