> From: Alex Williamson
> Sent: Tuesday, June 13, 2023 6:42 AM
>
> On Fri, 2 Jun 2023 05:16:50 -0700
> Yi Liu wrote:
>
> > This moves the noiommu device determination and noiommu taint out of
> > vfio_group_find_or_alloc(). noiommu device is determined in
> > __vfio_register_dev() and result
> From: Alex Williamson
> Sent: Tuesday, June 13, 2023 6:27 AM
>
> On Fri, 2 Jun 2023 05:16:47 -0700
> Yi Liu wrote:
>
> > This adds ioctl for userspace to bind device cdev fd to iommufd.
> >
> > VFIO_DEVICE_BIND_IOMMUFD: bind device to an iommufd, hence gain DMA
> >
> From: Alex Williamson
> Sent: Tuesday, June 13, 2023 5:52 AM
>
> On Fri, 2 Jun 2023 05:16:36 -0700
> 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).
== Series Details ==
Series: drm/i915/display/dp: On AUX xfer timeout restart freshly (rev3)
URL : https://patchwork.freedesktop.org/series/119055/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13264 -> Patchwork_119055v3
== Series Details ==
Series: drm/i915: GSC FW support for MTL (rev4)
URL : https://patchwork.freedesktop.org/series/117396/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13263_full -> Patchwork_117396v4_full
Summary
> From: Alex Williamson
> Sent: Tuesday, June 13, 2023 5:52 AM
>
> On Fri, 2 Jun 2023 05:16:35 -0700
> Yi Liu wrote:
>
> > This avoids passing too much parameters in multiple functions. Per the
> > input parameter change, rename the function to be vfio_df_open/close().
> >
> > Reviewed-by:
On AUX transfer timeout, as per DP spec need to retry for 3 times and
has to be restarted freshly.
v3: handle timeout and dont rely on register value on timeout (Imre)
Signed-off-by: Arun R Murthy
---
.../drm/i915/display/intel_display_types.h| 1 -
== Series Details ==
Series: PCI/VGA: Introduce is_boot_device function callback to
vga_client_register
URL : https://patchwork.freedesktop.org/series/119249/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13264 -> Patchwork_119249v1
== Series Details ==
Series: PCI/VGA: Introduce is_boot_device function callback to
vga_client_register
URL : https://patchwork.freedesktop.org/series/119249/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
From: Sui Jingfeng
[why]
The vga_is_firmware_default() defined in drivers/pci/vgaarb.c is
arch-dependent, it's a dummy on non-x86 architectures currently.
This made VGAARB lost an important condition for the arbitration.
It could still be wrong even if we remove the #ifdef and #endif guards.
From: Sui Jingfeng
[why]
The vga_is_firmware_default() defined in drivers/pci/vgaarb.c is
arch-dependent, it's a dummy on non-x86 architectures currently.
This made VGAARB lost an important condition for the arbitration.
It could still be wrong even if we remove the #ifdef and #endif guards.
From: Sui Jingfeng
The vga_is_firmware_default() function is arch-dependent, it's probably
wrong if we simply remove the arch guard. As the VRAM BAR which contains
firmware framebuffer may move, while the lfb_base and lfb_size members of
the screen_info does not change accordingly. In short, it
From: Sui Jingfeng
Per Documentation/process/license-rules.rst, the SPDX MIT identifier is
equivalent to including the entire MIT license text from
LICENSES/preferred/MIT.
Replace the MIT license text with the equivalent SPDX identifier.
Cc: David Airlie
Cc: Daniel Vetter
Cc: Maarten
From: Sui Jingfeng
This patch adds the aperture_contain_firmware_fb() function to do the
determination. Unfortunately due to the fact that apertures list will be
freed dynamically, the location and size information of the firmware fb
will be lost after dedicated drivers call
From: Sui Jingfeng
This patch replaces the leading space with a tab and removes the double
blank line, no functional change.
Cc: Bjorn Helgaas
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Thomas Zimmermann
Cc: David Airlie
Cc: Daniel Vetter
Signed-off-by: Sui Jingfeng
Reviewed-by: Andi
From: Sui Jingfeng
Deal only with the VGA devcie(pdev->class == 0x0300), so replace the
pci_get_subsys() function with pci_get_class(). Filter the non-PCI display
device(pdev->class != 0x0300) out. There no need to process the non-display
PCI device.
Cc: Bjorn Helgaas
Signed-off-by: Sui
From: Sui Jingfeng
The io_state variable in the vga_arb_write() function is declared with
unsigned int type, while the vga_str_to_iostate() function takes int *
type. To keep them consistent, replace the third argument of
vga_str_to_iostate() function with the unsigned int * type.
Cc: Bjorn
The vga_is_firmware_default() function is arch-dependent, it's probably
wrong if we simply remove the arch guard. As the VRAM BAR which contains
firmware framebuffer may move, while the lfb_base and lfb_size members of
the screen_info does not change accordingly. In short, it should take the
The io_state variable in the vga_arb_write() function is declared with
unsigned int type, while the vga_str_to_iostate() function takes int *
type. To keep them consistent, replace the third argument of
vga_str_to_iostate() function with the unsigned int * type.
Cc: Bjorn Helgaas
Signed-off-by:
Per Documentation/process/license-rules.rst, the SPDX MIT identifier is
equivalent to including the entire MIT license text from
LICENSES/preferred/MIT.
Replace the MIT license text with the equivalent SPDX identifier.
Cc: David Airlie
Cc: Daniel Vetter
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Deal only with the VGA devcie(pdev->class == 0x0300), so replace the
pci_get_subsys() function with pci_get_class(). Filter the non-PCI display
device(pdev->class != 0x0300) out. There no need to process the non-display
PCI device.
Cc: Bjorn Helgaas
Signed-off-by: Sui Jingfeng
---
This patch replaces the leading space with a tab and removes the double
blank line, no functional change.
Cc: Bjorn Helgaas
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Thomas Zimmermann
Cc: David Airlie
Cc: Daniel Vetter
Signed-off-by: Sui Jingfeng
Reviewed-by: Andi Shyti
---
From: Sui Jingfeng <15330273...@189.cn>
The vga_is_firmware_default() function is arch-dependent, it's probably
wrong if we simply remove the arch guard. As the VRAM BAR which contains
firmware framebuffer may move, while the lfb_base and lfb_size members of
the screen_info does not change
On Fri, 2 Jun 2023 05:16:53 -0700
Yi Liu wrote:
> This gives notes for userspace applications on device cdev usage.
>
> Reviewed-by: Kevin Tian
> Signed-off-by: Yi Liu
> ---
> Documentation/driver-api/vfio.rst | 132 ++
> 1 file changed, 132 insertions(+)
>
>
Hi Arnd,
On Mon, Jun 12, 2023 at 02:43:59PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> When CONFIG_PNP is disabled, the mchbar_addr variable is only written but
> not read:
>
> drivers/gpu/drm/i915/soc/intel_gmch.c: In function
> 'intel_alloc_mchbar_resource':
>
On Fri, 2 Jun 2023 05:16:51 -0700
Yi Liu wrote:
> This converts noiommu test to use vfio_device->noiommu flag. Per this
> change, vfio_device_is_noiommu() is removed.
>
> Signed-off-by: Yi Liu
> ---
> drivers/vfio/group.c | 2 +-
> drivers/vfio/iommufd.c | 4 ++--
> drivers/vfio/vfio.h
On Fri, 2 Jun 2023 05:16:50 -0700
Yi Liu wrote:
> This moves the noiommu device determination and noiommu taint out of
> vfio_group_find_or_alloc(). noiommu device is determined in
> __vfio_register_dev() and result is stored in flag vfio_device->noiommu,
> the noiommu taint is added in the end
On Fri, 2 Jun 2023 05:16:49 -0700
Yi Liu wrote:
> group->type can be VFIO_NO_IOMMU only when vfio_noiommu option is true.
> And vfio_noiommu option can only be true if CONFIG_VFIO_NOIOMMU is enabled.
> So checking group->type is enough when testing noiommu.
>
> Signed-off-by: Yi Liu
> ---
>
On Fri, 2 Jun 2023 05:16:47 -0700
Yi Liu wrote:
> 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
>
On Fri, 2 Jun 2023 05:16:36 -0700
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 Fri, 2 Jun 2023 05:16:35 -0700
Yi Liu wrote:
> This avoids passing too much parameters in multiple functions. Per the
> input parameter change, rename the function to be vfio_df_open/close().
>
> Reviewed-by: Kevin Tian
> Reviewed-by: Jason Gunthorpe
> Reviewed-by: Eric Auger
>
== Series Details ==
Series: drm/i915/gmch: avoid unused variable warning
URL : https://patchwork.freedesktop.org/series/119197/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13262_full -> Patchwork_119197v1_full
Summary
== Series Details ==
Series: drm/i915: GSC FW support for MTL (rev4)
URL : https://patchwork.freedesktop.org/series/117396/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13263 -> Patchwork_117396v4
Summary
---
== Series Details ==
Series: drm/i915: GSC FW support for MTL (rev4)
URL : https://patchwork.freedesktop.org/series/117396/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915: GSC FW support for MTL (rev4)
URL : https://patchwork.freedesktop.org/series/117396/
State : warning
== Summary ==
Error: dim checkpatch failed
57f9c0764e65 drm/i915/gsc: fixes and updates for GSC memory allocation
fa4495ba0bfe drm/i915/mtl/gsc: extract
Verify that SLPC API works as expected after a suspend. Added
another subtest that does multiple GT resets and checks freq api
works as expected after each one.
We now check requested frequency instead of soft min/max after a
reset or suspend. That ensures the soft limits got applied
correctly at
The vga_is_firmware_default() function is arch-dependent, it's probably
wrong if we simply remove the arch guard. As the VRAM BAR which contains
firmware framebuffer may move, while the lfb_base and lfb_size members of
the screen_info does not change accordingly. In short, it should take the
From: Sui Jingfeng
Per Documentation/process/license-rules.rst, the SPDX MIT identifier is
equivalent to including the entire MIT license text from
LICENSES/preferred/MIT.
Replace the MIT license text with the equivalent SPDX identifier.
Signed-off-by: Sui Jingfeng
Reviewed-by: Andi Shyti
From: Sui Jingfeng
Deal only with the VGA devcie(pdev->class == 0x0300), so replace the
pci_get_subsys() function with pci_get_class(). Filter the non-PCI display
device(pdev->class != 0x0300) out. There no need to process the non-display
PCI device.
Signed-off-by: Sui Jingfeng
---
From: Sui Jingfeng
This patch replaces the leading space with a tab and removes the double
blank line, no functional change.
Signed-off-by: Sui Jingfeng
Reviewed-by: Andi Shyti
---
drivers/pci/vgaarb.c | 108 -
include/linux/vgaarb.h | 4 +-
2
From: Sui Jingfeng
The vga_is_firmware_default() function is arch-dependent, it's probably
wrong if we simply remove the arch guard. As the VRAM BAR which contains
firmware framebuffer may move, while the lfb_base and lfb_size members of
the screen_info does not change accordingly. In short, it
From: Sui Jingfeng
The io_state variable in the vga_arb_write() function is declared with
unsigned int type, while the vga_str_to_iostate() function takes int *
type. To keep them consistent, replace the third argument of
vga_str_to_iostate() function with the unsigned int * type.
Add a new debugfs to dump information about the GSC. This includes:
- the FW path and SW tracking status;
- the release, security and compatibility versions;
- the HECI1 status registers.
Note that those are the same registers that the mei driver dumps in
their own status sysfs on DG2 (where mei
The release and security versions of the GSC binary are not used at
runtime to decide interface compatibility (there is a separate version
for that), but they're still useful for debug, so it is still worth
extracting them and printing them out in dmesg.
To get to these version, we need to
The compatibility version is queried via an MKHI command. Right now, the
only existing interface is 1.0
This is basically the interface version for the GSC FW, so the plan is
to use it as the main tracked version, including for the binary naming
in the fetch code.
v2: use define for the object
A few fixes/updates are required around the GSC memory allocation and it
is easier to do them all at the same time. The changes are as follows:
1 - Switch the memory allocation to stolen memory. We need to avoid
accesses from GSC FW to normal memory after the suspend function has
completed and to
Last chunk of the required support for the GSC FW. This includes some
fixes to the GSC memory allocation, FW idefinition and version
management, plus a new debugfs for debug information.
The FW team has asked to not send the current FW blob to
linux-firmware yet, as they're planning some updates.
> -Original Message-
> From: Deak, Imre
> Sent: Monday, June 12, 2023 6:28 PM
> To: Murthy, Arun R
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCHv2] drm/i915/display/dp: On AUX xfer timeout
> restart freshly
>
> On Mon, Jun 12, 2023 at 02:47:37PM +0300, Murthy,
== Series Details ==
Series: drm/i915/gmch: avoid unused variable warning
URL : https://patchwork.freedesktop.org/series/119197/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13262 -> Patchwork_119197v1
Summary
---
== Series Details ==
Series: drm/i915/gmch: avoid unused variable warning
URL : https://patchwork.freedesktop.org/series/119197/
State : warning
== Summary ==
Error: dim checkpatch failed
578f7e0a22b6 drm/i915/gmch: avoid unused variable warning
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible
Hi Arnd,
On Mon, Jun 12, 2023 at 02:43:59PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> When CONFIG_PNP is disabled, the mchbar_addr variable is only written but
> not read:
>
> drivers/gpu/drm/i915/soc/intel_gmch.c: In function
> 'intel_alloc_mchbar_resource':
>
== Series Details ==
Series: fdinfo memory stats (rev3)
URL : https://patchwork.freedesktop.org/series/119082/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13262 -> Patchwork_119082v3
Summary
---
**FAILURE**
On Mon, Jun 12, 2023 at 02:47:37PM +0300, Murthy, Arun R wrote:
> > -Original Message-
> > From: Deak, Imre
> > Sent: Monday, June 12, 2023 5:07 PM
> > To: Murthy, Arun R
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] [PATCHv2] drm/i915/display/dp: On AUX xfer
== Series Details ==
Series: fdinfo memory stats (rev3)
URL : https://patchwork.freedesktop.org/series/119082/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: fdinfo memory stats (rev3)
URL : https://patchwork.freedesktop.org/series/119082/
State : warning
== Summary ==
Error: dim checkpatch failed
0e7a9361b003 drm/i915: Add ability for tracking buffer objects per client
e0e7d111353c drm/i915: Record which client owns a
From: Arnd Bergmann
When CONFIG_PNP is disabled, the mchbar_addr variable is only written but
not read:
drivers/gpu/drm/i915/soc/intel_gmch.c: In function
'intel_alloc_mchbar_resource':
drivers/gpu/drm/i915/soc/intel_gmch.c:41:13: error: variable 'mchbar_addr' set
but not used
> -Original Message-
> From: Deak, Imre
> Sent: Monday, June 12, 2023 5:07 PM
> To: Murthy, Arun R
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCHv2] drm/i915/display/dp: On AUX xfer timeout
> restart freshly
>
> On Thu, Jun 08, 2023 at 03:02:18PM +0530, Arun R
On Thu, Jun 08, 2023 at 03:02:18PM +0530, Arun R Murthy wrote:
> At the begining of the aux transfer a check for aux control busy bit is
> done. Then as per the spec on aux transfer timeout, need to retry
> freshly for 3 times with a delay which is taken care by the control
> register.
> On each
On Tue, Jun 6, 2023 at 12:33 PM Daniele Ceraolo Spurio
wrote:
>
> The following changes since commit fc90c59beebd551dde5fe5eb3e76d36651ba08fb:
>
> Merge branch 'db410c' of https://github.com/lumag/linux-firmware
> (2023-05-31 07:35:15 -0400)
>
> are available in the Git repository at:
>
>
From: Tvrtko Ursulin
To enable accounting of indirect client memory usage (such as page tables)
in the following patch, lets start recording the creator of each PPGTT.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gem/i915_gem_context.c | 11 ---
From: Tvrtko Ursulin
Use the newly added drm_print_memory_stats helper to show memory
utilisation of our objects in drm/driver specific fdinfo output.
To collect the stats we walk the per memory regions object lists
and accumulate object size into the respective drm_memory_stats
categories.
From: Tvrtko Ursulin
Account page table backing store against the owning client memory usage
stats.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/intel_gtt.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_gtt.c
From: Tvrtko Ursulin
Account ring buffers and logical context space against the owning client
memory usage stats.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/intel_context.c | 8
drivers/gpu/drm/i915/i915_drm_client.c | 10 ++
From: Tvrtko Ursulin
I added tracking of most classes of objects which contribute to client's memory
footprint and accouting along the similar lines as in Rob's msm code. Then
printing it out to fdinfo using the drm helper Rob added.
Accounting by keeping per client lists may not be the most
From: Tvrtko Ursulin
In order to show per client memory usage lets add some infrastructure
which enables tracking buffer objects owned by clients.
We add a per client list protected by a new per client lock and to support
delayed destruction (post client exit) we make tracked objects hold
On 09/06/2023 18:09, Rob Clark wrote:
On Fri, Jun 9, 2023 at 7:12 AM Tvrtko Ursulin
wrote:
On 09/06/2023 13:44, Iddamsetty, Aravind wrote:
On 09-06-2023 17:41, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
I need a new flavour of the drm_gem_prime_fd_to_handle helper, one which
will
66 matches
Mail list logo
