From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Zidar Subject: Re: hypervisor memory usage Date: Wed, 28 Oct 2009 13:02:14 +0100 Message-ID: <4AE832C6.8090309@mindnever.org> References: <4AE828A4.4080601@mindnever.org> <20091028115800.GA1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20091028115800.GA1434@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Sounds possible. However it would be great if there was switch to=20 disable that feature in case hardware is not capable of VT-d, as I'd=20 rather use those 300mb than have software support for something that I=20 can't actually use. Thanks for hints, you were very helpful. I'll dig more into rhel/centos xen sources to look for any reference to=20 vt-d. Pasi K=E4rkk=E4inen wrote: >> I understand that this could be due to rhel patches, and maybe=20 >> doesn't relate to official xen builds, but I'd like to know if this=20 >> issue was known or not before jumping into xen 3.4 - as it won't be=20 >> direct rpm/yum upgrade path. >> >> =20 > > RHEL 5.4 (-164 kernel) added more support for VT-d etc, so maybe that's= why > more DMA memory is reserved. dunno. > > -- Pasi > =20