[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v3 3/3] tools: introduce parameter max_wp_ram_ranges.
- To: "Paul Durrant" <Paul.Durrant@xxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Fri, 05 Feb 2016 03:41:15 -0700
- Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, Zhang Yu <yu.c.zhang@xxxxxxxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxx>, "zhiyuan.lv@xxxxxxxxx" <zhiyuan.lv@xxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxx>, "Keir \(Xen.org\)" <keir@xxxxxxx>
- Delivery-date: Fri, 05 Feb 2016 10:41:24 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 05.02.16 at 10:24, <Paul.Durrant@xxxxxxxxxx> wrote:
> Utilizing the default server is a backwards step. GVT-g would have to use the
> old HVM_PARAM mechanism to cause it's emulator to become default. I think a
> more appropriate mechanism would be p2m_mmio_write_dm to become something
> like 'p2m_ioreq_server_write' and then have a hypercall to allow it to be
> mapped to a particular ioreq server.
> Obviously only one could claim it but, with a p2t, the bit could be
> re-purposed to simply mean 'go look in the p2t' for more information and
> then the p2t could be structured to allow emulations to be steered to one of
> many ioreq servers (for read and/or write emulation).
Sounds reasonable.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
