From: Greg KH <greg@kroah.com>
To: Marc Aurele La France <tsi@ualberta.ca>
Cc: hpa@kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org, "H. Peter Anvin" <hpa@linux.intel.com>,
Research.Support@ualberta.ca
Subject: Re: [rs] Re: [stable] [PATCH] x86, setup (2.6.30-stable) fix 80x34 and 80x60 console modes
Date: Tue, 30 Jun 2009 08:43:36 -0700 [thread overview]
Message-ID: <20090630154336.GE16038@kroah.com> (raw)
In-Reply-To: <alpine.WNT.1.10.0906300743550.2004@cluij.ucs.ualberta.ca>
On Tue, Jun 30, 2009 at 08:01:47AM -0600, Marc Aurele La France wrote:
> On Mon, 29 Jun 2009, H. Peter Anvin wrote:
> > Greg KH wrote:
> >> On Mon, Jun 29, 2009 at 06:27:40PM -0700, H. Peter Anvin wrote:
> >>> Marc Aurele La France wrote:
> >>>> As coded, most INT10 calls in video-vga.c allow the compiler to assume EAX
> >>>> remains unchanged across them, which is not always the case. This
> >>>> triggers an optimisation issue that causes vga_set_vertical_end() to be
> >>>> called with an incorrect number of scanlines. Fix this by beefing up the
> >>>> asm constraints on these calls.
>
> >>>> Reported-by: Marc Aurele La France <tsi@xfree86.org>
> >>>> Signed-off-by: Marc Aurele La France <tsi@xfree86.org>
> >>>> Acked-by: H. Peter Anvin <hpa@zytor.com>
>
> >>> Note: this is not in upstream since upstream is not affected due to the
> >>> new "BIOS glovebox" subsystem.
>
> >> So it is a ".30 only" type patch? Any older kernel versions affected?
>
> > Yes, all the way back to .23 or something like that.
>
> No. The problem can only arise in 2.6.30 and is a consequence of commit
> 5f641356127712fbdce0eee120e5ce115860c17f. It disappears with subsequent
> mainline commit cf06de7b9cdd3efee7a59dced1977b3c21d43732.
>
> Prior to 2.6.30, vga_set_480_scanlines() was passed a byte-size value (as
> an int), which means the compiler was forced to load EAX, instead of only
> AL, even if it did assume AH still contained 0x01. That 0x01 is what the
> last INT10 call in the vga_set_{8,14}font() functions sets AH to.
>
> In truth, only those two INT10's need beefing up. But I did them all for
> completeness.
Ah, thanks. Next time, putting that information into the patch itself
would be most helpful :)
I'll go queue it up.
greg k-h
prev parent reply other threads:[~2009-06-30 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 0:07 [PATCH] x86, setup (2.6.30-stable) fix 80x34 and 80x60 console modes Marc Aurele La France
2009-06-30 1:27 ` H. Peter Anvin
2009-06-30 3:48 ` [stable] " Greg KH
2009-06-30 6:33 ` H. Peter Anvin
2009-06-30 14:01 ` [rs] " Marc Aurele La France
2009-06-30 15:43 ` Greg KH [this message]
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=20090630154336.GE16038@kroah.com \
--to=greg@kroah.com \
--cc=Research.Support@ualberta.ca \
--cc=hpa@kernel.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tsi@ualberta.ca \
--cc=x86@kernel.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