Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2195715ybh; Mon, 9 Mar 2020 00:41:08 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsixFSszkBgFx7af6Lj6YsJbrAX8Gb/h+lNzqisC92NGVDSOfHxi8Bm6N52MRDitLNwI3bX X-Received: by 2002:a9d:4541:: with SMTP id p1mr12278381oti.199.1583739668863; Mon, 09 Mar 2020 00:41:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583739668; cv=none; d=google.com; s=arc-20160816; b=aKKs7CJ/XNzFHXYc/l9Gf98h6z5og0UvRk6uFNPuAb5kCkP0Yn/9zMEuwBmji7b/pg PDXc/fXWLqmK/U7Ar1lBSxiWXYO3VC0eKlfow7p5/wWg5Qh4Ug30iT1M+hFNhX85rHSl WoJ5hIeTz1DN8h1E8cPxYN5T3tqEL2AunUVQcVoPSntUI/gwWKZQzdjB7w6RE8OJE+Qr cWUw7WvU5Vauz6C+vtfasi8a19+UNVSs0j93v0PTV8LL0pYNCr37Ls+LfTIppClOD0Ja 9qJjbN/E56BH5EPLYnj0ABS78PQWllRbIlZ6W62cgEyxlyWNC2S1ibCLkg13pnn/5gkf AcZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=lDh2YIDb9vMSkZayjdTws9M7um4cCCRB3gf7x+Y/aVA=; b=VmmzD92t26cqqiRB+X/GPvAK39iuyDWLRJNRzkmGeljicntpn63Yluq0p1MdsgayWz jPV1Y3eWX6L+Xv5N79SFlelH1OlcUtXvZbUmzec20Mz9n8+Iq3nnRMVSoCAY8s0QmPNB lzzhVhpuFV/+6Q93RrY/5RuDPz6kd6ieAa4GQUfDaHTqXwQ0/Yzmbi7mNaC+2NM+G7qM WSmk6bb+ZOx7QNVdf/3DSxADyKf+x6EYQX7wQRA8u4djW4jy9WGPWbw3/lTEEFekqp1+ yECvkul5Qv8fuofTVtISnhKM+V4jZwmXwHKKDvJgOdweaiTL2/ZJRAiYynDa0AFWjEkg slJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=HbwpAGiE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h13si5727153otk.167.2020.03.09.00.40.56; Mon, 09 Mar 2020 00:41:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=HbwpAGiE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726486AbgCIHjO (ORCPT + 99 others); Mon, 9 Mar 2020 03:39:14 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:46293 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726027AbgCIHjN (ORCPT ); Mon, 9 Mar 2020 03:39:13 -0400 Received: by mail-pg1-f194.google.com with SMTP id y30so4311580pga.13 for ; Mon, 09 Mar 2020 00:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=lDh2YIDb9vMSkZayjdTws9M7um4cCCRB3gf7x+Y/aVA=; b=HbwpAGiECfiJ5QIVoV/10COWkjpuf99URX3VmiBIs7WlpfDfrNcDSGvGrxu4C+BMvX ICRCaO8wT0g5mqLVYD6KM2z6mAD4grC6imeiHScgqESSeubx3qB5svp64w5UOhVveK/0 scZqsFzHua+ATFWvHml42xQhj6gHTEAmBaM+0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=lDh2YIDb9vMSkZayjdTws9M7um4cCCRB3gf7x+Y/aVA=; b=l9AhyFzgMzzic3z3uWujxT330dWg50UcKphB3TIhcTTRhjvVA9Pq74aWXIEulWp8f2 yFLWqHhESG9okNHunnfCIwbTNG2RGivIQ+/mo57OVs9SvXHG6/zj4Hu2O1tZILUH5m5z /lnaWqyT5HLM32vpxG8moO73EEMUmAVfLZs5oQqsqz5zaAPJ04ADziyyJ1DKOww/Pxfp llJ2wIc7juGDkm7wUK6gaLddVr62Ei1ISWMpsSVQWxNS5qglWtOoTiThwOykl6SIidqi bZUG+RFfatXX7/82PUdQNf4cH7odiKbiVYYDxtacEb9Ss2k7I6+aH+btGzygMU2gWMuJ 6m5w== X-Gm-Message-State: ANhLgQ2tJyyhEJXlBd8OXqNYoLQRyLQeTl0blc8WPS5rAgyymRzeqp2F y9xJy3cZIjTXG7eLG4uE1b75rQ== X-Received: by 2002:a63:a062:: with SMTP id u34mr15571753pgn.286.1583739552043; Mon, 09 Mar 2020 00:39:12 -0700 (PDT) Received: from localhost ([2401:fa00:8f:203:5bbb:c872:f2b1:f53b]) by smtp.gmail.com with ESMTPSA id x4sm38021917pgi.76.2020.03.09.00.39.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Mar 2020 00:39:11 -0700 (PDT) Date: Mon, 9 Mar 2020 16:39:09 +0900 From: Sergey Senozhatsky To: Hans Verkuil Cc: Sergey Senozhatsky , Hans Verkuil , Tomasz Figa , Mauro Carvalho Chehab , Kyungmin Park , Marek Szyprowski , Sakari Ailus , Laurent Pinchart , Pawel Osciak , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [PATCHv4 01/11] videobuf2: add cache management members Message-ID: <20200309073909.GD46830@google.com> References: <20200302041213.27662-2-senozhatsky@chromium.org> <17060663-9c30-de5e-da58-0c847b93e4d3@xs4all.nl> <20200307094634.GB29464@google.com> <6f5916dd-63f6-5d19-13f4-edd523205a1f@xs4all.nl> <20200307112838.GA125961@google.com> <20200309032707.GA9460@google.com> <40cd09d9-49a6-2159-3c50-825732151221@xs4all.nl> <20200309072526.GC46830@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (20/03/09 08:28), Hans Verkuil wrote: > >>> I'm looking into it. Will it work if I patch the vivid test driver to > >>> enable/disable ->allow_cache_hints bit per-node and include the patch > >>> into the series. So then v4l2 tests can create some nodes with > >>> ->allow_cache_hints. Something like this: > >> > >> I would add a 'cache_hints' module parameter (array of bool) to tell vivid > >> whether cache hints should be set or not for each instance. It would be useful > >> to have this in vivid. Don't forget to update Documentation/media/v4l-drivers/vivid.rst > >> as well. > > > > I see. Hmm, how do I do "test that V4L2_BUF_CAP_SUPPORTS_CACHE_HINTS > > is never set" then? > > Not sure I understand your question. When requesting buffers for non-MMAP memory, > this capability must never be returned. That has nothing to do with a cache_hints > module option. OK. What I thought was that not every MMAP memory node can have cache hints enabled, so it should be verified that only MMAP nodes which were configured to allow_cache_hints should report that CAP, the rest of MMAP nodes (if any) should have that CAP bit clear. -ss