Re: [RFC v2 0/8] drm: explicit fencing support

2016-04-25 Thread Daniel Vetter
On Mon, Apr 25, 2016 at 11:21:18PM +, Mike Lothian wrote: > Hi > > Out of interest will this allow tear free with PRIME? Tear free with prime on the kernel side is already supported using reservation objects/fences attached implicitly to dma-bufs. Just needs driver support (which for the disp

[PATCH] staging: board: line over 80 characters

2016-04-25 Thread Nikita Eshkeev
This patch fixes the checkpatch.pl warning: WARNING: line over 80 characters + .domain = "/system-controller@e618/pm-domains/c5/a4lc@1" Signed-off-by: Nikita Eshkeev --- drivers/staging/board/armadillo800eva.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --g

[RFC v2 6/8] drm/fence: add fence to drm_pending_event

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Now a drm_pending_event can either send a real drm_event or signal a fence, or both. It allow us to signal via fences when the buffer is displayed on the screen. Which in turn means that the previous buffer is not in use anymore and can be freed or sent back to another drive

[RFC v2 3/8] dma-buf/sync_file: add sync_file_fences_get()

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Creates a function that given an sync file descriptor returns a fence_collection containing all fences in the sync_file. If there is only one fence in the sync_file this fence itself is returned, however if there is more than one, a fence_collection fence is returned. v2:

[RFC v2 8/8] drm/fence: add out-fences support

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Support DRM out-fences creating a sync_file with a fence for each crtc update with the DRM_MODE_ATOMIC_OUT_FENCE flag. We then send an struct drm_out_fences array with the out-fences fds back in the drm_atomic_ioctl() as an out arg in the out_fences_ptr field. struct drm_o

[RFC v2 0/8] drm: explicit fencing support

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Hi, Currently the Linux Kernel only have an implicit fencing mechanism where the fence are attached directly to buffers and userspace is unaware of what is happening. On the other hand explicit fencing which is not supported yet by Linux but it expose fences to the userspac

[RFC v2 2/8] Documentation: add fence-collection to kernel DocBook

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Include fence-collection files in the DocBook. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/DocBook/device-drivers.tmpl b/Documentation/DocBook/device-drivers.tmpl index 5

[RFC v2 5/8] drm/fence: add in-fences support

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan There is now a new property called FENCE_FD attached to every plane state that receives the sync_file fd from userspace via the atomic commit IOCTL. The fd is then translated to a fence (that may be a fence_collection subclass or just a normal fence) and then used by DRM to

[RFC v2 4/8] drm/fence: allow fence waiting to be interrupted by userspace

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan If userspace is running an synchronously atomic commit and interrupts the atomic operation during fence_wait() it will hang until the timer expires, so here we change the wait to be interruptible so it stop immediately when userspace wants to quit. Also adds the necessary e

[RFC v2 7/8] drm/fence: add fence timeline to drm_crtc

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few members to struct drm_crtc: fence_context, where we store the context we get from fence_context_alloc(), the fence seqno and the fence lock, that we pass in fence_init()

[RFC v2 1/8] dma-buf/fence: add fence_collection fences

2016-04-25 Thread Gustavo Padovan
From: Gustavo Padovan struct fence_collection inherits from struct fence and carries a collection of fences that needs to be waited together. It is useful to translate a sync_file to a fence to remove the complexity of dealing with sync_files on DRM drivers. So even if there are many fences in t

Re: [PATCH 6/6] intel_sgx: TODO file for the staging area

2016-04-25 Thread Andi Kleen
Jarkko Sakkinen writes: > diff --git a/drivers/staging/intel_sgx/TODO b/drivers/staging/intel_sgx/TODO > new file mode 100644 > index 000..05f68c2 > --- /dev/null > +++ b/drivers/staging/intel_sgx/TODO > @@ -0,0 +1,25 @@ > +Documentation > += > + > +* Improve Documents/x86/intel-

Re: [PATCH 6/6] intel_sgx: TODO file for the staging area

2016-04-25 Thread One Thousand Gnomes
> +* Implement ACPI hot-lug for SGX. hot-plug Also with an upstream hat on I would add being able to check the keys on the enclave against a kernel keychain because not everyone will want to solely trust whatever keys the hardware thinks it wants to trust. Alan __

Re: [PATCH 0/6] Intel Secure Guard Extensions

2016-04-25 Thread Andy Lutomirski
On Mon, Apr 25, 2016 at 12:03 PM, Jarkko Sakkinen wrote: > On Mon, Apr 25, 2016 at 10:53:52AM -0700, Greg KH wrote: >> On Mon, Apr 25, 2016 at 08:34:07PM +0300, Jarkko Sakkinen wrote: >> > Intel(R) SGX is a set of CPU instructions that can be used by >> > applications to set aside private regions

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Jarkko Sakkinen
On Mon, Apr 25, 2016 at 10:55:36AM -0700, Greg KH wrote: > On Mon, Apr 25, 2016 at 08:34:10PM +0300, Jarkko Sakkinen wrote: > > Intel(R) SGX is a set of CPU instructions that can be used by > > applications to set aside private regions of code and data. The code > > outside the enclave is disallow

Re: [PATCH 0/6] Intel Secure Guard Extensions

2016-04-25 Thread Jarkko Sakkinen
On Mon, Apr 25, 2016 at 10:53:52AM -0700, Greg KH wrote: > On Mon, Apr 25, 2016 at 08:34:07PM +0300, Jarkko Sakkinen wrote: > > Intel(R) SGX is a set of CPU instructions that can be used by > > applications to set aside private regions of code and data. The code > > outside the enclave is disallow

Re: [PATCH 6/6] intel_sgx: TODO file for the staging area

2016-04-25 Thread Jarkko Sakkinen
On Mon, Apr 25, 2016 at 10:54:26AM -0700, Greg KH wrote: > On Mon, Apr 25, 2016 at 08:34:13PM +0300, Jarkko Sakkinen wrote: > > Signed-off-by: Jarkko Sakkinen > > --- > > drivers/staging/intel_sgx/TODO | 25 + > > 1 file changed, 25 insertions(+) > > create mode 100644 dr

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Greg KH
On Mon, Apr 25, 2016 at 08:34:10PM +0300, Jarkko Sakkinen wrote: > Intel(R) SGX is a set of CPU instructions that can be used by > applications to set aside private regions of code and data. The code > outside the enclave is disallowed to access the memory inside the > enclave by the CPU access co

Re: [PATCH 6/6] intel_sgx: TODO file for the staging area

2016-04-25 Thread Greg KH
On Mon, Apr 25, 2016 at 08:34:13PM +0300, Jarkko Sakkinen wrote: > Signed-off-by: Jarkko Sakkinen > --- > drivers/staging/intel_sgx/TODO | 25 + > 1 file changed, 25 insertions(+) > create mode 100644 drivers/staging/intel_sgx/TODO > > diff --git a/drivers/staging/intel_

Re: [PATCH 0/6] Intel Secure Guard Extensions

2016-04-25 Thread Greg KH
On Mon, Apr 25, 2016 at 08:34:07PM +0300, Jarkko Sakkinen wrote: > Intel(R) SGX is a set of CPU instructions that can be used by > applications to set aside private regions of code and data. The code > outside the enclave is disallowed to access the memory inside the > enclave by the CPU access co

[PATCH 4/6] intel_sgx: ptrace() support for the driver

2016-04-25 Thread Jarkko Sakkinen
This commit implements the 'access' callback for the enclave VMA thus enabling reading and writing the memory of debug enclaves. The page that is accessed is first faulted and marked as reserved so that the EPC evictor will know not to swap the page while it is being manipulated. Signed-off-by: Ja

[PATCH 6/6] intel_sgx: TODO file for the staging area

2016-04-25 Thread Jarkko Sakkinen
Signed-off-by: Jarkko Sakkinen --- drivers/staging/intel_sgx/TODO | 25 + 1 file changed, 25 insertions(+) create mode 100644 drivers/staging/intel_sgx/TODO diff --git a/drivers/staging/intel_sgx/TODO b/drivers/staging/intel_sgx/TODO new file mode 100644 index 000..0

[PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

2016-04-25 Thread Jarkko Sakkinen
Intel(R) SGX is a set of CPU instructions that can be used by applications to set aside private regions of code and data. The code outside the enclave is disallowed to access the memory inside the enclave by the CPU access control. Intel SGX driver provides a ioctl interface for loading and initi

[PATCH 0/6] Intel Secure Guard Extensions

2016-04-25 Thread Jarkko Sakkinen
Intel(R) SGX is a set of CPU instructions that can be used by applications to set aside private regions of code and data. The code outside the enclave is disallowed to access the memory inside the enclave by the CPU access control. The firmware uses PRMRR registers to reserve an area of physical

[PATCH v6] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Parth Sane
Fixed alignment to match open parenthesis. Signed-off-by: Parth Sane --- Changes in v6: -Added line before Signed-off message drivers/staging/rtl8712/hal_init.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/staging/rtl8712/hal_init.c b/drivers/st

Re: [PATCH v5] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Dan Carpenter
On Mon, Apr 25, 2016 at 08:36:48AM +, Parth Sane wrote: > Fixed alignment to match open parenthesis. > Signed-off-by: Parth Sane > > --- Leave a blank line before the Signed-off-by. Really you are resending patches too quickly. You should wait over night or a few hours at least, then do a

RE: [PATCH v2] tools: hv: lsvmbus: add pci pass-through UUID

2016-04-25 Thread Dexuan Cui
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Monday, April 25, 2016 19:06 > To: de...@linuxdriverproject.org > Cc: linux-ker...@vger.kernel.org; KY Srinivasan ; Haiyang > Zhang ; Dexuan Cui > Subject: [PATCH v2] tools: hv: lsvmbus: add pci pass-through UUID > > lsvmbus keeps its

[PATCH v2] tools: hv: lsvmbus: add pci pass-through UUID

2016-04-25 Thread Vitaly Kuznetsov
lsvmbus keeps its own copy of all VMBus UUIDs, add PCIe pass-through device there to not report 'Unknown' for such devices. Signed-off-by: Vitaly Kuznetsov --- Changes since v1: - indentation [Dexuan Cui] --- tools/hv/lsvmbus | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/hv/lsvmbus b

Re: [PATCH] tools: hv: lsvmbus: add pci pass-through UUID

2016-04-25 Thread Vitaly Kuznetsov
Dexuan Cui writes: >> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] >> Sent: Saturday, April 23, 2016 0:21 >> To: de...@linuxdriverproject.org >> Cc: linux-ker...@vger.kernel.org; KY Srinivasan ; Haiyang >> Zhang ; Dexuan Cui >> Subject: [PATCH] tools: hv: lsvmbus: add pci pass-through UUI

[PATCH v5] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Parth Sane
Fixed alignment to match open parenthesis. Signed-off-by: Parth Sane --- Changes in v5: -Fixed missing commit messages. drivers/staging/rtl8712/hal_init.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/staging/rtl8712/hal_init.c b/drivers/staging/rt

[PATCH v4] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Parth Sane
diff --git a/drivers/staging/rtl8712/hal_init.c b/drivers/staging/rtl8712/hal_init.c index 0c76fbc..0dd458d 100644 --- a/drivers/staging/rtl8712/hal_init.c +++ b/drivers/staging/rtl8712/hal_init.c @@ -197,8 +197,8 @@ static u8 rtl8712_dl_fw(struct _adapter *padapter)

[PATCH v3] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Parth Sane
Signed-off-by: Parth Sane --- Changes in v3: -Added missing signed off by line and fixed alignment to match open parenthesis. -Fixed location of message drivers/staging/rtl8712/hal_init.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/staging

Re: [PATCH v2] rtl8712: Fixed alignment to match open parenthesis

2016-04-25 Thread Giedrius Statkevičius
On Mon, Apr 25, 2016 at 4:00 AM, Parth Sane wrote: > Added missing signed off by line and fixed alignment to match > open parenthesis. Put "Added missing signed off by line" below the ---. This is not what we want to have in change logs. ___ devel maili