Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1554055ybl; Fri, 13 Dec 2019 17:55:25 -0800 (PST) X-Google-Smtp-Source: APXvYqwK5lQQD2XafHqiGrS0BXMHiznYszLnOi6vOobA7kGYuZcdsAJ0JHkXy8oVT3sMG5hAOLC0 X-Received: by 2002:a05:6830:14d3:: with SMTP id t19mr18770176otq.278.1576288525809; Fri, 13 Dec 2019 17:55:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576288525; cv=none; d=google.com; s=arc-20160816; b=XSnejHwo1rK4uYtdezj7HbTDWqwxy7VGIy/PAou6195DL0cfSwqQQCB06R3SNIGxL3 Wn2PJlh0dixqSujUFD0mbxM2hwW2o1VpsPf9Uhp5PJhy3VL66cEhgSmxubOVFqWUvnLH y1zbhi5yg5lzW7gt47mIw3hN1Tl5BHUKBEGSLW7jVMsXKn9ufWKL/4JsrnWJICJ+RTwb AcVQrtxRFIB9113OehpwXgSN0uBmGjrmvMtNtJT2XHwozgvfmle4etRMFfhxOv2cTik/ 93J9A3bav2or7aacQySjWE86ZAPWN4WVrvfyM3oXdeaks46byrPxXWV4J3Yuya3iNd6y 88Jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=uK0W0JkFAPq/7bzztiplVTmtBzdxeVP9XmfNvkvH2kg=; b=C6XhwfZhL7viHTuE1UbxDlEcLrfDmdy6qH6FVHjFqC/AiiuEXlKDDtz1/xlM6dUTUk VbIK6FGKco56nCKlrIlFXJIJfVoZad1USetiLOg6MgAQTyOnTrU2Q9dz2Db72jkX1tMN wfZiRLhmwmp7XHOOD/nlwjkrfgCleLQ0lUb+NeBhEwxWMzsXeEtd8KAVzfM6UJADSRgZ A88MURdn99Jm1awzZg9uovXLKtyTT+H5mOFzYlnpq7iddIHFJk1uDIf2B4B68MMU2B0A +xC0Q5R5lLTeONf4vDH0v20WJlzOY3j5hr63SwsnYHu++20uZkDw6TOAZFlXb/4qFmkt m6+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si5828900oto.116.2019.12.13.17.55.01; Fri, 13 Dec 2019 17:55:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726671AbfLNBxm (ORCPT + 99 others); Fri, 13 Dec 2019 20:53:42 -0500 Received: from mga12.intel.com ([192.55.52.136]:46750 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726046AbfLNBxm (ORCPT ); Fri, 13 Dec 2019 20:53:42 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Dec 2019 17:53:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,311,1571727600"; d="scan'208";a="226462850" Received: from allen-box.sh.intel.com (HELO [10.239.159.136]) ([10.239.159.136]) by orsmga002.jf.intel.com with ESMTP; 13 Dec 2019 17:53:38 -0800 Cc: baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] iommu/vt-d bad RMRR workarounds To: Barret Rhoden , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , David Woodhouse , Joerg Roedel , Yian Chen , Sohil Mehta References: <20191211194606.87940-1-brho@google.com> <35f49464-0ce5-9998-12a0-624d9683ea18@linux.intel.com> <8a530d5c-22e1-3c2f-98df-45028cc6c771@google.com> From: Lu Baolu Message-ID: <02d69d9a-9c45-d9e7-4c1a-cb5e50590c47@linux.intel.com> Date: Sat, 14 Dec 2019 09:52:50 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <8a530d5c-22e1-3c2f-98df-45028cc6c771@google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/13/19 10:31 PM, Barret Rhoden wrote: > On 12/11/19 9:43 PM, Lu Baolu wrote: >> The VT-d spec defines the BIOS considerations about RMRR in section 8.4: >> >> " >> BIOS must report the RMRR reported memory addresses as reserved (or as >> EFI runtime) in the system memory map returned through methods such as >> INT15, EFI GetMemoryMap etc. >> " >> >> So we should treat it as firmware bug if the RMRR range is not mapped as >> RESERVED in the system memory map table. >> >> As for how should the driver handle this case, ignoring buggy RMRR with >> a warning message might be a possible choice. > > Agreed, firmware should not be doing this.  My first patch just skips > those entries, instead of aborting DMAR processing, and keeps the warning. > Hi Yian, Does this work for you? Best regards, baolu > So long as the machine still boots in a safe manner, I'm reasonably happy. > > Thanks, > > Barret > >