From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F03D3C47255 for ; Mon, 11 May 2020 11:35:53 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B25F320708 for ; Mon, 11 May 2020 11:35:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="dmn+gDFU" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B25F320708 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:56372 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jY6iu-0000B7-UB for qemu-devel@archiver.kernel.org; Mon, 11 May 2020 07:35:52 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58106) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jY6hz-0007Tc-T3 for qemu-devel@nongnu.org; Mon, 11 May 2020 07:34:55 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:32232 helo=us-smtp-delivery-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1jY6hy-0007TN-NE for qemu-devel@nongnu.org; Mon, 11 May 2020 07:34:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589196893; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eiIw/GYlFotp6RclmORvcQ8g8kH2kGGUsqY/lzLOzlU=; b=dmn+gDFUO8SsGyPyVW3zndfndVUVgYyNtSB/tHUsbm0bcHYZsgbS5pctZy4UoTO2rcjQVN 9zJrEN5a9hzNk1JyJcZGVKAm2WqOk18AAuR3w83dz+y+7W5XRWpCBLkP+lCuKgY1NSHsvw 3VAj2PZNDkdTimh+8bijoBxhHrAmbDI= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-274-0dg06w4IM1OBA_Ruta1-9w-1; Mon, 11 May 2020 07:34:52 -0400 X-MC-Unique: 0dg06w4IM1OBA_Ruta1-9w-1 Received: by mail-wr1-f72.google.com with SMTP id z10so1099536wrs.2 for ; Mon, 11 May 2020 04:34:51 -0700 (PDT) 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; bh=eiIw/GYlFotp6RclmORvcQ8g8kH2kGGUsqY/lzLOzlU=; b=C5Y89S86UEv3hfDumqToaRvR4S9ew2ALwjJdBfXxpnRGNyhioo8aR4QvVOLMlUhJor PP8bSMiGTv+dj/Xd8vIDAM3/g7KOYa3bUA4zclLI1XaKH7tZlLysWWhl9EGuzjOUhgTH ZE9BmsV1L1BRIaZU4WF0axhJfwF0TLMqukhPpWV3+pdKgtXUx0Ql8crtBEvnEuREhdKB Irv2v8ZrF3r5DLAOufTJbNCp7U14eiDn1med3sinbyal7jXk6lIAaYRvotxCOz6xGExg 1z7e4hVtlLQQL49OkuXaGNOodluZdvVQbZTEet/V+2kMsK/64PKOwqbEeZABw584iVyJ tBeg== X-Gm-Message-State: AGi0PuYaxgBGzKqdVkWG5ycseJsLCJqbNyNkUmTYtjh6tjysl9V0+Xis hwScHpjgrlqj9bXEVj5Ls5MVAyemCjzs/obYbseAtaLuSBviPf4rGYRtryhMSHYXGXzguSFZaLG DM/RfOwbvNH87D20= X-Received: by 2002:a7b:cbc5:: with SMTP id n5mr15428997wmi.110.1589196890610; Mon, 11 May 2020 04:34:50 -0700 (PDT) X-Google-Smtp-Source: APiQypKyBWwxj/9b2ZHY5bPRGi2XfOKP8X4m/HsGGG2sV5u/SojFeY0G5z8fRdAhuRLIPCKS3cfuGw== X-Received: by 2002:a7b:cbc5:: with SMTP id n5mr15428958wmi.110.1589196890333; Mon, 11 May 2020 04:34:50 -0700 (PDT) Received: from redhat.com (bzq-79-179-68-225.red.bezeqint.net. [79.179.68.225]) by smtp.gmail.com with ESMTPSA id u16sm17244263wrq.17.2020.05.11.04.34.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 May 2020 04:34:49 -0700 (PDT) Date: Mon, 11 May 2020 07:34:47 -0400 From: "Michael S. Tsirkin" To: Dmitry Sepp Subject: Re: [virtio-dev] Re: Fwd: Qemu Support for Virtio Video V4L2 driver Message-ID: <20200511073251-mutt-send-email-mst@kernel.org> References: <2515515.r9knKAEANn@os-lin-dmo> MIME-Version: 1.0 In-Reply-To: <2515515.r9knKAEANn@os-lin-dmo> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=205.139.110.61; envelope-from=mst@redhat.com; helo=us-smtp-delivery-1.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/11 03:10:56 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Samiullah Khawaja , Keiichi Watanabe , Alex Lau , Kiran Pawar , Alexandre Courbot , virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org, Tomasz Figa , Saket Sinha , Gerd Hoffmann , Hans Verkuil , Pawel Osciak , Linux Media Mailing List Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Mon, May 11, 2020 at 01:25:23PM +0200, Dmitry Sepp wrote: > Hi Saket, > > On Montag, 11. Mai 2020 13:05:53 CEST Saket Sinha wrote: > > Hi Keiichi, > > > > I do not support the approach of QEMU implementation forwarding > > requests to the host's vicodec module since this can limit the scope > > of the virtio-video device only for testing, > > That was my understanding as well. > > > which instead can be used with multiple use cases such as - > > > > 1. VM gets access to paravirtualized camera devices which shares the > > video frames input through actual HW camera attached to Host. > > This use-case is out of the scope of virtio-video. Initially I had a plan to > support capture-only streams like camera as well, but later the decision was > made upstream that camera should be implemented as separate device type. We > still plan to implement a simple frame capture capability as a downstream > patch though. > > > > > 2. If Host has multiple video devices (especially in ARM SOCs over > > MIPI interfaces or USB), different VM can be started or hotplugged > > with selective video streams from actual HW video devices. > > We do support this in our device implementation. But spec in general has no > requirements or instructions regarding this. And it is in fact flexible enough > to provide abstraction on top of several HW devices. Hmm I agree if it's just for pass-through of host devices that's a very limited usecase. Not out of scope for virtio, but let's make it clear it's pass-through in the device name, so that if people want to create a virtualizeable interface down the road they don't feel blocked. > > > > Also instead of using libraries like Gstreamer in Host userspace, they > > can also be used inside the VM userspace after getting access to > > paravirtualized HW camera devices . > > > > Regarding the cameras, unfortunately same as above. > > Best regards, > Dmitry. > > > Regards, > > Saket Sinha > > > > On Mon, May 11, 2020 at 12:20 PM Keiichi Watanabe > wrote: > > > Hi Dmitry, > > > > > > On Mon, May 11, 2020 at 6:40 PM Dmitry Sepp > wrote: > > > > Hi Saket and all, > > > > > > > > As we are working with automotive platforms, unfortunately we don't plan > > > > any Qemu reference implementation so far. > > > > > > > > Of course we are ready to support the community if any help is needed. > > > > Is > > > > there interest in support for the FWHT format only for testing purpose > > > > or you want a full-featured implementation on the QEMU side? > > > > > > I guess we don't need to implement the codec algorithm in QEMU. > > > Rather, QEMU forwards virtio-video requests to the host video device > > > or a software library such as GStreamer or ffmpeg. > > > So, what we need to implement in QEMU is a kind of API translation, > > > which shouldn't care about actual video formats so much. > > > > > > Regarding the FWHT format discussed in the patch thread [1], in my > > > understanding, Hans suggested to have QEMU implementation forwarding > > > requests to the host's vicodec module [2]. > > > Then, we'll be able to test the virtio-video driver on QEMU on Linux > > > even if the host Linux has no hardware video decoder. > > > (Please correct me if I'm wrong.) > > > > > > Let me add Hans and Linux media ML in CC. > > > > > > [1] https://patchwork.linuxtv.org/patch/61717/ > > > [2] https://lwn.net/Articles/760650/ > > > > > > Best regards, > > > Keiichi > > > > > > > Please note that the spec is not finalized yet and a major update is now > > > > discussed with upstream and the Chrome OS team, which is also interested > > > > and deeply involved in the process. The update mostly implies some > > > > rewording and reorganization of data structures, but for sure will > > > > require a driver rework. > > > > > > > > Best regards, > > > > Dmitry. > > > > > > > > On Samstag, 9. Mai 2020 16:11:43 CEST Saket Sinha wrote: > > > > > Hi, > > > > > > > > > > As suggested on #qemu-devel IRC channel, I am including virtio-dev, > > > > > Gerd and Michael to point in the right direction how to move forward > > > > > with Qemu support for Virtio Video V4L2 driver > > > > > posted in [1]. > > > > > > > > > > [1]: https://patchwork.linuxtv.org/patch/61717/ > > > > > > > > > > Regards, > > > > > Saket Sinha > > > > > > > > > > On Sat, May 9, 2020 at 1:09 AM Saket Sinha > wrote: > > > > > > Hi , > > > > > > > > > > > > This is to inquire about Qemu support for Virtio Video V4L2 driver > > > > > > posted in [1]. > > > > > > I am currently not aware of any upstream effort for Qemu reference > > > > > > implementation and would like to discuss how to proceed with the > > > > > > same. > > > > > > > > > > > > [1]: https://patchwork.linuxtv.org/patch/61717/ > > > > > > > > > > > > Regards, > > > > > > Saket Sinha > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org > > > > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org >