From mboxrd@z Thu Jan 1 00:00:00 1970 From: Weidong Han Subject: Re: [PATCH] VT-d: improve RMRR validity checking Date: Thu, 21 Jan 2010 20:46:39 +0800 Message-ID: <4B584CAF.10909@intel.com> References: <4B583122.6030002@intel.com> <4B58465C.40508@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B58465C.40508@jp.fujitsu.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: Noboru Iwamatsu Cc: "Cihula, Joseph" , "xen-devel@lists.xensource.com" , "keir.fraser@eu.citrix.com" List-Id: xen-devel@lists.xenproject.org Noboru Iwamatsu wrote: > Hi Weidong, > > I re-send the DRHD-fix patch. > > If DRHD does not have existent devices, ignore it. > If DRHD has both existent and non-existent devices, consider it invalid > and not register. > Although you patch workarounds your buggy BIOS, but we still need to enable it for security purpose as I mentioned in previous mail. We needn't workaround / fix all BIOS issues in software. I think security is more important for this specific BIOS issue. Did you report the BIOS issue to your OEM vendor? maybe it's better to get it fixed in BIOS. Regards, Weidong > According to this patch and yours, my machine successfully booted > with vt-d enabled. > > Signed-off-by: Noboru Iwamatsu > > > >> Keir Fraser wrote: >> >>> On 21/01/2010 10:19, "Weidong Han" wrote: >>> >>> >>>>> Sorry this is typo. >>>>> I mean: >>>>> So, I think RMRR that has no-existent device is "invalid" >>>>> and whole RMRR should be ignored. >>>>> >>>> looks reasonable. >>>> >>>> Keir, I Acks Noboru's rmrr patch. Or do you want us to merge them to one >>>> patch? >>>> >>> Merge them up, re-send with both sign-off and acked-by all in one email. >>> >>> Thanks, >>> Keir >>> >>> >> Sorry, I disagree with Noboru after thinking it again. If the RMRR has >> both no-existent device and also has existent devices in its scope, we >> should not ignore it because the existent devices under its scope will >> be impacted without the RMRR. so I suggest to print a warning instead of >> ignore it. Attached a patch for it. >> >> Signed-off-by: Weidong Han >> > >