From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v2 4/5] Viridian: populate CPUID leaf 6 Date: Thu, 4 Jul 2013 11:18:27 +0100 Message-ID: <51D54BF3.5020500@citrix.com> References: <51C8092A02000078000DFDA0@nat28.tlf.novell.com> <51C80C3102000078000DFDC6@nat28.tlf.novell.com> <51D54282.6080907@citrix.com> <51D564FC02000078000E2B49@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51D564FC02000078000E2B49@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Keir Fraser , GeorgeDunlap , Eddie Dong , xen-devel , paul.durrant@citrix.com, Jun Nakajima , Yang ZZhang List-Id: xen-devel@lists.xenproject.org On 04/07/13 11:05, Jan Beulich wrote: >>>> On 04.07.13 at 11:38, Andrew Cooper wrote: >> On 24/06/13 08:06, Jan Beulich wrote: >>> Properly reporting hardware features we use can only help Windows in >>> making decisions towards its own performance tuning. >>> >>> Signed-off-by: Jan Beulich >> Does viridian allow for the possibility of these flags to change during >> runtime, e.g. migrating an HVM domain from hardware supporting HAP to >> hardware which can only manage shadow? > Don't know, but this is only reporting capabilities of the hypervisor, > so if they store those anywhere for any purpose they wouldn't > have migration in mind even on their own hypervisor. > > Jan > Very true. Reviewed-by: Andrew Cooper