Julien Grall julien.gr...@citrix.com 04/25/15 10:37 PM
On 21/04/2015 20:13, Jan Beulich wrote:
For this specific one - is there a reasonable use case? Other than
for host PFN, we have control over guest ones, and I'm not sure
managing a guest with GPFNs extending past 4 billion can be
Hi Jan,
On 27/04/2015 08:02, Jan Beulich wrote:
Julien Grall julien.gr...@citrix.com 04/25/15 10:37 PM
On 21/04/2015 20:13, Jan Beulich wrote:
For this specific one - is there a reasonable use case? Other than
for host PFN, we have control over guest ones, and I'm not sure
managing a guest
Hi Jan,
On 21/04/2015 20:13, Jan Beulich wrote:
For this specific one - is there a reasonable use case? Other than
for host PFN, we have control over guest ones, and I'm not sure
managing a guest with GPFNs extending past 4 billion can be
expected to work if only this one hypercall got fixed.
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops, XENMEM_current_reservation,
XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as an
int. However, in ARM64 we could potentially have
On Tue, Apr 21, 2015 at 4:29 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 16:24, ian.campb...@citrix.com wrote:
On Tue, 2015-04-21 at 15:14 +0100, Jan Beulich wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On Tue, Apr 21, 2015 at 5:13 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 16:42, tkleng...@sec.in.tum.de wrote:
On Tue, Apr 21, 2015 at 4:29 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 16:24, ian.campb...@citrix.com wrote:
On Tue, 2015-04-21 at 15:14 +0100, Jan
On Tue, 2015-04-21 at 15:29 +0100, Jan Beulich wrote:
On 21.04.15 at 16:24, ian.campb...@citrix.com wrote:
On Tue, 2015-04-21 at 15:14 +0100, Jan Beulich wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15
On 21.04.15 at 16:33, tkleng...@sec.in.tum.de wrote:
On Tue, Apr 21, 2015 at 4:14 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current
On 21.04.15 at 16:42, tkleng...@sec.in.tum.de wrote:
On Tue, Apr 21, 2015 at 4:29 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 16:24, ian.campb...@citrix.com wrote:
On Tue, 2015-04-21 at 15:14 +0100, Jan Beulich wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops, XENMEM_current_reservation,
XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as
On Tue, 2015-04-21 at 15:14 +0100, Jan Beulich wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops, XENMEM_current_reservation,
On 21.04.15 at 16:24, ian.campb...@citrix.com wrote:
On Tue, 2015-04-21 at 15:14 +0100, Jan Beulich wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of
On Tue, Apr 21, 2015 at 4:14 PM, Jan Beulich jbeul...@suse.com wrote:
On 21.04.15 at 15:23, ian.campb...@citrix.com wrote:
On Mon, 2015-04-20 at 16:22 +0100, Andrew Cooper wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops,
The current implementation of three memops, XENMEM_current_reservation,
XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as an
int. However, in ARM64 we could potentially have 36-bit pfn's, thus
in preparation for the ARM patch, in this patch we update the existing
memop routines
On Mon, Apr 20, 2015 at 5:22 PM, Andrew Cooper andrew.coop...@citrix.com
wrote:
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops, XENMEM_current_reservation,
XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as an
int. However, in ARM64 we
On 20/04/15 16:06, Tamas K Lengyel wrote:
The current implementation of three memops, XENMEM_current_reservation,
XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as an
int. However, in ARM64 we could potentially have 36-bit pfn's, thus
in preparation for the ARM patch, in this
16 matches
Mail list logo
