From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 5/8] xen/i386: make sure initial VGA/ISA mappings are not overridden
Date: Fri, 08 May 2009 08:08:48 -0700 [thread overview]
Message-ID: <4A044B00.7060003@goop.org> (raw)
In-Reply-To: <20090508105728.GB11596@elte.hu>
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.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?
>
No, it only matters if the ISA region is mapping real hardware. For
domU we set up a set of dummy maps for ISA to mop up any stray
references, but they have no connection to underlying hardware.
This area is all a bit ugly, and I hope to ultimately address it by
making 32 and 64-bit use the same code for setting up the kernel
mappings (as the 64-bit code doesn't try to double-map the ISA area).
>> 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)
>
OK. I guess Diagnosed-by: would be the most appropriate tag in this case.
>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.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.)
>
OK, they're footers now?
Do you want me to respin these patches and repost?
J
next prev parent reply other threads:[~2009-05-08 15:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 20:24 [GIT PULL] Xen core updates Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 1/8] xen/x86-64: fix breakpoints and hardware watchpoints Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 2/8] xen/x86-64: clean up warnings about IST-using traps Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 3/8] xen: cache cr0 value to avoid trap'n'emulate for read_cr0 Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 4/8] xen: deal with NMI's use of IST too Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 5/8] xen/i386: make sure initial VGA/ISA mappings are not overridden Jeremy Fitzhardinge
2009-05-08 10:57 ` Ingo Molnar
2009-05-08 15:08 ` Jeremy Fitzhardinge [this message]
2009-05-07 20:25 ` [PATCH 6/8] x86: use flush_tlb_others to implement flush_tlb_all Jeremy Fitzhardinge
2009-05-08 15:24 ` Ian Campbell
2009-05-08 15:49 ` Jeremy Fitzhardinge
2009-05-08 15:52 ` Ian Campbell
2009-05-11 13:09 ` [tip:x86/xen] x86: use flush_tlb_others to implement flush_tlb_all, fix tip-bot for Ian Campbell
2009-05-11 13:12 ` Ingo Molnar
2009-05-11 15:00 ` Ian Campbell
2009-05-11 15:11 ` Ingo Molnar
2009-05-11 15:39 ` Ian Campbell
2009-05-11 15:42 ` Ingo Molnar
2009-05-11 15:59 ` Ian Campbell
2009-05-11 15:40 ` Ingo Molnar
2009-05-11 15:06 ` tip-bot for Ian Campbell
2009-05-07 20:25 ` [PATCH 7/8] xen/i386: reserve Xen pagetables Jeremy Fitzhardinge
2009-05-07 20:25 ` [PATCH 8/8] xen: reserve Xen start_info rather than e820 reserving Jeremy Fitzhardinge
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=4A044B00.7060003@goop.org \
--to=jeremy@goop.org \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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