qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hao Zeng <zenghao@kylinos.cn>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: pbonzini@redhat.com, peter.maydell@linaro.org,
	qemu-arm@nongnu.org,  qemu-devel@nongnu.org,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH V2] hw/arm: enable qxl for aarch64
Date: Mon, 15 May 2023 17:56:32 +0800	[thread overview]
Message-ID: <e2d06c7a6528a16b6ae58360d49a1fc9c7e8ade5.camel@kylinos.cn> (raw)
In-Reply-To: <ZGHyvBb8BQdKhWEy@redhat.com>


On Mon, 2023-05-15 at 09:52 +0100, Daniel P. Berrangé wrote:
> On Fri, May 12, 2023 at 05:31:08PM +0800, Hao Zeng wrote:
> > Qemu does not support qxl graphics cards in arm, it is recommended
> > to enable
> 
> Who recommends this and why ?
> 
> The recommendations from Gerd are what I tend to point poeple to
> for display devices:
> 
>   https://www.kraxel.org/blog/2019/09/display-devices-in-qemu/
> 
> and it had this to say about arm:
> 
>   "On arm systems display devices with a pci memory bar do
>    not work, which reduces the choices alot. We are left with:
> 
>     virtio gpu, if your guest has drivers
>     ramfb"
> 
> Not sure if anything has changed in this respect ?
> 
> 
> The QXL graphics card is an incredibly complex device, offering
> 2d acceleration that is not very interesting for modern guest OS
> desktops since they're largely focused on 3d acceleration. This
> complexity is bad from a security POV.
> 
> It would also require a guest driver to take advantage of QXL
> features and while I presume the Linux driver will build, it is
> still mostly pointless because of lack of interest in 2d
> acceleration.
> I'm not sure about status of the Windows QXL driver for aarch64 ?
> 
> Further QXL is only useful when combined with SPICE graphics and
> the SPICE project is largely inactive.
> 
> 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 ?
> 
hi Daniel:
   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 apologize for the disturbance to you all.

Best regards,
> Hao
> 
> 
> > 
> > Signed-off-by: Hao Zeng <zenghao@kylinos.cn>
> > ---
> >  hw/arm/Kconfig | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
> > index 0f42c556d7..d0bedf9347 100644
> > --- a/hw/arm/Kconfig
> > +++ b/hw/arm/Kconfig
> > @@ -32,6 +32,7 @@ config ARM_VIRT
> >      select VIRTIO_MEM_SUPPORTED
> >      select ACPI_CXL
> >      select ACPI_HMAT
> > +    select QXL
> >  
> >  config CHEETAH
> >      bool
> > -- 
> > 2.37.2
> > 
> > 
> 
> With regards,
> Daniel



  parent reply	other threads:[~2023-05-15  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  9:31 [PATCH V2] hw/arm: enable qxl for aarch64 Hao Zeng
2023-05-15  8:52 ` Daniel P. Berrangé
2023-05-15  9:41   ` Peter Maydell
2023-05-15  9:56   ` Hao Zeng [this message]
2023-05-15  9:59     ` Peter Maydell
2023-05-15 10:03       ` Daniel P. Berrangé
2023-05-15 10:54         ` Gerd Hoffmann
2023-05-15 11:54           ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2d06c7a6528a16b6ae58360d49a1fc9c7e8ade5.camel@kylinos.cn \
    --to=zenghao@kylinos.cn \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).