xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Eddie Dong <eddie.dong@intel.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: [PATCH v2 2/5] VMX/Viridian: suppress MSR-based APIC suggestion when having APIC-V
Date: Tue, 25 Jun 2013 14:43:34 +0100	[thread overview]
Message-ID: <51C99E86.1020506@eu.citrix.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0051253@LONPEX01CL01.citrite.net>

On 06/25/2013 11:29 AM, Paul Durrant wrote:
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: 24 June 2013 08:05
>> To: xen-devel
>> Cc: Paul Durrant; George Dunlap; Eddie Dong; Jun Nakajima; Yang Z Zhang;
>> Keir (Xen.org)
>> Subject: [PATCH v2 2/5] VMX/Viridian: suppress MSR-based APIC suggestion
>> when having APIC-V
>>
>> When the CPU has the necessary capabilities, having Windows use
>> synthetic MSR reads/writes is bogus, as this still requires emulation
>> (which is pretty much guaranteed to be slower than having the hardware
>> carry out the operation).
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>
>
> Seems better just to not use the MSR in this case so I favour this patch over #1, hence
>
> Ack-ed by: Paul Durrant <paul.durrant@citrix.com>

This may push this over into the "#2 is probably a better idea" 
category; Paul, Yang, and Jan all think it's less intrusive.

Jan, I think it's your call -- You have an ack from me to put either #1 
or #2 in for 4.3 (but please not both).

  -George

  reply	other threads:[~2013-06-25 13:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  6:54 [PATCH v2 0/5] VMX: fix interaction of Viridian emulation with advanced features Jan Beulich
2013-06-24  7:03 ` [PATCH v2 1/5] VMX: fix interaction of APIC-V and Viridian emulation Jan Beulich
2013-06-24 10:10   ` George Dunlap
2013-06-24 12:52     ` Jan Beulich
2013-06-24 13:09       ` George Dunlap
2013-06-24 13:26         ` Jan Beulich
2013-06-24 13:29           ` George Dunlap
2013-06-24 13:48             ` Jan Beulich
2013-07-04  9:03   ` Andrew Cooper
2013-06-24  7:04 ` [PATCH v2 2/5] VMX/Viridian: suppress MSR-based APIC suggestion when having APIC-V Jan Beulich
2013-06-25 10:29   ` Paul Durrant
2013-06-25 13:43     ` George Dunlap [this message]
2013-06-25 13:59       ` Jan Beulich
2013-06-24  7:06 ` [PATCH v2 3/5] VMX: suppress pointless indirect calls Jan Beulich
2013-07-04  9:10   ` Andrew Cooper
2013-06-24  7:06 ` [PATCH v2 4/5] Viridian: populate CPUID leaf 6 Jan Beulich
2013-07-04  9:38   ` Andrew Cooper
2013-07-04 10:05     ` Jan Beulich
2013-07-04 10:18       ` Andrew Cooper
2013-06-24  7:08 ` [PATCH v2 5/5] Viridian: cleanup Jan Beulich
2013-07-04  9:38   ` Andrew Cooper
2013-07-04  8:38 ` [PATCH v2 0/5] VMX: fix interaction of Viridian emulation with advanced features Jan Beulich
2013-07-04  9:24   ` Zhang, Yang Z

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51C99E86.1020506@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).