From: Thomas Hellstrom <thellstrom@vmware.com>
To: Ilija Hadzic <ihadzic@research.bell-labs.com>
Cc: Dave Airlie <airlied@redhat.com>,
linux-graphics-maintainer@vmware.com,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Breakage in "track dev_mapping in more robust and flexible way"
Date: Fri, 26 Oct 2012 10:11:05 +0200 [thread overview]
Message-ID: <508A4599.80507@vmware.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1210251622110.394@umail>
Hi,
On 10/25/2012 11:27 PM, Ilija Hadzic wrote:
>
> Can you give the attached patch a whirl and let me know if it fixes
> the problem?
>
> As I indicated in my previous note, vmwgfx should be the only affected
> driver because it looks at dev_mapping in the open hook (others do it
> when they create an object, so they are not affected).
>
> I'll probably revise it (and I'll have some general questions about
> drm_open syscall) before officially send the patch, but I wanted to
> get something quickly to you to check if it fixes your problem. I hope
> that your vmwgfx test environment is such that you can reproduce the
> original
> problem.
>
> thanks,
>
> -- Ilija
Yes, it appears like this patch fixes the problem. It'd be good to have
it in 3.7 (drm-fixes) with a cc to stable.
/Thomas
next prev parent reply other threads:[~2012-10-26 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 14:02 Breakage in "track dev_mapping in more robust and flexible way" Thomas Hellstrom
2012-10-25 14:41 ` Jerome Glisse
2012-10-25 15:10 ` Thomas Hellström
2012-10-25 17:12 ` Ilija Hadzic
2012-10-25 17:31 ` Ilija Hadzic
2012-10-25 18:27 ` Thomas Hellström
2012-10-25 21:27 ` Ilija Hadzic
2012-10-26 8:11 ` Thomas Hellstrom [this message]
2012-10-26 13:14 ` Ilija Hadzic
2012-10-29 8:39 ` Thomas Hellstrom
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=508A4599.80507@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ihadzic@research.bell-labs.com \
--cc=linux-graphics-maintainer@vmware.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;
as well as URLs for NNTP newsgroup(s).