Re: Re: [PATCH v2 13/18] mm/compaction: support non-lru movable pagemigration

2016-03-23 Thread Minchan Kim
On Thu, Mar 24, 2016 at 05:26:50AM +0900, Gioh Kim wrote: >Hmmm... But, in failure case, is it safe to call putback_lru_page() for >them? >And, PageIsolated() would be left. Is it okay? It's not symmetric that >isolated page can be freed by decreasing ref count without calling >

Re: [PATCH v2 13/18] mm/compaction: support non-lru movable page migration

2016-03-23 Thread Minchan Kim
On Wed, Mar 23, 2016 at 02:05:11PM +0900, Joonsoo Kim wrote: > On Tue, Mar 22, 2016 at 11:55:45PM +0900, Minchan Kim wrote: > > On Tue, Mar 22, 2016 at 02:50:37PM +0900, Joonsoo Kim wrote: > > > On Mon, Mar 21, 2016 at 03:31:02PM +0900, Minchan Kim wrote: > > > > We have allowed migration for only

RE: Re: [PATCH v2 13/18] mm/compaction: support non-lru movable pagemigration

2016-03-23 Thread Gioh Kim
Hmmm... But, in failure case, is it safe to call putback_lru_page() for them? And, PageIsolated() would be left. Is it okay? It's not symmetric that isolated page can be freed by decreasing ref count without calling putback function. This should be clarified and documented. I agree Joo

Re: [PATCH v2 13/18] mm/compaction: support non-lru movable page migration

2016-03-23 Thread Joonsoo Kim
On Tue, Mar 22, 2016 at 11:55:45PM +0900, Minchan Kim wrote: > On Tue, Mar 22, 2016 at 02:50:37PM +0900, Joonsoo Kim wrote: > > On Mon, Mar 21, 2016 at 03:31:02PM +0900, Minchan Kim wrote: > > > We have allowed migration for only LRU pages until now and it was > > > enough to make high-order pages.

Re: [PATCH v2 13/18] mm/compaction: support non-lru movable page migration

2016-03-23 Thread Joonsoo Kim
On Mon, Mar 21, 2016 at 03:31:02PM +0900, Minchan Kim wrote: > We have allowed migration for only LRU pages until now and it was > enough to make high-order pages. But recently, embedded system(e.g., > webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory) > so we have seen several

[PATCH v2] drm/virtio: send vblank event after crtc updates

2016-03-23 Thread Gustavo Padovan
From: Gustavo Padovan virtio_gpu was failing to send vblank events when using the atomic IOCTL with the DRM_MODE_PAGE_FLIP_EVENT flag set. This patch fixes each and enables atomic pageflips updates. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_display.c | 12

Re: [PATCH 2/2] drm/virtio: send vblank event on plane atomic update

2016-03-23 Thread Daniel Stone
Hi, On 21 March 2016 at 19:23, Gustavo Padovan wrote: > @@ -96,6 +98,11 @@ static void virtio_gpu_plane_atomic_update(struct > drm_plane *plane, > plane->state->crtc_y, > plane->state->crtc_w, >

[PATCH 2/2] drm/virtio: send vblank event on plane atomic update

2016-03-23 Thread Gustavo Padovan
From: Gustavo Padovan virtio_gpu was failing to send vblank events when using the atomic IOCTL with the DRM_MODE_PAGE_FLIP_EVENT flag set. This patch fixes each and enables atomic pageflips updates. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_plane.c | 9 - 1 file

[PATCH 1/2] drm/virtio: use new drm_crtc_send_vblank_event()

2016-03-23 Thread Gustavo Padovan
From: Gustavo Padovan Simplify code by using the new vblank crtc helpers. Signed-off-by: Gustavo Padovan --- drivers/gpu/drm/virtio/virtgpu_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_d