From: Tormod Volden <lists.tormod@gmail.com>
To: Dave Airlie <airlied@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm: Compare only lower 32 bits of framebuffer map offsets
Date: Sat, 11 Jun 2011 00:59:43 +0200 [thread overview]
Message-ID: <BANLkTi=9UDOSvdbSRDLPhyqi99vYVQ7xYw@mail.gmail.com> (raw)
In-Reply-To: <1306784743-2430-1-git-send-email-lists.tormod@gmail.com>
On Mon, May 30, 2011 at 9:45 PM, Tormod Volden wrote:
> From: Tormod Volden <debian.tormod@gmail.com>
>
> Drivers using multiple framebuffers got broken by commit
> 41c2e75e60200a860a74b7c84a6375c105e7437f which ignored the framebuffer
> (or register) map offset when looking for existing maps. The rationale
> was that the kernel-userspace ABI is fixed at a 32-bit offset, so the
> real offsets could not always be handed over for comparison.
>
> Instead of ignoring the offset we will compare the lower 32 bit. Drivers
> using multiple framebuffers should just make sure that the lower 32 bit
> are different. The existing drivers in question are practically limited
> to 32-bit systems so that should be fine for them.
>
> It is assumed that current drivers always specify a correct framebuffer
> map offset, even if this offset was ignored since above commit. So this
> patch should not change anything for drivers using only one framebuffer.
>
> Drivers needing multiple framebuffers with 64-bit map offsets will need
> to cook up something, for instance keeping an ID in the lower bit which
> is to be aligned away when it comes to using the offset.
>
> All of above applies to _DRM_REGISTERS as well.
>
> Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
> ---
>
>
> On Mon, May 30, 2011 at 1:29 AM, Dave Airlie wrote:
>>
>> If you test it and it works I like it best. Simple and clear, and pretty
>> close to what I was thinking was a good idea.
>>
>> As you say if someone needs this functionality in a new driver they can
>> fix it, but really new drivers shouldn't be doing anything in this area.
>>
>> Dave.
>
>
> Whoops, there was a less obvious fallthrough from the _DRM_SHM case above,
> where we do not want to compare offsets at all if it contains a lock(*).
>
> This patch has been tested on savage, and for verification also on radeon
> with DRI1 and DRI2.
>
> Tormod
Hi Dave,
Is this good to go now and I can expect to see it in e.g. drm-next or
are there any issues or doubts?
Cheers,
Tormod
prev parent reply other threads:[~2011-06-10 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 21:54 multiple framebuffer drm maps Tormod Volden
2011-05-03 21:20 ` Tormod Volden
2011-05-03 21:54 ` Tormod Volden
2011-05-22 19:27 ` [PATCH] drm/savage: Do not add framebuffer and aperture maps Tormod Volden
2011-05-27 18:19 ` [PATCH resend] " Tormod Volden
2011-05-27 20:48 ` Dave Airlie
2011-05-27 23:44 ` Tormod Volden
2011-05-29 23:12 ` [PATCH] drm: Compare only lower 32 bits of framebuffer map offsets Tormod Volden
2011-05-29 23:29 ` Dave Airlie
2011-05-30 19:45 ` [PATCH v2] " Tormod Volden
2011-05-31 22:04 ` Tormod Volden
2011-06-10 22:59 ` Tormod Volden [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='BANLkTi=9UDOSvdbSRDLPhyqi99vYVQ7xYw@mail.gmail.com' \
--to=lists.tormod@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.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).