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 Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9B542EB64D8 for ; Tue, 20 Jun 2023 09:41:42 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.551488.861060 (Exim 4.92) (envelope-from ) id 1qBXrj-0003So-4u; Tue, 20 Jun 2023 09:41:35 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 551488.861060; Tue, 20 Jun 2023 09:41:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1qBXrj-0003SZ-1C; Tue, 20 Jun 2023 09:41:35 +0000 Received: by outflank-mailman (input) for mailman id 551488; Tue, 20 Jun 2023 09:41:33 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1qBXrh-00037y-Iz for xen-devel@lists.xenproject.org; Tue, 20 Jun 2023 09:41:33 +0000 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id a34b74df-0f4e-11ee-b234-6b7b168915f2; Tue, 20 Jun 2023 11:41:32 +0200 (CEST) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-272-ae1SokUPNamv0gV-ky2RfQ-1; Tue, 20 Jun 2023 05:41:25 -0400 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E94F0803FE0; Tue, 20 Jun 2023 09:41:23 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.126]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9AD1B40C200F; Tue, 20 Jun 2023 09:41:23 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 3CD1E1807DD4; Tue, 20 Jun 2023 11:41:22 +0200 (CEST) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: a34b74df-0f4e-11ee-b234-6b7b168915f2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687254091; 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=3It2NZYCXKRzeV7HhNGMTFh0lnlvIJkuzNah3Z/f6V8=; b=fhfIQukg5JWbT9W4QQQVIbWtuxSR140CNfsi8ZPlUQO/lcOm0S3VBo6vFM2XwDYL8oOMMu DFSF/p7PLFyNXu8I6bofkrLN0J3tBzM0Dw2hQ2BfJve7ugcYkCx2ysj6y/hVhq39FHMM32 Qn4wyv/EaqGHoJIjzoElEsGbU5qJNsk= X-MC-Unique: ae1SokUPNamv0gV-ky2RfQ-1 Date: Tue, 20 Jun 2023 11:41:22 +0200 From: Gerd Hoffmann To: "Chen, Jiqian" Cc: =?utf-8?Q?Marc-Andr=C3=A9?= Lureau , Damien Hedde , "Michael S . Tsirkin" , Stefano Stabellini , Anthony PERARD , Roger Pau =?utf-8?B?TW9ubsOp?= , Jan Beulich , Antonio Caggiano , "Dr . David Alan Gilbert" , Robert Beckett , "qemu-devel@nongnu.org" , "xen-devel@lists.xenproject.org" , "Deucher, Alexander" , "Koenig, Christian" , "Hildebrand, Stewart" , Xenia Ragiadakou , "Huang, Honglei1" , "Zhang, Julia" , "Huang, Ray" Subject: Re: [QEMU PATCH 1/1] virtgpu: do not destroy resources when guest suspend Message-ID: References: <20230608025655.1674357-1-Jiqian.Chen@amd.com> <20230608025655.1674357-2-Jiqian.Chen@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 Hi, > > The guest driver should be able to restore resources after resume. > > Thank you for your suggestion! > As far as I know, resources are created on host side and guest has no backup, if resources are destroyed, guest can't restore them. > Or do you mean guest driver need to send commands to re-create resources after resume? The later. The guest driver knows which resources it has created, it can restore them after suspend. > If so, I have some questions. Can guest re-create resources by using > object(virtio_vpu_object) or others? Can the new resources replace the > destroyed resources to continue the suspended display tasks after > resume? Any display scanout information will be gone too, the guest driver needs re-create this too (after re-creating the resources). take care, Gerd