[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] (v2) Design proposal for RMRR fix
- To: "George Dunlap" <george.dunlap@xxxxxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Thu, 15 Jan 2015 08:37:30 +0000
- Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, "wei.liu2@xxxxxxxxxx" <wei.liu2@xxxxxxxxxx>, "ian.campbell@xxxxxxxxxx" <ian.campbell@xxxxxxxxxx>, "stefano.stabellini@xxxxxxxxxxxxx" <stefano.stabellini@xxxxxxxxxxxxx>, "tim@xxxxxxx" <tim@xxxxxxx>, "ian.jackson@xxxxxxxxxxxxx" <ian.jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, YangZ Zhang <yang.z.zhang@xxxxxxxxx>, TiejunChen <tiejun.chen@xxxxxxxxx>
- Delivery-date: Thu, 15 Jan 2015 08:38:07 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 14.01.15 at 19:29, <george.dunlap@xxxxxxxxxxxxx> wrote:
> Just to be clear -- what we're talking about here is that at the
> do_domain_create() level (called by libxl_domain_create_new()), it will
> take a list of pci devices, and the rmrr list above (including "host"
> and individual ranges), and generate a list of RMRRs to pass to the
> lower layer. The lower layer will simply see the range, and a "force /
> no force" flag, and behave appropriately. The determination of which
> RMRRs to force will be done at the domain_create level.
>
> Is that about right?
That's certainly a sensible model.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
