From mboxrd@z Thu Jan 1 00:00:00 1970 From: Noboru Iwamatsu Subject: Re: [PATCH] VT-d: improve RMRR validity checking Date: Tue, 26 Jan 2010 10:16:38 +0900 Message-ID: <4B5E4276.90308@jp.fujitsu.com> References: <4B5DA659.1030506@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B5DA659.1030506@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: weidong.han@intel.com, keir.fraser@eu.citrix.com Cc: linux@eikelenboom.it, joseph.cihula@intel.com, xen-devel@lists.xensource.com, allen.m.kay@intel.com List-Id: xen-devel@lists.xenproject.org Weidong, Keir, I agree your suggestions. Noboru. > Keir Fraser wrote: >> On 25/01/2010 10:45, "Sander Eikelenboom" wrote: >> >>> a) Could be discussed if panic should be default instead of disabling >>> iommu or >>> not, although there seem to be a lot of broken bioses, so that would >>> lead to a >>> lot of machines not booting. >> >> Absolutely not acceptable. Warn and completely disable IOMMU is the >> correct >> default causing least pain to the most end users. >> >> -- Keir >> > Agree. It should not crash Xen by default due to BIOS issues. > warn-and-disable is better. It won't impact common Xen users, and if a > user really wants to use VT-d, he can try iommu=workaround_bogus_bios, > or directly report to OEM vendor to get it fixed in BIOS. As VT-d is > used more and more widely, I think the BIOS issues will be found and > fixed more quickly than before, thus the situation should be better. > > Regards, > Weidong > > >