[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090508105728.GB11596@elte.hu>
Date: Fri, 8 May 2009 12:57:28 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xen-devel <xen-devel@...ts.xensource.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: [PATCH 5/8] xen/i386: make sure initial VGA/ISA mappings are
not overridden
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
>
> arch/x86/mm/init_32.c overrides the ISA/VGA mappings with direct mappings
> which do not have _PAGE_IOMAP set, thereby making the ISA space inaccessible.
>
> This patch adds to the existing hack to make sure the
> pre-constructed ISA mappings are not incorrectly overwritten.
>
> This makes 32-bit dom0 VGA work properly.
I'm wondering, should we add this fix to .30 as well, is there any
relevancy beyond dom0?
> Thanks to Gerd Hoffman for pointing this out.
Please add Reported-by lines in such cases. That way not only does
the reporting get reported prominently, but the tip-bot will Cc:
Gerd too on the commit notification too. (which will sometimes spur
further comments - while a commit hidden somewhere might not)
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Please also add impact-footers to all commits you queue up, if you
want me to pull your tree directly. I can only guess at the impact
of this one, is it:
[ Impact: fix dom0-Xen-guest boot crash ]
or:
[ Impact: fix dom0-Xen-guest non-working VGA console ]
?
(Please look at latest tip/master for examples about various impact
lines, their precise format, and what we try to describe in them and
how.)
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists