[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070810192543.605f350f@the-village.bc.nu>
Date: Fri, 10 Aug 2007 19:25:43 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: "Glauber de Oliveira Costa" <glommer@...il.com>
Cc: "Jeremy Fitzhardinge" <jeremy@...p.org>, lguest@...abs.org,
linux-kernel@...r.kernel.org, chrisw@...s-sol.org,
anthony@...emonkey.ws, Steven@...p2.linux-foundation.org,
akpm@...ux-foundation.org,
"Glauber de Oliveira Costa" <gcosta@...hat.com>,
virtualization@...ts.linux-foundation.org, mingo@...e.hu
Subject: Re: [PATCH 23/25] [PATCH] paravirt hooks for arch initialization
On Fri, 10 Aug 2007 15:08:35 -0300
"Glauber de Oliveira Costa" <glommer@...il.com> wrote:
> On 8/9/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > > What's the EBDA actually used for? The only place which seems to use
> > > ebda_addr is in the e820 code to avoid that area as RAM.
> >
> > It belongs to the firmware.
>
> Wouldn't it be better, then, to just skip this step unconditionally if
> we are running a paravirtualized guest? What do we from doing it?
An EBDA is an optional BIOS feature so providing you virtualise the
relevant entry in the zero page (to avoid guest applications trying to
scan the EBDA for some system tables they may want to use like DMI) as
a zero entry you can ignore the EBDA.
That probably the right thing to do since the host EBDA won't match the
guest environment and the guest might migrate anyway
-
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