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=-10.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 9B45DC35280 for ; Wed, 2 Oct 2019 12:40:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6CDA221D7B for ; Wed, 2 Oct 2019 12:40:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570020005; bh=C27WP3WjY83XjqK00FA77hEI/TbJNxmgHsX3G7ohuJY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=NIxD+SfK0g/vzHVow+Do4I+gxtrsw5xPutKDD/LXIP/XxGpAGy4bLENGZHh2gLm1A Y/lsZd0rXpN+aWnahSLXFEvTkLzv+g4AkkkbTB6JmYkAIZ7iykHKZquUJW4GA+9G1n MSrrr+cj/kO2h8kLW6QS8VWUc0L0hJ/uNSVoZ0BY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726373AbfJBMkF (ORCPT ); Wed, 2 Oct 2019 08:40:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:35818 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726325AbfJBMkF (ORCPT ); Wed, 2 Oct 2019 08:40:05 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 430082133F; Wed, 2 Oct 2019 12:40:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570020003; bh=C27WP3WjY83XjqK00FA77hEI/TbJNxmgHsX3G7ohuJY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=r1ISHHmlUa3ArxhsAN1rIrYFbdp7E9Nft088x4rC2BWSc1rug9fMRZiNAEvlaN9sk psxK5zJ4K0fRIworDS+q3PHxoLSWsTxwjQE2GdAQfEPZ2BVH804MSe+aysCm4f7xwy KNwsXlVW8+wyrVavZo30CoO4tzHc6UVNjBTRJcfA= Date: Wed, 2 Oct 2019 08:40:02 -0400 From: Sasha Levin To: Dexuan Cui Cc: Michael Kelley , Wei Hu , "rdunlap@infradead.org" , "shc_work@mail.ru" , "gregkh@linuxfoundation.org" , "lee.jones@linaro.org" , "alexandre.belloni@bootlin.com" , "baijiaju1990@gmail.com" , "info@metux.net" , "linux-hyperv@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "linux-fbdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Stephen Hemminger , Haiyang Zhang , KY Srinivasan Subject: Re: [PATHC v6] video: hyperv: hyperv_fb: Support deferred IO for Hyper-V frame buffer driver Message-ID: <20191002124002.GL17454@sasha-vm> References: <20190918060227.6834-1-weh@microsoft.com> <20191001184828.GF8171@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-hyperv-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On Wed, Oct 02, 2019 at 08:09:41AM +0000, Dexuan Cui wrote: >> -----Original Message----- >> From: Sasha Levin >> Sent: Tuesday, October 1, 2019 11:48 AM >> >> On Fri, Sep 20, 2019 at 05:26:34PM +0000, Michael Kelley wrote: >> >From: Michael Kelley Sent: Wednesday, >> September 18, 2019 2:48 PM >> >> > >> >> > Without deferred IO support, hyperv_fb driver informs the host to refresh >> >> > the entire guest frame buffer at fixed rate, e.g. at 20Hz, no matter there >> >> > is screen update or not. This patch supports deferred IO for screens in >> >> > graphics mode and also enables the frame buffer on-demand refresh. The >> >> > highest refresh rate is still set at 20Hz. >> >> > >> >> > Currently Hyper-V only takes a physical address from guest as the starting >> >> > address of frame buffer. This implies the guest must allocate contiguous >> >> > physical memory for frame buffer. In addition, Hyper-V Gen 2 VMs only >> >> > accept address from MMIO region as frame buffer address. Due to these >> >> > limitations on Hyper-V host, we keep a shadow copy of frame buffer >> >> > in the guest. This means one more copy of the dirty rectangle inside >> >> > guest when doing the on-demand refresh. This can be optimized in the >> >> > future with help from host. For now the host performance gain from >> deferred >> >> > IO outweighs the shadow copy impact in the guest. >> >> > >> >> > Signed-off-by: Wei Hu >> > >> >Sasha -- this patch and one other from Wei Hu for the Hyper-V frame buffer >> >driver should be ready. Both patches affect only the Hyper-V frame buffer >> >driver so can go through the Hyper-V tree. Can you pick these up? Thx. >> >> I can't get this to apply anywhere, what tree is it based on? >> >> -- >> Thanks, >> Sasha > >Hi Sasha, >Today's hyperv/linux.git's hyperv-next branch's top commit is > 48b72a2697d5 ("hv_netvsc: Add the support of hibernation"). > >Please pick up two patches from Wei Hu: >#1: [PATCH v4] video: hyperv: hyperv_fb: Obtain screen resolution from Hyper-V host >#2: [PATHC v6] video: hyperv: hyperv_fb: Support deferred IO for Hyper-V frame buffer driver Ah, I guess I was missing the first one. I've queued both for hyperv-next, thanks! -- Thanks, Sasha