public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [pull] radeon drm-fixes-3.15
Date: Mon, 19 May 2014 10:49:58 +0200	[thread overview]
Message-ID: <5379C5B6.5020201@amd.com> (raw)
In-Reply-To: <CAPM=9tzbbbAmEkhLoJYFTyXHMEHRqhpnqP7P-UzGMZiibH=3sQ@mail.gmail.com>

Am 19.05.2014 01:04, schrieb Dave Airlie:
> On 16 May 2014 23:54, Christian König <christian.koenig@amd.com> wrote:
>> Hi Dave,
>>
>> this is the next pull quested for stashed up radeon fixes for 3.15.
>>
>> Highlights are:
>> 1. Avoid sending SIGBUS on CPU access just because kernel can't handle
>> buffer placement.
>> 2. Some fixes for VM page table updates and buffer placements.
>> 3. Fixing two typos in the PLL and SI register spec.
>> 4. Checking VCE buffers ranges.
>> 5. Adding a mutex for I2C access.
>> 6. Mullins and non-VGA pci class fixes from Alex.
> This is starting to feel a bit large, we should be in regression
> fixing, oopses and black screens at this point,
>
> The main ones I'm concerned about are the VCE buffer ranges and i2c
> mutex, whether these fix known problems or issues,

For the VCE buffer range checks that fixed a lockup I experienced while 
working on the userspace driver (VCE writing over the end of a buffer 
into an shader, GPU then trying to execute the messed up shader 
code...). Apart from that VCE is a new feature for 3.15 so we can't 
really break it compared to 3.14.

I can't judge on the I2C mutex since that was Alex suggestion and I'm 
not sure how invasive and/or necessary this is.

Regards,
Christian.

>
> Dave.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-05-19  8:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 13:54 [pull] radeon drm-fixes-3.15 Christian König
2014-05-18 23:04 ` Dave Airlie
2014-05-19  8:49   ` Christian König [this message]
2014-05-19 14:01     ` Deucher, Alexander
  -- strict thread matches above, loose matches on Subject: below --
2014-06-02 13:17 Christian König
2014-05-30 12:23 Christian König
2014-05-20 13:14 Christian König
2014-05-26  7:12 ` Malte Schröder
2014-05-26  7:39   ` Christian König
2014-05-06 10:32 Christian König
2014-05-01 13:47 Christian König
2014-05-05  0:51 ` Dave Airlie
2014-05-05  9:04   ` Christian König
2014-05-05 12:48     ` Deucher, Alexander
2014-04-22 16:49 Christian König
2014-04-17 12:40 Christian König

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=5379C5B6.5020201@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.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