All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/1] drm/i915: Fix VGA handling using stop_machine() or mmio
Date: Mon, 7 Oct 2013 09:34:25 +0200	[thread overview]
Message-ID: <CAKMK7uFMzUG-u33z7kjRj378GoSX3BjLixrQePAjkud5ghvoZA@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tzK0sNYxiePW6-Agx7QH-NBmw-Q6YVa1d6JT0ydpEXzTQ@mail.gmail.com>

On Mon, Oct 7, 2013 at 2:23 AM, Dave Airlie <airlied@gmail.com> wrote:
> I'm think I'm going to make an executive decision to merge Ville's
> latest patch to avoid the regression, the other option being just to
> revert everything back to the status quo by reverting all the patches
> from the past few months, if people are happier with that then maybe
> we should just do that for now and try and design our way out of it
> properly by reengineering userspace and plan to avoid the regression
> next time.

Ack on merging Ville's hack. Longer-term we could beautify the pig a
bit by moving it into vgaarb.c and avoiding the stop_machine if no one
else has a vga lock. And I think in next we could try to limit the vga
redisable hack in the lid notifier a bit on more modern platforms to
avoid the dreaded stop_machine at runtime and relegate it to just
resume/driver load.

Really long term (once broken X servers have died) we can try to rip
this hack out again. Or maybe intel hw engineers get their act
together beforehand ;-)

So can you directly pick it up since I've just flushed out my -fixes queue?

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-10-07  7:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 14:08 [PATCH 0/1] drm/i915: Another version of the vga stop_machine monstrosity ville.syrjala
2013-09-30 14:08 ` [PATCH v2 1/1] drm/i915: Fix VGA handling using stop_machine() or mmio ville.syrjala
2013-09-30 14:24   ` Chris Wilson
2013-09-30 14:41     ` Ville Syrjälä
2013-09-30 14:53       ` Chris Wilson
2013-09-30 15:10         ` Ville Syrjälä
2013-09-30 16:45           ` Chris Wilson
2013-09-30 18:37     ` Alex Williamson
2013-10-07  0:23       ` Dave Airlie
2013-10-07  7:34         ` Daniel Vetter [this message]
2013-10-02 13:42     ` [PATCH v3] " ville.syrjala
2013-10-07  9:15       ` Chris Wilson
2013-10-07  9:25         ` Ville Syrjälä
2013-10-07  9:44           ` Chris Wilson
2013-09-30 14:43   ` [PATCH v2 1/1] " Alex Williamson
2013-09-30 15:09     ` Ville Syrjälä
2013-09-30 16:45       ` Alex Williamson
2013-09-30 17:23         ` Ville Syrjälä

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=CAKMK7uFMzUG-u33z7kjRj378GoSX3BjLixrQePAjkud5ghvoZA@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.