[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] vesafb



<<However, doing one or two calls back to real mode before
 dom0 even starts to execute should definitely not be a problem 
>>

Ok.. We will test this solution.

I am curious,

Why else would you be jumping into real mode after/before the Dom0
creation?

-Kaushik


-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
Sent: Tuesday, May 08, 2007 1:07 PM
To: Kaushik Barde; Jan Beulich
Cc: ron minnich; Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx; Jayant
Mangalampalli
Subject: Re: [Xen-devel] vesafb

On 8/5/07 20:20, "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx> wrote:

> I Agree with Kier.
> 
> And from our experience (Phoenix) BIOS reserved areas usually aren't
> clobbered (except for a vendor specific BIOS/system customizations)
> 
> I am also not sure about why can't we create Dom0 interface changes?
> 
> Like I presented in my email earlier, is following ok?

Jan's specific concerns are relating to interrupts, NMIs and
machine-check
exceptions, if we return to real-mode at arbitrary times after the
machine
has finished booting. Those concerns are quite reasonable (but, I think,
work-aroundable). However, doing one or two calls back to real mode
before
dom0 even starts to execute should definitely not be a problem - that's
not
what is being argued against here.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.