From: Frediano Ziglio <fziglio@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
David Airlie <airlied@redhat.com>,
David Airlie <airlied@linux.ie>,
"open list:DRM DRIVER FOR QXL VIRTUAL GPU"
<spice-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVER FOR QXL VIRTUAL GPU"
<virtualization@lists.linux-foundation.org>
Subject: Re: [Spice-devel] [PATCH] drm/qxl: use qxl_num_crtc directly
Date: Thu, 6 Dec 2018 07:53:10 -0500 (EST) [thread overview]
Message-ID: <1902655248.48590444.1544100790071.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181206114217.vog4fgae73us437u@sirius.home.kraxel.org>
>
> On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote:
> > >
> > > Just use qxl_num_crtc directly everywhere instead of using
> > > qdev->monitors_config->max_allowed. Drops pointless indirection
> > > and also is less confusing.
> > >
> >
> > To me is MORE confusing, why comparing number of something with
> > another number? Previously code was comparing number of monitors
> > with number of monitors, not number of CRTs with number of
> > monitors.
>
> Yes, spice/qxl and drm/kms use slightly different terminology.
>
> drm crtc == qxl monitor.
> drm framebuffer == qxl surface.
>
> You need to know that anyway when looking at the qxl ksm code. We
> have function names like qxl_crtc_update_monitors_config(). I fail
> to see why that is a problem ...
>
> cheers,
> Gerd
>
>
I don't see any problem too but you are explaining to me
why your rationale "and also is less confusing" does not
stand.
Frediano
next prev parent reply other threads:[~2018-12-06 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 10:33 [PATCH] drm/qxl: use qxl_num_crtc directly Gerd Hoffmann
2018-12-06 10:59 ` [Spice-devel] " Frediano Ziglio
2018-12-06 11:42 ` Gerd Hoffmann
2018-12-06 12:53 ` Frediano Ziglio [this message]
2018-12-06 13:49 ` Gerd Hoffmann
2018-12-06 14:10 ` Frediano Ziglio
2018-12-06 14:21 ` Gerd Hoffmann
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=1902655248.48590444.1544100790071.JavaMail.zimbra@redhat.com \
--to=fziglio@redhat.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux-foundation.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