All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Hao Zeng <zenghao@kylinos.cn>,
	pbonzini@redhat.com, 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 11:03:47 +0100	[thread overview]
Message-ID: <ZGIDg+8xIOGpTIO4@redhat.com> (raw)
In-Reply-To: <CAFEAcA8fN-+FUJapo=+ObZgfrJW32ccFj22qvU92ndNzPLQ9Dw@mail.gmail.com>

On Mon, May 15, 2023 at 10:59:16AM +0100, Peter Maydell wrote:
> On Mon, 15 May 2023 at 10:57, Hao Zeng <zenghao@kylinos.cn> 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 :|


  reply	other threads:[~2023-05-15 10:04 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
2023-05-15  9:59     ` Peter Maydell
2023-05-15 10:03       ` Daniel P. Berrangé [this message]
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=ZGIDg+8xIOGpTIO4@redhat.com \
    --to=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 \
    --cc=zenghao@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.