On 4/2/21 7:26 AM, Catalin Marinas wrote:
On Wed, Mar 31, 2021 at 02:23:44PM -0400, Zack Rusin wrote:
The pagetable walk callbacks in mm/mapping_dirty_helpers.c depend
on a set of helpers from which pud_dirty(pud) was missing. I'm
assuming mapping_dirty_helpers weren't used on AR
Lets make sure we don't use pud hugepage helpers on architectures
which do not support it. This fixes the code on arm64.
Signed-off-by: Zack Rusin
Cc: Andrew Morton
Cc: Thomas Hellström (Intel)
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/mapping_dirty_helpers.c | 2
On 2/25/21 4:09 AM, Daniel Vetter wrote:
On Wed, Feb 24, 2021 at 11:55 AM Sumera Priyadarsini
wrote:
Add a virtual hardware or vblank-less mode as a module to enable
VKMS to emulate virtual graphic drivers. This mode can be enabled
by setting enable_virtual_hw=1 at the time of loading VKMS.
A
> On Jan 19, 2021, at 03:29, Lee Jones wrote:
>
> On Mon, 18 Jan 2021, Daniel Vetter wrote:
>
>> On Mon, Jan 18, 2021 at 03:09:45PM +, Lee Jones wrote:
>>> On Mon, 18 Jan 2021, Daniel Vetter wrote:
>>>
>>>> On Fri, Jan 15, 2021 at 06:27:15
usage with the given pgprot.
>
> Remove the NULL pointer check for the map. These functions return a valid
> address for valid pages and the return was bogus anyway as it would have
> left preemption and pagefaults disabled.
>
> Signed-off-by: Thomas Gleixner
> Cc: VMware Grap
code uses mapping_dirty_helpers and
has been ported to ARM64 but it depends on this code getting in
first in order to compile/work.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Peter Zijlstra
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Zack Rusin
---
arch/arm64/include/asm/pgtable.h | 1 +
1 fi
on my next series. Unless of
course you want to push it through a different tree in which case:
Reviewed-by: Zack Rusin
z
ompilation errors whenever one of the drivers
is ported to new architectures.
Signed-off-by: Zack Rusin
Cc: Andrew Morton
Cc: Thomas Hellström (Intel)
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/mapping_dirty_helpers.c | 2 ++
1 file changed, 2 insertions(+)
diff
Add an interruptible version of down_write. It's the other
side of the already implemented down_read_interruptible.
It allows drivers which used custom locking code to
support interruptible rw semaphores to switch over
to rwsem.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Will Deacon
Cc: linux-kerne
vmwgfx used a custom locking code to support semantics of a
interruptible rwsem. Now with down_(read|write)_interruptible
implemented in the rwsem we can completely remove the custom
locking code. It also allows us to remove the hacks we needed
to support proper waits for write resources before
hib
Zijlstra
Cc: Ingo Molnar
Cc: Will Deacon
Cc: Martin Krastev
Cc: Roland Scheidegger
Cc: linux-kernel@vger.kernel.org
Cc: dri-de...@lists.freedesktop.org
Zack Rusin (2):
locking/rwsem: Add down_write_interruptible
drm/vmwgfx: Remove custom locking code
drivers/gpu/drm/vmwgfx/Makefile
On 3/9/21 3:49 AM, Peter Zijlstra wrote:
On Mon, Mar 08, 2021 at 03:54:55PM -0500, Zack Rusin wrote:
Add an interruptible version of down_write. It's the other
side of the already implemented down_read_interruptible.
It allows drivers which used custom locking code to
support interruptib
r all the vmwgfx bits:
Reviewed-by: Zack Rusin
z
x86.
Thanks! For all the vmwgfx bits:
Reviewed-by: Zack Rusin
z
14 matches
Mail list logo
