[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks

To: "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Thu, 05 Jan 2017 05:23:24 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Thu, 05 Jan 2017 12:23:32 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 04.01.17 at 13:39, <andrew.cooper3@xxxxxxxxxx> wrote:
> ... rather than dynamically claming against the PV maximum policy.

What is "claming"? I'm even having a hard time guessing what you
may have meant - clamping maybe?

> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks
  - From: Andrew Cooper

References:
- [Xen-devel] [PATCH 00/27] xen/x86: Per-domain CPUID policies
  - From: Andrew Cooper
- [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks
  - From: Andrew Cooper

Prev by Date: Re: [Xen-devel] [PATCH 2/2] x86/pv: Defer I/O bitmap checks even in 64bit mode for emulate_privilege_op()
Next by Date: Re: [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks
Previous by thread: [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks
Next by thread: Re: [Xen-devel] [PATCH 17/27] x86/pv: Use per-domain policy information when calculating the cpumasks
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.