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.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 smtp.lore.kernel.org (Postfix) with ESMTPS id 0546CC7EE22 for ; Mon, 15 May 2023 10:05:13 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pyV4M-0001Eq-M7; Mon, 15 May 2023 06:04:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pyV40-00019J-FV for qemu-devel@nongnu.org; Mon, 15 May 2023 06:04:20 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pyV3y-0000Ww-Lc for qemu-devel@nongnu.org; Mon, 15 May 2023 06:04:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1684145058; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ytu6mNbKiHMRjxb5/HCxd8UnrRmRjwtii8S1gvg+KXY=; b=gHG+RjTBdRS4Mc5b4PWIHtlqo/CR4ketrLnudRZqlUaQB/KPbX98QUGIHBVPyhwYgu5nba +bhKl6G1+fYtCKaRXnccDUUZZe6S6NgFKGEw0IGe4oByeumF8pMRsjk6YwcTaAHd7M4P0c I3kV69Wr8h0FbKYEuIyiegBM4EVXaUI= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-561-6OUWgs3bN06D7NJZwwlGvQ-1; Mon, 15 May 2023 06:04:14 -0400 X-MC-Unique: 6OUWgs3bN06D7NJZwwlGvQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E0EF43814948; Mon, 15 May 2023 10:04:13 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.48]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5D5B82166B26; Mon, 15 May 2023 10:03:55 +0000 (UTC) Date: Mon, 15 May 2023 11:03:47 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Peter Maydell Cc: Hao Zeng , pbonzini@redhat.com, qemu-arm@nongnu.org, qemu-devel@nongnu.org, Gerd Hoffmann Subject: Re: [PATCH V2] hw/arm: enable qxl for aarch64 Message-ID: References: <20230512093108.1180726-1-zenghao@kylinos.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.9 (2022-11-12) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 Received-SPF: pass client-ip=170.10.129.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Mon, May 15, 2023 at 10:59:16AM +0100, Peter Maydell wrote: > On Mon, 15 May 2023 at 10:57, Hao Zeng wrote: > > > > > > On Mon, 2023-05-15 at 09:52 +0100, Daniel P. Berrangé wrote: > > > Overall, IMHO, we should keep QXL restricted to as few build > > > scenarios > > > as possible. Given the status of SPICE, possibly we'll even want to > > > deprecate it on x86 eventually, not add it to more arches. > > > > > > What are you seeing as the compelling use case that requires QXL to > > > exist on aarch64 ? > > > Thank you for your answer, it made me learn a lot. No use case, just > > outside customer feedback on the ARM architecture qxl use has problems, > > I compiled the community qemu, found that the default does not support > > qxl display, so the submitted enablement. > > I agree with you, please ignore this commit. > > I would still like to know why QXL isn't automatically > enabled like every other PCI device... Historical reasons ? Originally both QXL and SPICE were x86 only and SPICE was broken on big endian if you tried to build it. The orignal QXL code in QEMU had a hard dependancy on SPICE until an enhancement made it work with other backends. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|