Add missing include in ipu-cpmem and ipu-ic, select
BITREVERSE for ipu-cpmem and GENERIC_ALLOCATOR for ipu-pre, and allow
to build if COMPILE_TEST is enabled.
Signed-off-by: Philipp Zabel
---
drivers/gpu/ipu-v3/Kconfig | 4 +++-
drivers/gpu/ipu-v3/ipu-cpmem.c | 1 +
On 19/12/17 11:05, Daniel Vetter wrote:
> On Mon, Dec 18, 2017 at 08:50:46AM +0100, Maxime Ripard wrote:
>> Hi,
>>
>> On Fri, Dec 15, 2017 at 06:06:32PM +0100, Daniel Vetter wrote:
>>> On Fri, Dec 15, 2017 at 05:46:19PM +0100, Hans Verkuil wrote:
When I connected my cubieboard running
On Tue, Dec 19, 2017 at 09:30:12PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> The vk cts test:
> dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
>
> triggers a lot of
> VFS: Close: file count is 0
>
> This patch fixes it, but I'm guessing
On Thu, Dec 14, 2017 at 04:36:49PM +0100, Max Staudt wrote:
> On 12/13/2017 10:35 PM, Daniel Vetter wrote:
> > Using drm directly would allow you to flush the contents without the fake
> > (and tbh, really expensive on most drivers) copy op. If you insist on
> > using fbdev for this stuff, then at
https://bugs.freedesktop.org/show_bug.cgi?id=103791
--- Comment #19 from denisgolo...@yandex.ru ---
Still better to have a proper fix first as New Year present to us (poor users)
;)
--
You are receiving this mail because:
You are the assignee for the
Quoting Dave Airlie (2017-12-19 11:30:12)
> From: Dave Airlie
>
> The vk cts test:
> dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
>
> triggers a lot of
> VFS: Close: file count is 0
>
> This patch fixes it, but I'm guessing it's racy and someone
On Tue, Dec 19, 2017 at 12:07:00PM +, Chris Wilson wrote:
> The vk cts test:
> dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
>
> triggers a lot of
> VFS: Close: file count is 0
>
> Dave pointed out that clearing the syncobj->file from
> drm_syncobj_file_release()
From: Dave Airlie
The vk cts test:
dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
triggers a lot of
VFS: Close: file count is 0
This patch fixes it, but I'm guessing it's racy and someone will
smell rcu, but I just wanted to send out the proof of
The vk cts test:
dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
triggers a lot of
VFS: Close: file count is 0
Dave pointed out that clearing the syncobj->file from
drm_syncobj_file_release() was sufficient to silence the test, but that
opens a can of worm since we
Hi Neil,
On Tuesday, 19 December 2017 11:00:28 EET Neil Armstrong wrote:
> On 17/12/2017 01:17, Laurent Pinchart wrote:
> > Color keying is the action of replacing pixels matching a given color
> > (or range of colors) with transparent pixels in an overlay when
> > performing blitting. Depending
On 12/19/2017 01:23 PM, Daniel Vetter wrote:
> On Thu, Dec 14, 2017 at 04:36:49PM +0100, Max Staudt wrote:
>> 2) We need to go out of the way when a graphical application starts, and
>> come back when it's done. fbcon already has the logic for this, and
>> fbcon is also the thing we're trying to
On Tue, Dec 19, 2017 at 03:33:57PM +0200, Laurent Pinchart wrote:
> On Tuesday, 19 December 2017 12:03:55 EET Daniel Vetter wrote:
> > On Mon, Dec 18, 2017 at 06:13:46PM +0200, Laurent Pinchart wrote:
> > > On Thursday, 14 December 2017 22:30:53 EET Daniel Vetter wrote:
> > >> + * Drivers are
Dear Fabio,
On 12/18/2017 02:02 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> devm_ioremap_resource() already checks if the resource is NULL, so
> remove the unnecessary platform_get_resource() error check.
>
> Cc: Archit Taneja
>
Am 19.12.2017 um 11:39 schrieb Michel Dänzer:
On 2017-12-19 11:37 AM, Michel Dänzer wrote:
On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
On 12/18/17 7:06 PM, Mike Galbraith wrote:
Greetings,
Kernel bound workloads seem to trigger the below for whatever reason.
I only see this when
Hi Daniel,
On Tuesday, 19 December 2017 12:03:55 EET Daniel Vetter wrote:
> On Mon, Dec 18, 2017 at 06:13:46PM +0200, Laurent Pinchart wrote:
> > On Thursday, 14 December 2017 22:30:53 EET Daniel Vetter wrote:
> >> DK put some nice docs into the commit introducing driver private
> >> state, but
On Tue, Dec 19, 2017 at 02:34:22PM +0100, Max Staudt wrote:
> On 12/19/2017 01:23 PM, Daniel Vetter wrote:
> > On Thu, Dec 14, 2017 at 04:36:49PM +0100, Max Staudt wrote:
> >> 2) We need to go out of the way when a graphical application starts, and
> >> come back when it's done. fbcon already has
Dear Fabio,
On 12/18/2017 02:02 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> devm_ioremap_resource() already checks if the resource is NULL, so
> remove the unnecessary platform_get_resource() error check.
>
> Cc: Philippe Cornu
>
2017-12-19 15:14 GMT+01:00 Philippe CORNU :
> Dear Fabio,
>
> On 12/18/2017 02:02 PM, Fabio Estevam wrote:
>> From: Fabio Estevam
>>
>> devm_ioremap_resource() already checks if the resource is NULL, so
>> remove the unnecessary
https://bugs.freedesktop.org/show_bug.cgi?id=104289
--- Comment #4 from Christian König ---
You can restrict that to changes to drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c.
The problem is that we use more dw than expected for clearing the page tables.
No idea what
Hi Daniel,
On Tuesday, 19 December 2017 16:00:36 EET Daniel Vetter wrote:
> On Tue, Dec 19, 2017 at 03:33:57PM +0200, Laurent Pinchart wrote:
> > On Tuesday, 19 December 2017 12:03:55 EET Daniel Vetter wrote:
> > > On Mon, Dec 18, 2017 at 06:13:46PM +0200, Laurent Pinchart wrote:
> > > > On
Hi Fabio,
On 12/18/2017 02:02 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> devm_ioremap_resource() already checks if the resource is NULL, so
> remove the unnecessary platform_get_resource() error check.
>
> Cc: Philippe Cornu
>
2017-12-19 15:15 GMT+01:00 Philippe CORNU :
> Hi Fabio,
>
>
> On 12/18/2017 02:02 PM, Fabio Estevam wrote:
>> From: Fabio Estevam
>>
>> devm_ioremap_resource() already checks if the resource is NULL, so
>> remove the unnecessary
On Tue, Dec 19, 2017 at 4:41 PM, Max Staudt wrote:
> On 12/19/2017 02:57 PM, Daniel Vetter wrote:
>> Where do drivers deal with struct file deep down?
>
> As an example, I remembered this to be the case in nouveau's code for
> allocating a framebuffer. So I checked, and it's
btw the reason drmcon didn't move is that David Herrmann moved on from
hacking on graphics stuff, and no one needs it. There's nothing
fundamentally wrong with his patches for a basic emergency console on
plain drm, or the simpledrm driver to get a basic drm framebuffer up
on vesafb/efifb and
https://bugs.freedesktop.org/show_bug.cgi?id=101900
Sandro changed:
What|Removed |Added
CC|
On 12/19/2017 02:57 PM, Daniel Vetter wrote:
> Where do drivers deal with struct file deep down?
As an example, I remembered this to be the case in nouveau's code for
allocating a framebuffer. So I checked, and it's much better now.
So I was mistaken about this - sorry.
Thanks a lot for
https://bugs.freedesktop.org/show_bug.cgi?id=104194
--- Comment #2 from Jerry Zuo ---
(In reply to laichiaheng from comment #1)
> I've found a solution to make it work, just re-plug-in the HDMI cable from
> the GPU side (not the screen side)
I've checked the top of the
On Wed, Dec 13, 2017 at 08:47:42PM +0100, Max Staudt wrote:
> Dear fbdev and fbcon developers,
>
> Thank you very much for your input for the first patch series.
>
> I've included your feedback into this second roll, and kindly ask for
> your opinion on the new patch series.
Ok I've realized
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #13 from Andreas Brogle (an...@ok.de) ---
Hello,
here is the complete bisection process. Testing needs about a week.
All versions 4.10.0-rc1 lead to a kernel panic. So there are 60 commits that
have to be SKIPped.
git bisect start
On 12/19/2017 05:16 PM, Daniel Vetter wrote:
> On Wed, Dec 13, 2017 at 08:47:42PM +0100, Max Staudt wrote:
>> Dear fbdev and fbcon developers,
>>
>> Thank you very much for your input for the first patch series.
>>
>> I've included your feedback into this second roll, and kindly ask for
>> your
On 12/19/2017 05:02 PM, Daniel Vetter wrote:
> On Tue, Dec 19, 2017 at 4:41 PM, Max Staudt wrote:
>> On 12/19/2017 02:57 PM, Daniel Vetter wrote:
>>> The problem is that defio is totally not how a real driver works.
>>
>> But they do exist and I can't ignore them.
>>
>> I'm
On 12/19/2017 05:09 PM, Daniel Vetter wrote:
> btw the reason drmcon didn't move is that David Herrmann moved on from
> hacking on graphics stuff, and no one needs it. There's nothing
> fundamentally wrong with his patches for a basic emergency console on
> plain drm, or the simpledrm driver to
On Tue, Dec 19, 2017 at 6:04 PM, Max Staudt wrote:
> On 12/19/2017 05:16 PM, Daniel Vetter wrote:
>> On Wed, Dec 13, 2017 at 08:47:42PM +0100, Max Staudt wrote:
>>> Dear fbdev and fbcon developers,
>>>
>>> Thank you very much for your input for the first patch series.
>>>
>>>
On Tue, 19 Dec 2017, Joe Perches wrote:
> drivers/gpu/drm/i915/i915_sysfs.c | 12 ++--
For i915,
Acked-by: Jani Nikula
--
Jani Nikula, Intel Open Source Technology Center
___
dri-devel
Hi,
On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote:
> I'm hooking into the in-kernel terminal emulator, because the bootsplash is a
> functional extension of that. It just happens that fbcon sits on top of FB,
> so I
> work with what I get.
>
> And the console in turn
https://bugs.freedesktop.org/show_bug.cgi?id=104331
--- Comment #4 from MWATTT ---
Created attachment 136303
--> https://bugs.freedesktop.org/attachment.cgi?id=136303=edit
Right texture
--
You are receiving this mail because:
You are the assignee for the
On Tue, 2017-12-19 at 13:41 -0800, Rodrigo Vivi wrote:
> On Tue, Dec 19, 2017 at 05:26:58AM +, Dhinakaran Pandiyan wrote:
> > When DC states are enabled and PSR is active, the hardware enters DC5/DC6
> > states resulting in frame counter resets. The frame counter resets mess
> > up the
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #15 from Andreas Brogle (an...@ok.de) ---
Hmm, seems like a lucky punch to mee. No chance if the two commits would have
been vice versa ;-)
# skip: [d939cdfde34f50b95254b375f498447c82190b3e] md/linear: shutup lockdep
warnning
git
https://bugs.freedesktop.org/show_bug.cgi?id=104331
--- Comment #2 from MWATTT ---
I can confirm that the segfault is gone.
However, the demo does not render properly(I don't know if I should make
another report for that).
I'll upload an other trace, as the first one was
On Tue, 2017-12-19 at 13:29 -0800, Rodrigo Vivi wrote:
> On Tue, Dec 19, 2017 at 05:26:54AM +, Dhinakaran Pandiyan wrote:
> > DPCD read for the eDP is complete by the time intel_psr_init() is
> > called, which means we can avoid initializing PSR structures and state
> > if there is no sink
Upload of intial version of hyper_DMABUF driver enabling
DMA_BUF exchange between two different VMs in virtualized
platform based on hypervisor such as KVM or XEN.
Hyper_DMABUF drv's primary role is to import a DMA_BUF
from originator then re-export it to another Linux VM
so that it can be mapped
High-level description of hyper_dmabuf driver has been added
to "Documentation" directory.
Signed-off-by: Dongwon Kim
---
Documentation/hyper-dmabuf-sharing.txt | 734 +
1 file changed, 734 insertions(+)
create mode 100644
Need a new index, k in hyper_dmabuf_extract_pgs function for
picking up a correct n-th page in contigous memory space.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_imp.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
Now we re-use dma_buf instead of exporting it via normal process
(including new mappings). For this, hyper_dmabuf list entries can
be searched with "struct dma_buf*". Also, ioctl (export_remote) is
modified to just return hyper_dmabuf_id if the specific dmabuf
has already been exported to the
Use workqueue mechanism to delay message parsing done
after exiting from ISR to reduce ISR execution time.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.c| 13 ++
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.h| 5 +
Importer now sends a synchronization request to the
exporter when any of DMA_BUF operations on imported
Hyper_DMABUF is executed (e.g dma_buf_map and dma_buf_unmap).
This results in a creation of shadow DMA_BUF and exactly same
DMA_BUF operation to be executed on it.
The main purpose of this is
hyper_dmabuf_importer_ring_setup creates new channel only if
there is no existing downstream communication channel previously
created for the exporter VM.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_imp.c | 13 +++--
On Tue, Dec 19, 2017 at 05:26:52AM +, Dhinakaran Pandiyan wrote:
> This flag has become redundant since
> commit 4d90f2d507ab ("drm/i915: Start tracking PSR state in crtc state")
> It is set at the same place as psr.enabled, which is also exposed via
> debugfs.
>
> Cc: Rodrigo Vivi
On Tue, Dec 19, 2017 at 05:26:53AM +, Dhinakaran Pandiyan wrote:
> The global variable dev_priv->psr.sink_support is set if an eDP sink
> supports PSR. Use this instead of redoing the check with is_edp_psr().
> Combine source and sink support checks into a macro that can be used to
> return
On Tue, Dec 19, 2017 at 05:26:58AM +, Dhinakaran Pandiyan wrote:
> When DC states are enabled and PSR is active, the hardware enters DC5/DC6
> states resulting in frame counter resets. The frame counter resets mess
> up the vblank counting logic. In order to disable DC states when
> vblank
I forgot to include this brief information about this patch series.
This patch series contains the implementation of a new device driver,
hyper_dmabuf, which provides a method for DMA-BUF sharing across
different OSes running on the same virtual OS platform powered by
a hypervisor.
Detailed
https://bugs.freedesktop.org/show_bug.cgi?id=104331
MWATTT changed:
What|Removed |Added
Attachment #136265|0 |1
is obsolete|
On Tue, Dec 19, 2017 at 05:26:54AM +, Dhinakaran Pandiyan wrote:
> DPCD read for the eDP is complete by the time intel_psr_init() is
> called, which means we can avoid initializing PSR structures and state
> if there is no sink support.
>
> Cc: Rodrigo Vivi
> Cc:
On 06/12/17 17:18, Jon Hunter wrote:
>
> On 06/12/17 09:22, Guillaume Tucker wrote:
>> On 05/12/17 18:32, Ben Skeggs wrote:
>>> On Wed, Dec 6, 2017 at 12:30 AM, Jon Hunter wrote:
>>>
On 04/12/17 18:37, Guillaume Tucker wrote:
> If the firmware fails to load
https://bugs.freedesktop.org/show_bug.cgi?id=104306
--- Comment #2 from eric vz ---
Working on narrowing down the source of the issue, I've found so far that
17.2.7 builds work fine (though I had to change --enable-omx-bellagio back to
--enable-omx), and
On Sun, Dec 17, 2017 at 03:34:33AM +0100, Jonathan Neuschäfer wrote:
> The compatible string for this panel was specified as
> toshiba,lt089ac29000.txt. I believe this is a mistake.
>
> Fixes: 06e733e41f87 ("drm/panel: simple: add Toshiba LT089AC19000")
> Cc: Lucas Stach
Adding ID check to make sure a dma-buf is exported externally
since hyper_dmabuf only allows to export a dmabuf to a different
VM.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
sgt_info->priv will be used to store user private info passed in
ioctl. Data in sgt_info->priv is transfered via comm channel to
the importer VM whenever DMA_BUF is exported to keep the private
data synchroized across VMs.
This patch also adds hyper_dmabuf_send_export_msg that replaces
some of
Removed prefix "hyper_dmabuf" from backend functions and static func
(except for driver APIs) and add 'be' after 'xen' in backend function
calls to show those are backend APIs.
Also, modified some of function names for clarification and addressed
some missing errors and warnings in
Re-orginized source code for more intuitive structure
For this,
1. driver's file operations other than ioctls have been moved to
hyper_dmabuf_drv.c.
2. Separated out dma-buf operations from hyper_dmabuf_ops.c
and put those in a new file, 'hyper_dmabuf_ops.c'. Remaining part
(SGT core
Make sure to free buffers before returning to prevent memory leaks
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c | 19 +++-
drivers/xen/hyper_dmabuf/hyper_dmabuf_msg.c| 9 +++-
drivers/xen/hyper_dmabuf/hyper_dmabuf_ops.c
From: Mateusz Polrola
Extending DMA bitmask of hyper_dmabuf device to cover whole
address space driver may access.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_ioctl.c | 2 +-
1 file changed, 1 insertion(+), 1
From: Mateusz Polrola
It is needed to freeing already-mapped pages if it gets error
before finishing mapping all pages.
Signed-off-by: Dongwon Kim
---
.../xen/hyper_dmabuf/xen/hyper_dmabuf_xen_shm.c| 43 +++---
1 file
From: Mateusz Polrola
Introduced additional init and cleanup routines in the backend
API structure that might be useful for hypervisors other than Xen.
Signed-off-by: Mateusz Polrola
Signed-off-by: Dongwon Kim
---
From: Mateusz Polrola
This change adds two query items, 'HYPER_DMABUF_QUERY_PRIV_INFO_SIZE'
and 'HYPER_DMABUF_QUERY_PRIV_INFO', for retrieving buffer's private
info and its size.
'info' is an address of user-space buffer (user application provides
this) ,where
On Tue, Dec 19, 2017 at 8:15 PM, Joe Perches wrote:
> Convert DEVICE_ATTR uses to DEVICE_ATTR_RW where possible.
>
> Done with perl script:
>
> $ git grep -w --name-only DEVICE_ATTR | \
> xargs perl -i -e 'local $/; while (<>) {
>
This looks okay to me.
On Mon, Dec 18, 2017 at 07:26:03PM -0500, Woody Suwalski wrote:
> The 4.15 drm_atomic_helper driver shows a warning during boot (both 32 and
> 64 bit x86)
> It is caused by a mismatch between the result of vmw_enable_vblank() and
> what the drm_atomic_helper expects:
>
Hi,
On 19-12-17 20:42, Rodrigo Vivi wrote:
On Tue, Dec 19, 2017 at 07:21:13PM +, Hans de Goede wrote:
At least on the Chuwi Vi8 (non pro/plus) the LCD panel will show an image
shifted aprox. 20% to the left (with wraparound) and sometimes also wrong
colors, showing that the panel
For adoption of hyper_dmabuf driver to various hypervisors
other than Xen, a "backend" layer is defined and separated out
from existing one-body structure.
"Backend" is basically a list of entry points of function calls
that provides method to do Kernel's page-level sharing and inter
VMs
From: Mateusz Polrola
If shared pages of buffer were already mapped on importer side, do
not map them again on next request to export fd.
Signed-off-by: Mateusz Polrola
Signed-off-by: Dongwon Kim
---
From: Mateusz Polrola
In hyper_dmabuf_export_remote, page_info->pages needs to
be freed before freeing page_info.
Also, info_entry in hyper_dmabuf_remove_exported/imported
and hyper_dmabuf_remove_exporter/importer_ring needs to
be freed after removal of an entry.
From: Mateusz Polrola
Immediate clean up of buffer is not possible if the buffer is
actively used by importer. In this case, we need to postpone
freeing hyper_DMABUF until the last consumer unmaps and releases
the buffer on impoter VM. New reference count is added for
Now, released hyper_dmabuf_ids are stored in a stack -
(hyper_dmabuf_private.id_queue) for reuse. This is to prevent
overflow of ids for buffers. We also limit maximum number for
the id to 1000 for the stability and optimal performance.
Signed-off-by: Dongwon Kim
---
From: Michał Janiszewski
This adds two entries in SYSFS with information about imported
and exported entries. The information exposed contains details
about number of pages, whether a buffer is valid or not, and
importer/exporter count.
Sysfs for hyper_dmabuf can
Now relaese funcs checks f_count for the file instead of
our own refcount because it can't track dma_buf_get.
Also, importer now sends out HYPER_DMABUF_FIRST_EXPORT
to let the exporter know corresponding dma-buf has ever
exported on importer's side. This is to cover the case
where exporter
unexporting on exporter's side now have two options, one is
, that just remove and free everything to literally "disconnect"
from importer, the other is just to return fail if any apps
running on importer is still attached or DMAing. Currently whether
forcing or unforcing it is determined by how
From: Mateusz Polrola
This introduces use of xenstore for creating and managing
communication channels between two VMs in the system.
When hyper_dmabuf driver is loaded in the service VM (host OS),
a new xenstore directory, "/local/domain//data/hyper_dmabuf"
is
From: Mateusz Polrola
Replaces printk to debug macros
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.c| 4 +-
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.h| 4 ++
hyper_dmabuf driver on importing domain now generates event
every time new hyper_dmabuf is available (visible) to the
importer.
Each event comes with 128 byte private data, which can
contain any meta data or user data specific to the originator
of DMA BUF.
Signed-off-by: Dongwon Kim
Added missing mutex_unlock to make sure mutex is unlocked
before returning.
Also, moved spinlock lock/unlock into hyper_dmabuf_send_event
and remove checking on spinlock (with assumption caller does
the spinlock in advance) to make it more straight forward.
This patch includes a couple of minor
From: Mateusz Polrola
hyper_dmabuf driver is generic driver that is designed to work
with any hypervisor with various backend implementations. So
moving out its device node out of /dev/xen.
Signed-off-by: Mateusz Polrola
Signed-off-by:
To make hyper_dmabuf_export_remote_ioctl more compact and readable,
a new function call, 'fastpath_export' is created to replace a routine
in hyper_dmabuf_export_remote_ioctl for the case requested buffer for
exporting is already in the LIST (exported previously).
Signed-off-by: Dongwon Kim
This patch fixes several defects on event handling
including:
1. Imported sgt info and exported sgt info now have
buffer for private data (priv) with variable size
2. Now user input to export_remote_ioctl contain sz_priv,
which specifies size of private data (e.g. meta data)
3. Increased
To make type's name compact, *_backend_ops is changed to '*_bknd_ops'. Also
'ops' is now changed to 'bknd_ops' to clarify it is a data structure with
entry points of 'backend' operations.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.c|
From: Mateusz Polrola
Wrong vmid is used in case of sending HYPER_DMABUF_EXPORT_FD_FAILED
message. Instead of vmid, hypder dmabuf id is being used.
Signed-off-by: Mateusz Polrola
Signed-off-by: Dongwon Kim
---
Hi,
On 19-12-17 20:48, Ville Syrjälä wrote:
On Tue, Dec 19, 2017 at 08:31:07PM +0100, Hans de Goede wrote:
Hi,
I forgot to add a coverletter, anyways what I wanted to put in the
coverletter and not in the commit message is a link to a picture of the
problem this fixes:
Joe Perches (4):
sysfs.h: Use octal permissions
treewide: Use DEVICE_ATTR_RW
treewide: Use DEVICE_ATTR_RO
treewide: Use DEVICE_ATTR_WO
arch/arm/mach-pxa/sharpsl_pm.c | 4 +-
arch/s390/kernel/smp.c | 2 +-
arch/s390/kernel/topology.c
Convert DEVICE_ATTR uses to DEVICE_ATTR_RW where possible.
Done with perl script:
$ git grep -w --name-only DEVICE_ATTR | \
xargs perl -i -e 'local $/; while (<>) {
Hi,
I forgot to add a coverletter, anyways what I wanted to put in the
coverletter and not in the commit message is a link to a picture of the
problem this fixes:
https://fedorapeople.org/~jwrdegoede/IMG_20171217_195637.jpg
Note the screen is actually a portrait screen, so the picture is the
Cleaned up and corrected error codes and condition in various
error check routines. Also added proper err messages when func
returns error.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_drv.c| 14 +++--
From: Mateusz Polrola
Checking whether buffer has more than two pages should be done
by evaluating nents > 1 instead of i > 1 to properly cover the
case when nents == 2.
Signed-off-by: Dongwon Kim
---
From: Mateusz Polrola
Added mutex to export_fd ioctl to prevent double pages mapping of the
same buffer to prevent race condition when two consumers are trying to
map the same buffer on importer VM.
Also locked mutex before sending request via xen communication
Set the license of the driver to "GPL and MIT-X dual" and owner
to "Intel". Also attached license term to all source and header
files
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/hyper_dmabuf_conf.h | 26 ++
Redefined nents_last, which means # of gref in the last page
of lvl2 table in any situation even if it is same as REFS_PER_PAGE.
With this, loop can be simplified with less condition check.
Signed-off-by: Dongwon Kim
---
drivers/xen/hyper_dmabuf/xen/hyper_dmabuf_xen_shm.c
Hi,
> For example, having a userspace splash that starts as early as it can
> (thus on vesafb/efifb on a PC) will cause the KMS driver to fail
> reserving the entirety of video RAM, and thus fail loading. This cannot be
> fixed.
well the fix there is to use drm devices... like this:
On 12/19/2017 06:26 PM, Daniel Vetter wrote:
> On Tue, Dec 19, 2017 at 6:04 PM, Max Staudt wrote:
>> Well, those could enable fbcon if they want the bootsplash. Shouldn't make a
>> difference anyway if they're powerful enough to run Linux. As long as the
>> bootsplash is shown,
From: Kai Chen
Make sure hy_drv_priv is freed before exiting in several places
in hyper_dmabuf_drv_init.
v2: unlocking mutex before freeing hy_drv_priv when bknd_ops->init
fails
Signed-off-by: Kai Chen
Signed-off-by: Dongwon Kim
Comm env intialization is now scheduled to be done
when xenstore is initialized. This scheduling is done
in driver's init routine.
Also, adding a recursively scheduled routine
that monitors any new tx ch setup from other domains
and automaticlaly configure rx channel accordingly
(every 10 sec).
On Tue, Dec 19, 2017 at 07:21:13PM +, Hans de Goede wrote:
> At least on the Chuwi Vi8 (non pro/plus) the LCD panel will show an image
> shifted aprox. 20% to the left (with wraparound) and sometimes also wrong
> colors, showing that the panel controller is starting with sampling the
>
Convert DEVICE_ATTR uses to DEVICE_ATTR_RO where possible.
Done with perl script:
$ git grep -w --name-only DEVICE_ATTR | \
xargs perl -i -e 'local $/; while (<>) {
s/\bDEVICE_ATTR\s*\(\s*(\w+)\s*,\s*\(?(?:\s*S_IRUGO\s*|\s*0444\s*)\)?\s*,\s*\1_show\s*,\s*NULL\s*\)/DEVICE_ATTR_RO(\1)/g;
1 - 100 of 151 matches
Mail list logo