From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Airlie <airlied@redhat.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.sf.net" <dri-devel@lists.sf.net>
Subject: Re: [PATCH] vt_buffer: drop console buffer copying optimisations
Date: Fri, 30 Jan 2015 10:14:36 +1000 [thread overview]
Message-ID: <CAPM=9tzbZucODYHAGvXii=8HWeBRNWedAdWgk_mf4wB1s=zo4w@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwNSKEpEGexJbcqpLuRJPLMA2pb9Pr61ikxidwAX3Hcyg@mail.gmail.com>
On 30 January 2015 at 10:03, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Jan 29, 2015 at 3:57 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> I can take this through the tty tree, but can I put it in linux-next and
>> wait for the 3.20 merge window to give people who might notice a
>> slow-down a chance to object?
>
> Yes. The problem only affects one (or a couple of) truly outrageously
> bad graphics cards that are only used in servers (because they are
> such crap that they wouldn't be acceptable anywhere else anyway), and
> they have afaik never worked with 64-bit kernels, so it's not even a
> regression.
>
> So it's worth fixing because it's a real - albeit very rare - problem
> (especially since the enhanched rep instruction model of memcpy could
> easily be *worse* than the 16-bit-at-a-time manual version), but I
> wouldn't consider it anywhere near high priority.
>
Totally not a priority, it just finally got tested for RHEL so I wanted to
make sure I posted it upstream before I forgot about it for months,
I also filed:
https://bugzilla.kernel.org/show_bug.cgi?id=92311
since the RH bug is private and full of crap, that bug contains
a screenshot of the remote console to see what sort of crap it produces.
Dave.
next prev parent reply other threads:[~2015-01-30 0:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 4:11 [PATCH] vt_buffer: drop console buffer copying optimisations Dave Airlie
2015-01-29 12:06 ` Peter Hurley
2015-01-29 23:40 ` Linus Torvalds
2015-01-29 23:57 ` Greg Kroah-Hartman
2015-01-30 0:03 ` Linus Torvalds
2015-01-30 0:14 ` Dave Airlie [this message]
2015-02-03 15:54 ` One Thousand Gnomes
2015-02-05 9:01 ` Geert Uytterhoeven
2015-02-05 11:35 ` One Thousand Gnomes
2015-02-09 10:35 ` Daniel Stone
2015-02-09 10:49 ` Geert Uytterhoeven
2015-02-09 11:00 ` Daniel Stone
2015-02-09 20:17 ` One Thousand Gnomes
2015-02-24 16:49 ` Pavel Machek
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='CAPM=9tzbZucODYHAGvXii=8HWeBRNWedAdWgk_mf4wB1s=zo4w@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sf.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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).