In order to ease up on the logic, break the current code to gather the
dssdevs:
first get all available dssdevs, then call connect on each dssdev. As the
last step remove the dssdevs which failed to connect from the available
dssdev list.
Signed-off-by: Peter Ujfalusi
---
Instead of reaching back to DSS to iterate through the dss_devices every
time, use an internal array where we store the available and usable
dss_devices.
At the same time remove the omapdss_device_is_connected() check from
omap_modeset_init() as it became irrelevant: We are not adding dssdevs
if
On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
> From: Colin Ian King
>
> The pointer workload is dereferenced before it is null checked, hence
> there is a potential for a null pointer dereference on workload. Fix
> this by only dereferencing workload after it is
Signed-off-by: Giulio Benetti
---
.../display/panel/cdtech,s043wq26h-ct7.txt | 7 ++
drivers/gpu/drm/panel/panel-simple.c | 28 ++
2 files changed, 35 insertions(+)
create mode 100644
This adds a vendor prefix "micronova" for Micronova srl
Signed-off-by: Giulio Benetti
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
On Wed, Mar 21, 2018 at 09:45:09PM +0100, Thomas Hellstrom wrote:
> Hi, Ville,
>
> On 11/14/2017 07:32 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Currently userspace is allowed to feed in any king of garbage in the
> > high bits of the mode
Hi, Ville,
On 11/14/2017 07:32 PM, Ville Syrjala wrote:
From: Ville Syrjälä
Currently userspace is allowed to feed in any king of garbage in the
high bits of the mode flags/type, as are drivers when probing modes.
Reject any mode with bogus flags/type.
On 03/21/2018 09:51 PM, Ville Syrjälä wrote:
On Wed, Mar 21, 2018 at 09:45:09PM +0100, Thomas Hellstrom wrote:
Hi, Ville,
On 11/14/2017 07:32 PM, Ville Syrjala wrote:
From: Ville Syrjälä
Currently userspace is allowed to feed in any king of garbage in the
high
From: Colin Ian King
The pointer workload is dereferenced before it is null checked, hence
there is a potential for a null pointer dereference on workload. Fix
this by only dereferencing workload after it is null checked.
Detected by CoverityScan, CID#1466017
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #40 from taij...@posteo.de ---
OK, I hate to be necrobumping this, but I've continued to follow and test
drm-next-4.17-wip and it seems that not only has the backlight patch from #34
not made it in yet, but also that the forced atpx
From: Ville Syrjälä
Apparently xf86-video-vmware leaves the mode->type uninitialized
when feeding the mode to the kernel. Thus we have no choice but
to accept the garbage in. We'll just ignore any of the bits we
don't want. The mode type is just a hint anyway, and
The A20-Linova1-4_3 HMI, also called Q027_2_A which is printed on
production label, is an industrial Human Machine Interface.
It features:
- 512MB DDR RAM
- 1 Sd-card >= 4GB
- 1 Usb otg(programmable via software) with A-Usb Connector
- 1 Usb host
- 1 Buzzer
- 1 Input for LiPo
- 1 Relay to signal
This adds a vendor prefix "cdtech" for CDTech(H.K.) Electronics Limited
Signed-off-by: Giulio Benetti
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The A20-Linova1-7 HMI, also called Q027_2_F which is printed on production
label, is an industrial Human Machine Interface.
It features:
- 512MB DDR RAM
- 1 Sd-card >= 4GB
- 1 Usb otg(programmable via software) with A-Usb Connector
- 1 Usb host
- 1 Buzzer
- 1 Input for LiPo
- 1 Relay to signal
The A20 supports RGB888 with H/V sync from LCD0. Add a pinmux setting
for the needed pins.
Signed-off-by: Giulio Benetti
---
arch/arm/boot/dts/sun7i-a20.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi
Signed-off-by: Giulio Benetti
---
.../display/panel/cdtech,s070wv95-ct16.txt | 7 ++
drivers/gpu/drm/panel/panel-simple.c | 27 ++
2 files changed, 34 insertions(+)
create mode 100644
https://bugs.freedesktop.org/show_bug.cgi?id=105240
Hleb Valoshka <375...@gmail.com> changed:
What|Removed |Added
Version|unspecified |17.3
https://bugs.freedesktop.org/show_bug.cgi?id=105240
Hleb Valoshka <375...@gmail.com> changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop
On Wed, 2018-03-21 at 18:26 +, Colin King wrote:
> From: Colin Ian King
>
> The for-loops process data in the mclk_table but use slck_table.count
> as the loop index limit. I believe these are cut-n-paste errors from
> the previous almost identical loops as
On 21/03/18 19:23, Chris Wilson wrote:
> Quoting Colin Ian King (2018-03-21 19:18:28)
>> On 21/03/18 19:09, Joe Perches wrote:
>>> On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
From: Colin Ian King
The pointer workload is dereferenced before it is
https://bugs.freedesktop.org/show_bug.cgi?id=105426
--- Comment #7 from Tapani Pälli ---
(In reply to iive from comment #6)
> > It looks like the same problem as bug 104668 and bug 104777.
> > 4195eed961ccfe404ae81b9112189fc93a254ded fixes the problem.
>
> Well, this is kind
From: Colin Ian King
The for-loops process data in the mclk_table but use slck_table.count
as the loop index limit. I believe these are cut-n-paste errors from
the previous almost identical loops as indicated by static analysis.
Fix these.
Detected by CoverityScan,
On Wed, Mar 21, 2018 at 04:28:46PM +, Nipun Gupta wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Wednesday, March 21, 2018 15:05
> > To: Nipun Gupta
> > Cc: robin.mur...@arm.com; h...@lst.de;
On 21/03/18 19:09, Joe Perches wrote:
> On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
>> From: Colin Ian King
>>
>> The pointer workload is dereferenced before it is null checked, hence
>> there is a potential for a null pointer dereference on workload. Fix
>>
Quoting Colin Ian King (2018-03-21 19:18:28)
> On 21/03/18 19:09, Joe Perches wrote:
> > On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
> >> From: Colin Ian King
> >>
> >> The pointer workload is dereferenced before it is null checked, hence
> >> there is a
On Wed, 2018-03-21 at 19:18 +, Colin Ian King wrote:
> On 21/03/18 19:09, Joe Perches wrote:
> > On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
> > > From: Colin Ian King
> > >
> > > The pointer workload is dereferenced before it is null checked, hence
> > >
On Wed, Mar 21, 2018 at 12:25:22PM +0530, Nipun Gupta wrote:
> It's bus specific aspect to map a given device on the bus and
> relevant firmware description of its DMA configuration.
> So, this change introduces '/dma_configure/' as bus callback
> giving flexibility to busses for implementing its
https://bugs.freedesktop.org/show_bug.cgi?id=105651
spgle...@gmail.com changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
On Wed, Mar 21, 2018 at 12:25:23PM +0530, Nipun Gupta wrote:
> With each bus implementing its own DMA configuration callback,
> there is no need for bus to explicitly have force_dma in its
> global structure. This patch modifies of_dma_configure API to
> accept an input parameter which specifies
https://bugs.freedesktop.org/show_bug.cgi?id=105651
Bug ID: 105651
Summary: Vega64 doesn't output properly onto dell up2715k at
5120x2880
Product: DRI
Version: unspecified
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=105651
spgle...@gmail.com changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=99801
spgle...@gmail.com changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugzilla.kernel.org/show_bug.cgi?id=199123
--- Comment #11 from david becerra (davidbecerrapor...@gmail.com) ---
issue still present in 4.16rc6
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #4 from freedesk...@kp-tech.hu ---
Created attachment 138236
--> https://bugs.freedesktop.org/attachment.cgi?id=138236=edit
Xorg log when using the 4.15 kernel
Thank you for your help! Sorry for the delay, the Xorg log attached I
Hi,
Changes since v4:
- rebased the series on drm-next
NOTE on the tegra patch: since the v4 series the atomic check of tegra got
additional call to tegra_display_hub_atomic_check().
Based on the code the order, placement of the hub check is not strict, it can
be done as the last step as well.
On 2018-03-20 20:47, Sean Paul wrote:
On Tue, Mar 20, 2018 at 07:13:38PM +0530, skoll...@codeaurora.org
wrote:
On 2018-03-19 19:29, Sean Paul wrote:
> On Wed, Mar 14, 2018 at 11:21:38AM +0530, Sravanthi Kollukuduru wrote:
> > This change adds the hardware catalog information in driver source
>
Hi all,
A series of commits
a82f034765fa ("drm: omapdrm: Split init and cleanup from probe and remove
functions")
to
663ac57b285d ("drm: omapdrm: venc: Allocate the venc private data structure
dynamically")
are missing a Signed-off-by from their commiter.
--
Cheers,
Stephen Rothwell
Am 21.03.2018 um 09:18 schrieb Daniel Vetter:
[SNIP]
They're both in i915_gem_userptr.c, somewhat interleaved. Would be
interesting if you could show what you think is going wrong in there
compared to amdgpu_mn.c.
i915 implements only one callback:
static const struct mmu_notifier_ops
https://bugs.freedesktop.org/show_bug.cgi?id=105651
spgle...@gmail.com changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
When we are running without fbdev, transitioning from the login screen to
X or gnome-shell/wayland will cause a vt switch and the driver will disable
svga mode, losing all modesetting resources. However, the kms atomic state
does not reflect that and may think that a crtc is still turned on, which
When validating legacy surfaces, the backup bo might be destroyed at
surface validate time. However, the kms resource validation code may have
the bo reserved, so we will destroy a locked mutex. While there shouldn't
be any other users of that mutex when it is destroyed, it causes a lock
leak and
On unknown/unhandled ioctls the driver should return an error, so
userspace knows it tried to use something unsupported.
Cc: sta...@vger.kernel.org
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
https://bugs.freedesktop.org/show_bug.cgi?id=105619
--- Comment #5 from freedesk...@kp-tech.hu ---
Created attachment 138237
--> https://bugs.freedesktop.org/attachment.cgi?id=138237=edit
Xorg log when running on kernel 4.13 (ubuntu)
Here is the Xorg log when running on kernel 4.13.
it has
Hi Arnd,
On Wednesday, 21 March 2018 09:38:35 EET Arnd Bergmann wrote:
> On Tue, Mar 20, 2018 at 9:15 PM, Laurent Pinchart wrote:
> > On Friday, 16 March 2018 10:25:25 EET Arnd Bergmann wrote:
> >> On Fri, Mar 16, 2018 at 2:39 AM, wrote:
> >>> On Thursday, March 15, 2018
If we allocate the drm_device earlier we can just return the error code
without the need to use goto.
Do the unref of the drm_device as a last step when cleaning up. This will
make the drm_device available longer for us and makes sure that we only
free up the memory when all other cleanups have
Hi,
Changes since v1:
- rebased it on drm-next
- Dropped the devm_kzalloc conversion patch
Changes since RFC:
- Comments from Laurent have been addressed:
- Get alias ID once and store it for later use in sorting
- Commit message updated for 'drm/omap: Manage the usable omap_dss_device list
Sort the dssdev array based on DT aliases.
With this change we can remove the panel ordering from dss/display.c and
have all sorting related to dssdevs in one place.
Signed-off-by: Peter Ujfalusi
---
drivers/gpu/drm/omapdrm/dss/display.c | 2 ++
Instead of drivers duplicating the drm_atomic_helper_check() code to be
able to normalize the zpos they can use the normalize_zpos flag to let the
drm core to do it.
Signed-off-by: Peter Ujfalusi
---
drivers/gpu/drm/drm_atomic_helper.c | 11 +++
Set the drm_mode_config->normalize_zpos and call drm_atomic_helper_check()
from rcar_du_atomic_check() instead of re implementing the function locally.
Signed-off-by: Peter Ujfalusi
CC: Laurent Pinchart
Acked-by: Daniel Vetter
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_mode_config->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Inki Dae
CC: Joonyoung Shim
Planes with identical zpos value will result undefined behavior:
disappearing planes, screen flickering and it is not supported by the
hardware.
Use normalized zpos to make sure that we don't encounter invalid
configuration.
Signed-off-by: Peter Ujfalusi
CC: Tomi
Set the drm_mode_config->normalize_zpos and call the generic
drm_atomic_helper_check() instead of duplicating it within
tegra_atomic_check().
Call tegra_display_hub_atomic_check() after the drm_atomic_helpre_check()
returned without error.
Signed-off-by: Peter Ujfalusi
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_mode_config->normalize_zpos.
Note: the drm_atomic_helper_check() now includes
if (state->legacy_cursor_update)
state->async_update =
https://bugzilla.kernel.org/show_bug.cgi?id=199157
Bug ID: 199157
Summary: BUG: unable to handle kernel NULL pointer dereference
at
Product: Drivers
Version: 2.5
Kernel Version: 4.15.10
Hardware:
On Tue, Mar 20, 2018 at 9:15 PM, Laurent Pinchart
wrote:
> Hi Arnd,
>
> On Friday, 16 March 2018 10:25:25 EET Arnd Bergmann wrote:
>> On Fri, Mar 16, 2018 at 2:39 AM, wrote:
>> > On Thursday, March 15, 2018 8:37 AM, Arnd Bergmann wrote:
On Tue, Mar 20, 2018 at 09:17:52PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Currently we're leaking fbs on load detect on account of nothing setting
> up plane->old_fb for the drm_atomic_clean_old_fb() call in
>
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Kyle De'Vir (kyle.de...@mykolab.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Tue, Mar 20, 2018 at 06:47:57PM +0100, Christian König wrote:
> Am 20.03.2018 um 15:08 schrieb Daniel Vetter:
> > [SNIP]
> > For the in-driver reservation path (CS) having a slow-path that grabs a
> > temporary reference, drops the vram lock and then locks the reservation
> > normally (using
https://bugs.freedesktop.org/show_bug.cgi?id=89713
redearth...@gmail.com changed:
What|Removed |Added
Attachment #114681|0 |1
is obsolete|
On Tue, Mar 20, 2018 at 06:47:57PM +0100, Christian König wrote:
> Am 20.03.2018 um 15:08 schrieb Daniel Vetter:
> > [SNIP]
> > For the in-driver reservation path (CS) having a slow-path that grabs a
> > temporary reference, drops the vram lock and then locks the reservation
> > normally (using
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #65 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
Hi
IOMMU is disabled:
root@qt5122:~# ls /sys/class/iommu
ls: cannot access '/sys/class/iommu': No such file or directory
root@qt5122:~# dmesg | grep -i iommu
root@qt5122:~#
On 03/20/2018 03:47 PM, Daniel Vetter wrote:
On Tue, Mar 20, 2018 at 01:58:01PM +0200, Oleksandr Andrushchenko wrote:
On 03/19/2018 05:28 PM, Daniel Vetter wrote:
There should be no difference between immediate removal and delayed
removal of the drm_device from the xenbus pov. The lifetimes of
On unknown/unhandled ioctls the driver should return an error, so
userspace knows it tried to use something unsupported.
Cc: linux-sta...@vger.kernel.org
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, Mar 20, 2018 at 11:29:27AM -0700, Santha Meena Ramamoorthy wrote:
> Replace drm_gem_object_reference/unreference function with *_get/put()
> suffixes, because it is shorter and consistent with the kernel
> kref_get/put() functions. The following Coccinelle script was used:
>
> @@
>
On Tue, Mar 20, 2018 at 09:01:11PM -0400, Rob Clark wrote:
> On Tue, Mar 20, 2018 at 6:58 PM, Daniel Stone wrote:
> > getfb can only return a single plane, so reject attempts to use it with
> > multi-plane framebuffers.
> >
>
> yeah, this seems like a pretty good idea,
>
Am 21.03.2018 um 09:28 schrieb Daniel Vetter:
On Tue, Mar 20, 2018 at 06:47:57PM +0100, Christian König wrote:
Am 20.03.2018 um 15:08 schrieb Daniel Vetter:
[SNIP]
For the in-driver reservation path (CS) having a slow-path that grabs a
temporary reference, drops the vram lock and then locks
On Wed, 21 Mar 2018 10:08:03 +0100
Gerd Hoffmann wrote:
> On unknown/unhandled ioctls the driver should return an error, so
> userspace knows it tried to use something unsupported.
>
> Cc: sta...@vger.kernel.org
> Signed-off-by: Gerd Hoffmann
> ---
>
The previous patch implements the ordering of the dss_devices based on DT
aliases in omap_drm.c, so there is no need to do the ordering in
dss/display.c anymore.
At the same time remove the alias member of the omap_dss_device struct
since it is no longer needed. The only place it was used is in
omapdrm.displays (int array) can be used to reorder the displays by id if
needed. It can be also used to disable display.
If the board have two active displays:
0 - LCD
1 - HDMI
then:
omapdrm.displays=0,1 - represents the original order (LCD, HDMI)
omapdrm.displays=1,0 - represents reverse order
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #67 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
I have coreboot. So I do not have the typical menu.
I have an FPGA writing to the main memory, and that could not happen if iommu
is enabled without extra configuration.
If
https://bugs.freedesktop.org/show_bug.cgi?id=105530
--- Comment #6 from txtsd ---
Also, is there an older kernel I should try? Give me a branch/commit, and I'll
compile and see if the issue exists.
--
You are receiving this mail because:
You are the
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #66 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
(In reply to Ricardo Ribalda from comment #65)
> Hi
>
> IOMMU is disabled:
>
> root@qt5122:~# ls /sys/class/iommu
> ls: cannot access '/sys/class/iommu': No such file or
Hi,
On 21 March 2018 at 08:27, Daniel Vetter wrote:
> On Tue, Mar 20, 2018 at 09:01:11PM -0400, Rob Clark wrote:
>> On Tue, Mar 20, 2018 at 6:58 PM, Daniel Stone wrote:
>> > getfb can only return a single plane, so reject attempts to use it with
>> >
On Wed, Mar 21, 2018 at 09:25:06AM +0100, Daniel Vetter wrote:
> On Tue, Mar 20, 2018 at 09:17:52PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Currently we're leaking fbs on load detect on account of nothing setting
> > up plane->old_fb for the
https://bugs.freedesktop.org/show_bug.cgi?id=105633
Christian König changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #41 from Alex Deucher ---
(In reply to taijian from comment #40)
> OK, I hate to be necrobumping this, but I've continued to follow and test
> drm-next-4.17-wip and it seems that not only has the backlight
https://bugs.freedesktop.org/show_bug.cgi?id=104880
Konstantin A. Lepikhov changed:
What|Removed |Added
Summary|No sound via DP on R9 Fury |No
On Wed, Mar 21, 2018 at 11:09 PM, Joe Perches wrote:
> Some functions definitions have either the initial open brace and/or
> the closing brace outside of column 1.
>
> Move those braces to column 1.
>
> This allows various function analyzers like gnu complexity to work
>
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #42 from taij...@posteo.de ---
(In reply to Alex Deucher from comment #41)
> Sorry, my impression from comment 29 was that messing the the OSI string
> fixed the issue. Is that not the case? Do you still need to force ATPX?
> If
https://bugs.freedesktop.org/show_bug.cgi?id=105426
i...@yahoo.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi Dave,
A few more fixes for 4.16. Mostly for displays:
- A fix for DP handling on radeon
- Fix banding on eDP panels
- Fix HBR audio
- Fix for disabling VGA mode on Raven that leads to a corrupt or
blank display on some platforms
The following changes since commit
There are cases where other parts of the kernel may wish to store data
associated with individual cgroups without building a full cgroup
controller. Let's add interfaces to allow them to register and lookup
this private data for individual cgroups.
A kernel system (e.g., a driver) that wishes to
Introduce a new DRM_IOCTL_I915_CGROUP_SETPARAM ioctl that will allow
userspace to set i915-specific parameters for individual cgroups. i915
cgroup data will be registered and later looked up via the new
cgroup_priv infrastructure.
v2:
- Large rebase/rewrite for new cgroup_priv interface
v3:
-
In preparation for adding cgroup-based priority adjustments, let's
define the driver's priority values a little more clearly.
v2:
- checkpatch warning fix (Intel CI)
Cc: Chris Wilson
Signed-off-by: Matt Roper
---
Wraps task_dfl_cgroup() to also take a reference to the cgroup.
v2:
- Eliminate cgroup_mutex and make lighter-weight (Tejun)
Cc: Tejun Heo
Cc: cgro...@vger.kernel.org
Signed-off-by: Matt Roper
---
include/linux/cgroup.h | 29
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #24 from Ainola ---
My stability has been fine since I last commented. I'm now on 4.15.10+these
patches. However, my monitors won't turn off: When the screen turns off it'll
come right back on after a second.
Just
Some functions definitions have either the initial open brace and/or
the closing brace outside of column 1.
Move those braces to column 1.
This allows various function analyzers like gnu complexity to work
properly for these modified functions.
Signed-off-by: Joe Perches
This version of the patch series just contains some minor updates to
address checkpatch and sparse warnings. There are no serious design or
implementation changes since v4.
You can find the previous versions of this series (and more detailed
cover letters) here:
(v1)
Getting cgroup private data for the current process' cgroup is such a
common pattern that we should add a convenience wrapper for it.
Signed-off-by: Matt Roper
---
include/linux/cgroup.h | 1 +
kernel/cgroup/cgroup.c | 23 +++
2 files changed, 24
Usually display-boosted contexts get treated as
I915_CONTEXT_MAX_USER_PRIORITY+1, which prioritizes them above regular
GPU contexts. Now that we allow a much larger range of effective
priority values via per-cgroup priority offsets, a system administrator
may want more detailed control over how
There are cases where a system integrator may wish to raise/lower the
priority of GPU workloads being submitted by specific OS process(es),
independently of how the software self-classifies its own priority.
Exposing "priority offset" as an i915-specific cgroup parameter will
enable such
Update i915_context_status to include priority information.
v2:
- Clarify that the offset is based on cgroup (Chris)
Signed-off-by: Matt Roper
---
drivers/gpu/drm/i915/i915_debugfs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
Hi Dave,
Here goes drm-intel-fixes-2018-03-21:
One fix for DP MST and one fix for GPU reset on hang check.
Thanks,
Rodrigo.
The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f:
Linux 4.16-rc6 (2018-03-18 17:48:42 -0700)
are available in the git repository at:
On Wed, Mar 21, 2018 at 04:05:31PM +0530, skoll...@codeaurora.org wrote:
> On 2018-03-20 20:47, Sean Paul wrote:
> > On Tue, Mar 20, 2018 at 07:13:38PM +0530, skoll...@codeaurora.org wrote:
> > > On 2018-03-19 19:29, Sean Paul wrote:
> > > > On Wed, Mar 14, 2018 at 11:21:38AM +0530, Sravanthi
On Tue, Mar 20, 2018 at 11:35:40PM -0400, Rob Clark wrote:
> On Tue, Mar 20, 2018 at 11:16 AM, Alexandru-Cosmin Gheorghe
> wrote:
> > On Tue, Mar 20, 2018 at 10:00:17AM -0400, Sean Paul wrote:
> >> On Tue, Mar 13, 2018 at 04:21:20PM +, Alexandru Gheorghe
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #69 from Ricardo Ribalda (ricardo.riba...@gmail.com) ---
This is my kernel configuration:
ricardo@neopili:~/curro/kernel-upstream$ cat .config | grep -i IOMMU
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
From: Oleksandr Andrushchenko
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM master.
Configuration of both
From: Oleksandr Andrushchenko
Hello!
This patch series adds support for Xen [1] para-virtualized
frontend display driver. It implements the protocol from
include/xen/interface/io/displif.h [2].
Accompanying backend [3] is implemented as a user-space application
Hi Sean & Rob,
On Wed, Mar 21, 2018 at 10:01:07AM -0400, Sean Paul wrote:
> On Tue, Mar 20, 2018 at 11:35:40PM -0400, Rob Clark wrote:
> > On Tue, Mar 20, 2018 at 11:16 AM, Alexandru-Cosmin Gheorghe
> > wrote:
> > > On Tue, Mar 20, 2018 at 10:00:17AM -0400,
On unknown/unhandled ioctls the driver should return an error, so
userspace knows it tried to use something unsupported.
Cc: sta...@vger.kernel.org
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
1 - 100 of 117 matches
Mail list logo