https://bugs.freedesktop.org/show_bug.cgi?id=106875
Timothy Arceri changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Mesa core
On Mon, 1 Jul 2019 at 12:37, Yongxin Liu wrote:
>
> In nouveau_conn_reset(), if connector->state is true,
> __drm_atomic_helper_connector_destroy_state() will be called,
> but the memory pointed by asyc isn't freed. Memory leak happens
> in the following function
Thanks for the notice. I had already had a fix for this, but forgot to push
it. It's pushed now.
Marek
On Wed, Jul 3, 2019 at 7:10 PM John Stultz wrote:
> Building with clang, I'm seeing
> u_blitter.h:627:1: error: control may reach end of non-void function
> [-Werror,-Wreturn-type]
>
> The
https://bugs.freedesktop.org/show_bug.cgi?id=98693
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message
https://bugs.freedesktop.org/show_bug.cgi?id=93475
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=92999
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=92755
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #7 from Timothy
https://bugs.freedesktop.org/show_bug.cgi?id=79417
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
Add documentation for KUnit, the Linux kernel unit testing framework.
- Add intro and usage guide for KUnit
- Add API reference
Signed-off-by: Felix Guo
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
Changes Since Last Revision:
- Fixed a
From: Iurii Zaikin
KUnit tests for initialized data behavior of proc_dointvec that is
explicitly checked in the code. Includes basic parsing tests including
int min/max overflow.
Signed-off-by: Iurii Zaikin
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan
Add myself as maintainer of KUnit, the Linux kernel's unit testing
framework.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
From: Felix Guo
The ultimate goal is to create minimal isolated test binaries; in the
meantime we are using UML to provide the infrastructure to run tests, so
define an abstract way to configure and run tests that allow us to
change the context in which tests are built without affecting the
Add entry for the new proc sysctl KUnit test to the PROC SYSCTL section.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
Acked-by: Luis Chamberlain
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
Add support for aborting/bailing out of test cases, which is needed for
implementing assertions.
An assertion is like an expectation, but bails out of the test case
early if the assertion is not met. The idea with assertions is that you
use them to state all the preconditions for your test.
From: Avinash Kondareddy
Add unit tests for KUnit managed resources. KUnit managed resources
(struct kunit_resource) are resources that are automatically cleaned up
at the end of a KUnit test, similar to the concept of devm_* managed
resources.
Signed-off-by: Avinash Kondareddy
Signed-off-by:
Add defconfig for UML and a fragment that can be used to configure other
architectures for building KUnit tests. Add option to kunit_tool to use
a defconfig to create the kunitconfig.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
Add support for assertions which are like expectations except the test
terminates if the assertion is not satisfied.
The idea with assertions is that you use them to state all the
preconditions for your test. Logically speaking, these are the premises
of the test case, so if a premise isn't true,
Add KUnit tests for the KUnit test abort mechanism (see preceding
commit). Add tests both for general try catch mechanism as well as
non-architecture specific mechanism.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
kunit/Makefile| 3 +-
Fix the following warning seen on GCC 7.3:
kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls
through to next function kunit_test_catch()
kunit_try_catch_throw is a function added in the following patch in this
series; it allows KUnit, a unit testing framework for the
A lot of the expectation and assertion infrastructure prints out fairly
complicated test failure messages, so add a C++ style log library for
for logging test results.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
include/kunit/kunit-stream.h
Add support for expectations, which allow properties to be specified and
then verified in tests.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
include/kunit/test.h | 525 +++
kunit/test.c | 66
KUnit is a new unit testing framework for the kernel and when used is
built into the kernel as a part of it. Add KUnit to the root Kconfig and
Makefile to allow it to be actually built.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
Kconfig |
Add a test for string stream along with a simpler example.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
kunit/Kconfig | 21 +
kunit/Makefile | 4 ++
kunit/example-test.c | 88
A number of test features need to do pretty complicated string printing
where it may not be possible to rely on a single preallocated string
with parameters.
So provide a library for constructing the string as you go similar to
C++'s std::string.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg
Create a common API for test managed resources like memory and test
objects. A lot of times a test will want to set up infrastructure to be
used in test cases; this could be anything from just wanting to allocate
some memory to setting up a driver stack; this defines facilities for
creating "test
## TL;DR
This is a pretty straightforward follow-up to Stephen and Luis' comments
on PATCH v5: There is nothing that really changes any functionality or
usage with the minor exception that I renamed `struct kunit_module` to
`struct kunit_suite`. Nevertheless, a good deal of clean ups and fixes.
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and determine whether the code under test behaves as expected; this also
provides a way to group together related test cases in test suites (here
we call
https://bugs.freedesktop.org/show_bug.cgi?id=68527
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hiya,
Looks like the last -fixes pull for this cycle. One patch to fix a possible
double-free.
drm-misc-fixes-2019-07-03:
panfrost- Avoid double free by deleting GEM handle in create_bo failure
path (Boris)
Cc: Boris Brezillon
Cheers, Sean
The following changes since commit
On Fri, Jun 21, 2019 at 5:54 PM Brendan Higgins
wrote:
>
> On Fri, Jun 21, 2019 at 12:21 PM shuah wrote:
> >
> > On 6/21/19 12:13 PM, Theodore Ts'o wrote:
> > > On Fri, Jun 21, 2019 at 08:59:48AM -0600, shuah wrote:
> > ### But wait! Doesn't kselftest support in kernel testing?!
> >
>
On Wed, Jul 3, 2019 at 4:10 PM John Stultz wrote:
>
> With current master we're seeing build failures with AOSP:
> error: undefined symbol: ir3_nir_lower_imul
>
> This is due to the ir3_nir_imul.c file not being generated
> in the Android.mk files.
>
> This patch simply adds it to the Android
On Thu, 4 Jul 2019 at 07:32, Stephen Rothwell wrote:
>
> Hi Alex,
>
> On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote:
> >
> > Go ahead and respin your patch as per the suggestion above. then I
> > can apply it I can either merge hmm into amd's drm-next or we can just
> > provide the
With current master we're seeing build failures with AOSP:
error: undefined symbol: ir3_nir_lower_imul
This is due to the ir3_nir_imul.c file not being generated
in the Android.mk files.
This patch simply adds it to the Android build, after which
thigns build and boot ok on db410c.
Cc: Rob
Building with clang, I'm seeing
u_blitter.h:627:1: error: control may reach end of non-void function
[-Werror,-Wreturn-type]
The util_blitter_get_color_format_for_zs() asserts for any
unhandled types, so we do not expect to reach the end of the
function here.
But provide a dummy return with an
This adds the plumbing for reading panel rotation from the devicetree
and sets up adding a panel property for the panel orientation on
Mediatek SoCs when a rotation is present.
v5 changes:
-rebased
v4 changes:
-fixed some changes made to the i915 driver
-clarified comments on of orientation
Not every platform needs quirk detection for panel orientation, so
split the drm_connector_init_panel_orientation_property into two
functions. One for platforms without the need for quirks, and the
other for platforms that need quirks.
Signed-off-by: Derek Basehore
---
This adds a helper function for reading the rotation (panel
orientation) from the device tree.
Signed-off-by: Derek Basehore
---
drivers/gpu/drm/drm_panel.c | 43 +
include/drm/drm_panel.h | 7 ++
2 files changed, 50 insertions(+)
diff --git
The ti-sn65dsi86 can be configured in two ways - via i2c or "inband" via
DSI. The DSI option can be useful on platforms where the i2c link does
not seem to be wired up.
To support configuration via DSI, register as a DSI device, use the
provided DSI device instead of creating our own, and
The ti-sn65dsi86 bridge on the Lenovo Miix 630 does not appear to be
wired to an I2C bus - there is no indication from the FW which bus to
use and scanning all of the busses does not result in an unknown device
being discovered.
As a result, we must utilize the ability of the ti-sn65dsi86 to be
Hi Felix,
On Wed, 3 Jul 2019 21:03:32 + "Kuehling, Felix"
wrote:
>
> It looks like Stephen already applied my patch as a conflict resolution
> on linux-next, though. I see linux-next/master is getting updated
> non-fast-forward. So is the idea that its history will updated again
> with
Hi Alex,
On Wed, 3 Jul 2019 17:09:16 -0400 Alex Deucher wrote:
>
> Go ahead and respin your patch as per the suggestion above. then I
> can apply it I can either merge hmm into amd's drm-next or we can just
> provide the conflict fix patch whichever is easier. Which hmm branch
> is for 5.3?
>
On Wed, Jul 3, 2019 at 5:03 PM Kuehling, Felix wrote:
>
> On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote:
> > On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote:
> >> From: Philip Yang
> >>
> >> In order to pass mirror instead of mm to hmm_range_register, we need
> >> pass bo
On 2019-07-03 10:10 a.m., Jason Gunthorpe wrote:
> On Wed, Jul 03, 2019 at 01:55:08AM +, Kuehling, Felix wrote:
>> From: Philip Yang
>>
>> In order to pass mirror instead of mm to hmm_range_register, we need
>> pass bo instead of ttm to amdgpu_ttm_tt_get_user_pages because mirror
>> is part
On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
>
> Switch to the virtio_gpu_array_* helper workflow.
(just repeating my question on patch 6)
Does this fix the obj refcount issue? When was the issue introduced?
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_drv.h
On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
>
> Switch to the virtio_gpu_array_* helper workflow.
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/virtio/virtgpu_drv.h | 2 +-
> drivers/gpu/drm/virtio/virtgpu_ioctl.c | 43 --
>
On Wed, Jul 3, 2019 at 11:31 AM Chia-I Wu wrote:
>
> On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
> >
> > Some helper functions to manage an array of gem objects.
> >
> > v6:
> > - add ticket to struct virtio_gpu_object_array.
> > - add virtio_gpu_array_{lock,unlock}_resv helpers.
> >
On Wed, Jul 3, 2019 at 4:32 AM Laura Abbott wrote:
>
> On 7/3/19 5:50 AM, Daniel Vetter wrote:
> > On Wed, Jul 3, 2019 at 10:37 AM Greg KH wrote:
> >>
> >> On Wed, Jul 03, 2019 at 01:48:41PM +0530, Nishka Dasgupta wrote:
> >>> Remove file ion_carveout_heap.c as its functions and definitions are
Den 03.07.2019 10.32, skrev Thomas Zimmermann:
> DRM client buffers are permanently mapped throughout their lifetime. This
> prevents us from using generic framebuffer emulation for devices with
> small dedicated video memory, such as ast or mgag200. With fb buffers
> permanently mapped, such
On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
>
> Rework fencing workflow, starting with virtio_gpu_execbuffer_ioctl.
> Stop using ttm helpers, use the virtio_gpu_array_* helpers (which work
> on the reservation objects directly) instead.
>
> New workflow:
>
> (1) All gem objects needed by
You can run:
AMD_DEBUG=testdmaperf glxgears
It tests transfer sizes of up to 128 MB, and it tests ~60 slightly
different methods of transfering data.
Marek
On Wed, Jul 3, 2019 at 4:07 AM Michel Dänzer wrote:
> On 2019-07-02 11:49 a.m., Timur Kristóf wrote:
> > On Tue, 2019-07-02 at 10:09
On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
>
> Some helper functions to manage an array of gem objects.
>
> v6:
> - add ticket to struct virtio_gpu_object_array.
> - add virtio_gpu_array_{lock,unlock}_resv helpers.
> - add virtio_gpu_array_add_fence helper.
> v5: some small
On Tue, Jul 2, 2019 at 7:19 AM Gerd Hoffmann wrote:
>
> Call reservation_object_* directly instead
> of using ttm_bo_{reserve,unreserve}.
>
> v4: check for EINTR only.
> v3: check for EINTR too.
>
> Signed-off-by: Gerd Hoffmann
> Reviewed-by: Daniel Vetter
> ---
>
On Wed, 3 Jul 2019 at 19:41, Rob Clark wrote:
>
> On Wed, Jul 3, 2019 at 9:33 AM Leif Lindholm wrote:
> >
> > On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > > > There is one kernel, and there
> > > > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > >
https://bugs.freedesktop.org/show_bug.cgi?id=106224
LunarG changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
On Wed, Jul 3, 2019 at 1:49 PM Ralph Campbell wrote:
> On 6/30/19 11:20 PM, Christoph Hellwig wrote:
> > hmm_vma_fault is marked as a legacy API to get rid of, but quite suites
> > the current nouvea flow. Move it to the only user in preparation for
>
> I didn't quite parse the phrase "quite
On Wed, Jul 3, 2019 at 9:33 AM Leif Lindholm wrote:
>
> On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > > There is one kernel, and there
> > > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > > problem because their distro missed some shim patch really
https://bugs.freedesktop.org/show_bug.cgi?id=110113
--- Comment #1 from ludo.sur...@gmail.com ---
Hello,
Juste to say i have the same bug and we both have gigabyte Gaming OC Vega.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109524
--- Comment #6 from laszlo.erd...@freenet.de ---
(In reply to Ilia Mirkin from comment #5)
> Is there like a wine test or something of the sort that can be used to
> reproduce this? I have such a GPU plugged in I can test with, but I need a
>
From: Emil Velikov
There are cases (in mesa and applications) where one would open the
primary node without properly authenticating the client.
Sometimes we don't check if the authentication succeeds, but there's
also cases we simply forget to do it.
The former was a case for Mesa where it did
https://bugs.freedesktop.org/show_bug.cgi?id=109524
--- Comment #5 from Ilia Mirkin ---
NV05 and NV11 don't support GLSL at all. Some entry point must not be
preventing it properly... perhaps something internal.
Is there like a wine test or something of the sort that can be used to
reproduce
https://bugs.freedesktop.org/show_bug.cgi?id=109524
--- Comment #4 from laszlo.erd...@freenet.de ---
Other applications using OpenGL (and so mesa, I guess?) still seem to work
--
You are receiving this mail because:
You are the assignee for the
On Tue, Jul 02, 2019 at 03:48:48PM -0700, Rob Clark wrote:
> > > There is one kernel, and there
> > > are N distro's, so debugging a users "I don't get a screen at boot"
> > > problem because their distro missed some shim patch really just
> > > doesn't seem like a headache I want to have.
> >
> >
Am 03.07.2019 18:27 schrieb Fuqian Huang :
kmemdup is introduced to duplicate a region of memory in a neat way.
Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
write the size twice (sometimes lead to mistakes), kmemdup improves
readability, leads to smaller code and also
On Wed, Jul 03, 2019 at 07:32:27AM -0400, Laura Abbott wrote:
> On 7/3/19 5:50 AM, Daniel Vetter wrote:
> > On Wed, Jul 3, 2019 at 10:37 AM Greg KH wrote:
> > >
> > > On Wed, Jul 03, 2019 at 01:48:41PM +0530, Nishka Dasgupta wrote:
> > > > Remove file ion_carveout_heap.c as its functions and
On Wed, Jul 3, 2019 at 6:11 PM Steven Price wrote:
>
> On 03/07/2019 15:33, Boris Brezillon wrote:
> > On Wed, 3 Jul 2019 15:13:25 +0100
> > Steven Price wrote:
> >
> >> On 03/07/2019 14:56, Boris Brezillon wrote:
> >>> On Wed, 3 Jul 2019 07:45:32 -0600
> >>> Rob Herring wrote:
> >>>
> On
On Wed, Jul 3, 2019 at 5:59 PM Liviu Dudau wrote:
>
> On Wed, Jul 03, 2019 at 05:21:20PM +0200, Daniel Vetter wrote:
> > On Wed, Jul 03, 2019 at 04:03:30PM +0100, Liviu Dudau wrote:
> > > drm_debugfs_crtc_crc_add() function checks that both .set_crc_source and
> > > .verify_crc_source hooks are
On Wed, Jul 3, 2019 at 8:13 AM Steven Price wrote:
>
> On 03/07/2019 14:56, Boris Brezillon wrote:
> > On Wed, 3 Jul 2019 07:45:32 -0600
> > Rob Herring wrote:
> >
> >> On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
> >> wrote:
> >>>
> >>> Exported BOs might be imported back, then mmap()-ed to
On Wed, Jul 03, 2019 at 05:47:24PM +0200, Daniel Vetter wrote:
> On Wed, Jul 03, 2019 at 07:45:32AM -0600, Rob Herring wrote:
> > On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
> > wrote:
> > >
> > > Exported BOs might be imported back, then mmap()-ed to be written
> > > too. Most drivers handle
On Wed, Jul 03, 2019 at 07:45:32AM -0600, Rob Herring wrote:
> On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
> wrote:
> >
> > Exported BOs might be imported back, then mmap()-ed to be written
> > too. Most drivers handle that by mmap()-ing the GEM handle after it's
> > been imported, but,
/commits/Derek-Basehore/Panel-rotation-patches/20190703-172146
config: s390-debug_defconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.4.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
/commits/Derek-Basehore/Panel-rotation-patches/20190703-172146
config: i386-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported
On Wed, Jul 03, 2019 at 04:03:30PM +0100, Liviu Dudau wrote:
> drm_debugfs_crtc_crc_add() function checks that both .set_crc_source and
> .verify_crc_source hooks are provided before enabling debugfs support for
> reading per-frame CRC data. Make that explicit in the documentation.
>
> Cc: Daniel
On Wed, 3 Jul 2019 at 14:15, Fuqian Huang wrote:
>
> kmemdup is introduced to duplicate a region of memory in a neat way.
> Rather than kmalloc/kzalloc + memset, which the programmer needs to
> write the size twice (sometimes lead to mistakes), kmemdup improves
> readability, leads to smaller
On Wed, 3 Jul 2019 at 15:58, Koenig, Christian wrote:
> Am 03.07.2019 16:51 schrieb Emil Velikov :
>
> On Wed, 3 Jul 2019 at 15:33, Koenig, Christian
> wrote:
> > Am 03.07.2019 16:00 schrieb Emil Velikov :
> >
> > On Wed, 3 Jul 2019 at 14:48, Koenig, Christian
> > wrote:
> > >
> > > Well this
On Wed, 3 Jul 2019 15:50:08 +0100
Steven Price wrote:
> On 03/07/2019 15:33, Boris Brezillon wrote:
> > On Wed, 3 Jul 2019 15:13:25 +0100
> > Steven Price wrote:
> >
> >> On 03/07/2019 14:56, Boris Brezillon wrote:
> >>> On Wed, 3 Jul 2019 07:45:32 -0600
> >>> Rob Herring wrote:
> >>>
drm_debugfs_crtc_crc_add() function checks that both .set_crc_source and
.verify_crc_source hooks are provided before enabling debugfs support for
reading per-frame CRC data. Make that explicit in the documentation.
Cc: Daniel Vetter
Signed-off-by: Liviu Dudau
---
On 7/3/19 10:53 AM, Lucas Stach wrote:
> Am Mittwoch, den 03.07.2019, 14:41 + schrieb Grodzovsky, Andrey:
>> On 7/3/19 10:32 AM, Lucas Stach wrote:
>>> Am Mittwoch, den 03.07.2019, 14:23 + schrieb Grodzovsky, Andrey:
On 7/3/19 6:28 AM, Lucas Stach wrote:
>
Am 03.07.2019 16:51 schrieb Emil Velikov :
On Wed, 3 Jul 2019 at 15:33, Koenig, Christian wrote:
> Am 03.07.2019 16:00 schrieb Emil Velikov :
>
> On Wed, 3 Jul 2019 at 14:48, Koenig, Christian
> wrote:
> >
> > Well this is still a NAK.
> >
> > As stated previously please just don't remove
Am Mittwoch, den 03.07.2019, 14:41 + schrieb Grodzovsky, Andrey:
> On 7/3/19 10:32 AM, Lucas Stach wrote:
> > Am Mittwoch, den 03.07.2019, 14:23 + schrieb Grodzovsky, Andrey:
> > > On 7/3/19 6:28 AM, Lucas Stach wrote:
> > > > drm_sched_entity_kill_jobs_cb() is called right from the last
On Wed, 3 Jul 2019 at 15:33, Koenig, Christian wrote:
> Am 03.07.2019 16:00 schrieb Emil Velikov :
>
> On Wed, 3 Jul 2019 at 14:48, Koenig, Christian
> wrote:
> >
> > Well this is still a NAK.
> >
> > As stated previously please just don't remove DRM_AUTH and keep the
> > functionality as it
On 7/3/19 10:32 AM, Lucas Stach wrote:
> Am Mittwoch, den 03.07.2019, 14:23 + schrieb Grodzovsky, Andrey:
>> On 7/3/19 6:28 AM, Lucas Stach wrote:
>>> drm_sched_entity_kill_jobs_cb() is called right from the last scheduled
>>> job finished fence signaling. As this might happen from IRQ
On Wed, 3 Jul 2019 15:13:25 +0100
Steven Price wrote:
> On 03/07/2019 14:56, Boris Brezillon wrote:
> > On Wed, 3 Jul 2019 07:45:32 -0600
> > Rob Herring wrote:
> >
> >> On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
> >> wrote:
> >>>
> >>> Exported BOs might be imported back, then
Am 03.07.2019 16:00 schrieb Emil Velikov :
On Wed, 3 Jul 2019 at 14:48, Koenig, Christian wrote:
>
> Well this is still a NAK.
>
> As stated previously please just don't remove DRM_AUTH and keep the
> functionality as it is.
>
AFAICT nobody was in favour of your suggestion to remove DRM_AUTH
Am Mittwoch, den 03.07.2019, 14:23 + schrieb Grodzovsky, Andrey:
> On 7/3/19 6:28 AM, Lucas Stach wrote:
> > drm_sched_entity_kill_jobs_cb() is called right from the last scheduled
> > job finished fence signaling. As this might happen from IRQ context we
> > now end up calling the GPU driver
Den 03.07.2019 10.33, skrev Thomas Zimmermann:
> This patch replaces mgag200's framebuffer console with DRM's generic
> implememtation. All respective code is being removed from the driver.
>
> The console is set up with a shadow buffer. The actual buffer object is
> not permanently pinned in
Den 03.07.2019 10.33, skrev Thomas Zimmermann:
> The bochs driver (and virtual hardware) requires buffer objects to
> reside in video ram to display them to the screen. So it can not
> display the framebuffer console because the respective buffer object
> is permanently pinned in system memory.
Den 03.07.2019 10.33, skrev Thomas Zimmermann:
> This patch replaces ast's framebuffer console with DRM's generic
> implememtation. All respective code is being removed from the driver.
>
> The console is set up with a shadow buffer. The actual buffer object is
> not permanently pinned in video
On Wed, Jul 3, 2019 at 5:42 AM Robin Murphy wrote:
>
> On 02/07/2019 21:26, Rob Clark wrote:
> > From: Rob Clark
> >
> > Avoid attaching any non-driver managed domain if the driver indicates
> > that it manages the iommu directly.
> >
> > This solves a couple problems that drm/msm + arm-smmu has
From: Rob Clark
For platforms that require the "zap shader" to take the GPU out of
secure mode at boot, we also need the zap fw to end up in the initrd.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/adreno/adreno_device.c | 4
1 file changed, 4 insertions(+)
diff --git
On Wed, 3 Jul 2019 at 14:48, Koenig, Christian wrote:
>
> Well this is still a NAK.
>
> As stated previously please just don't remove DRM_AUTH and keep the
> functionality as it is.
>
AFAICT nobody was in favour of your suggestion to remove DRM_AUTH from
the handle to/from fd ioclts.
Thus this
On Wed, 3 Jul 2019 07:45:32 -0600
Rob Herring wrote:
> On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
> wrote:
> >
> > Exported BOs might be imported back, then mmap()-ed to be written
> > too. Most drivers handle that by mmap()-ing the GEM handle after it's
> > been imported, but, according to
Well this is still a NAK.
As stated previously please just don't remove DRM_AUTH and keep the
functionality as it is.
I absolutely don't see the point to add a new flag to remove the same
functionality a different flag provides.
Christian.
Am 03.07.2019 15:30 schrieb Emil Velikov :
From:
On Wed, Jul 3, 2019 at 7:34 AM Boris Brezillon
wrote:
>
> Exported BOs might be imported back, then mmap()-ed to be written
> too. Most drivers handle that by mmap()-ing the GEM handle after it's
> been imported, but, according to [1], this is illegal.
It's not illegal, but is supposed to go
On Wed, 3 Jul 2019 at 09:19, Vasilev, Oleg wrote:
>
> On Tue, 2019-07-02 at 14:38 +0100, Emil Velikov wrote:
> > Hi Oleg,
> >
> > On Mon, 1 Jul 2019 at 09:00, Oleg Vasilev
> > wrote:
> > > Currently, downstream port type is only reported in debugfs. This
> > > information should be considered
Exported BOs might be imported back, then mmap()-ed to be written
too. Most drivers handle that by mmap()-ing the GEM handle after it's
been imported, but, according to [1], this is illegal. The panfrost
driver has recently switched to this generic helper (which was renamed
into
From: Emil Velikov
With earlier commits we've removed DRM_AUTH for driver ioctls annotated
with DRM_AUTH | DRM_RENDER_ALLOW, as the protection it introduces is
effectively not existent.
With next commit, we'll effectively do the same for DRM core.
Yet the AMD developers have voiced concerns
From: Emil Velikov
There are cases (in mesa and applications) where one would open the
primary node without properly authenticating the client.
Sometimes we don't check if the authentication succeeds, but there's
also cases we simply forget to do it.
The former was a case for Mesa where it did
From: Emil Velikov
With later commit we'll rework DRM core authentication handling.
Namely unauthenticated master will be allowed with, DRM_AUTH ioctls.
Since vmwgfx does additional master locking and DRM_AUTH handling, this
will not matter almost all cases.
The only exception being using the
1 - 100 of 151 matches
Mail list logo
