All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Takashi Iwai <tiwai@suse.de>, David Airlie <airlied@redhat.com>,
	christian.koenig@amd.com,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance regression in ast drm driver
Date: Tue, 13 Nov 2018 13:08:21 +0100	[thread overview]
Message-ID: <20181113130821.2a7694a6@endymion> (raw)
In-Reply-To: <89ae9adf-27e7-ae80-639c-c67202a0d0b7@suse.de>

Hi Thomas,

On Tue, 13 Nov 2018 10:23:45 +0100, Thomas Zimmermann wrote:
> ast doesn't remove the vesafb's framebuffer before attaching to the
> device. I have a patch at [1]. If you have a way of testing it, I'd
> appreciate.
> 
> [1] https://bugzilla.suse.com/show_bug.cgi?id=1112963

Thank you very much for looking into this bug. I tested the patch above
and yes, it solves my console performance problem. The performance with
your patch applied is roughly the same as with commit "drm/drivers: add
support for using the arch wc mapping API" reverted.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2018-11-13 12:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 15:27 Performance regression in ast drm driver Jean Delvare
2018-11-08 12:05 ` Jean Delvare
2018-11-09  0:04   ` David Airlie
2018-11-10  8:39     ` Jean Delvare
2018-11-12 14:36     ` Jean Delvare
2018-11-12 14:45       ` Takashi Iwai
2018-11-12 16:41         ` Jean Delvare
2018-11-13  9:23           ` Thomas Zimmermann
2018-11-13  9:23             ` Thomas Zimmermann
2018-11-13 12:08             ` Jean Delvare [this message]
2018-11-13 12:16               ` Thomas Zimmermann
2018-11-13 12:16                 ` Thomas Zimmermann
2018-11-12 19:36       ` Thomas Zimmermann
2018-11-13  8:19   ` YC Chen
2018-11-13  8:19     ` YC Chen

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=20181113130821.2a7694a6@endymion \
    --to=jdelvare@suse.de \
    --cc=airlied@redhat.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=tzimmermann@suse.de \
    /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.