From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Chen, Tiejun" <tiejun.chen@intel.com>
Subject: Re: [v7][PATCH 06/16] hvmloader/pci: skip reserved
	ranges
Date: Wed, 15 Jul 2015 19:34:37 +0800
Message-ID: <55A6454D.2000201@intel.com>
References: <1436420047-25356-1-git-send-email-tiejun.chen@intel.com>
	<1436420047-25356-7-git-send-email-tiejun.chen@intel.com>
	<55A3D5600200007800090330@mail.emea.novell.com>
	<55A4AE88.2000200@intel.com>
	<55A4F2270200007800090834@mail.emea.novell.com>
	<55A4EA54.60708@intel.com>
	<55A5138F0200007800090A71@mail.emea.novell.com>
	<55A5AF6F.1050305@intel.com> <55A5E122.7030203@intel.com>
	<55A6374E02000078000911EC@mail.emea.novell.com>
	<55A6210E.8080406@intel.com>
	<55A64386020000780009132E@mail.emea.novell.com>
	<55A6374F.6030901@intel.com>
	<55A65F620200007800091472@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55A65F620200007800091472@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>
List-Id: xen-devel@lists.xenproject.org

>> Maybe I  can move this chunk of codes downward those actual allocation
>> to check if RDM conflicts with the final allocation, and then just
>> disable those associated devices by writing PCI_COMMAND without BUG()
>> like this draft code,
>
> And what would keep the guest from re-enabling the device?
>

We can't but IMO,

#1. We're already posting that warning messages.

#2. Actually this is like this sort of case like, as you known, even in 
the native platform, some broken devices are also disabled by BIOS, 
right? So I think this is OS's responsibility or risk to force enabling 
such a broken device.

#3. Its really rare possibility in real world.

Thanks
Tiejun