dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: ML mesa-dev <mesa-dev@lists.freedesktop.org>,
	Rob Herring <robh+dt@kernel.org>,
	Steven Price <steven.price@arm.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Boris Brezillon <boris.brezillon@collabora.com>
Subject: Re: [RFC PATCH] mesa: Export BOs in RW mode
Date: Wed, 3 Jul 2019 09:07:29 -0700	[thread overview]
Message-ID: <20190703160729.GA3948@kevin> (raw)
In-Reply-To: <20190703154724.GJ15868@phenom.ffwll.local>


[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]

> Since the same discussion is happening with etnaviv: Why exactly does mesa
> need to mmap imported buffers?

The golden question!

Seemingly, (one of the) reasons is that the state tracker does
colourspace conversion in software if the winsys wants a format that the
driver doesn't advertise. Unrelated to this, that's almost certainly a
performance issue and might explain quite a bit...

In this case, the winsys seems to want RGB10_A2 but we settle for RGBA8.
I thought that was just changing EGL negotiation stuff.. I had no idea
it was covering up in software... not good...

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

      parent reply	other threads:[~2019-07-03 16:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 13:33 [RFC PATCH] mesa: Export BOs in RW mode Boris Brezillon
2019-07-03 13:45 ` Rob Herring
2019-07-03 13:56   ` Boris Brezillon
2019-07-03 14:13     ` Steven Price
2019-07-03 14:33       ` Boris Brezillon
2019-07-03 14:50         ` Steven Price
2019-07-03 15:07           ` Boris Brezillon
2019-07-03 16:18           ` Daniel Vetter
2019-07-04  9:26             ` Steven Price
2019-07-04  9:46               ` [Mesa-dev] " Daniel Vetter
2019-07-04 16:37                 ` [PATCH] dma-buf: Update docs to discourage use of dma_buf_mmap() Steven Price
2019-07-03 15:59       ` [RFC PATCH] mesa: Export BOs in RW mode Rob Herring
2019-07-03 16:15         ` Steven Price
2019-07-03 15:47   ` Daniel Vetter
2019-07-03 15:49     ` Daniel Vetter
2019-07-03 16:07     ` Alyssa Rosenzweig [this message]

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=20190703160729.GA3948@kevin \
    --to=alyssa.rosenzweig@collabora.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=robh+dt@kernel.org \
    --cc=steven.price@arm.com \
    /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