public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	<david.vrabel@citrix.com>, <konrad.wilk@oracle.com>,
	<stefano.stabellini@eu.citrix.com>
Cc: <linux-kernel@vger.kernel.org>, <jun.nakajima@intel.com>,
	<xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH v2 0/2] xen/pci: Use APIC for MSIs when APIC virtualization is supported
Date: Wed, 29 Oct 2014 13:59:42 +0000	[thread overview]
Message-ID: <5450F2CE.8070104@citrix.com> (raw)
In-Reply-To: <1414425953-13987-1-git-send-email-boris.ostrovsky@oracle.com>

On 27/10/14 16:05, Boris Ostrovsky wrote:
> Changes in v2:
> * New version of cpuid.h file from Xen tree (with a couple of style adjustments)
> * Whitespace cleanup
> 
> Currently HVM guests handle MSI interrupts using pirqs/event channels, allowing
> us to not issue APIC accesses that result in somewhat expensive VMEXITs. When
> hardware supports APIC virtualization we don't need to use pirqs anymore
> since now guest's APIC accesses can be handled by the processor itself.
> 
> There are two patches in this series:
> 
> 1. Move setting of x86_msi ops to a later point. The reason for doing so is that
> we currently decide whether or not to use pirqs before kernel had a chance to
> see whether it should be using x2APIC instead of plain APIC. Since hardware may
> virtualize either or both of those two we can only make pirqs vs. APIC selection
> after kernel has settled down on which APIC version it will use. (Note that
> currently x2APIC is not used by HVM guests so technically this patch is not
> necessary. However, it probably makes sense to apply it now to avoid
> forgetting to do it when we enable x2APIC).
> 
> 2. Set x86_msi ops to use pirqs only when APIC virtualization is not available.
> The commit message describes performance improvements that this change brings.
> 
> Boris Ostrovsky (2):
>   xen/pci: Defer initialization of MSI ops on HVM guests until after
>     x2APIC has been set up
>   xen/pci: Use APIC directly when APIC virtualization is supported by
>     hardware

Applied to devel/for-linus-3.19.

Thanks.

David

      parent reply	other threads:[~2014-10-29 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 16:05 [PATCH v2 0/2] xen/pci: Use APIC for MSIs when APIC virtualization is supported Boris Ostrovsky
2014-10-27 16:05 ` [PATCH v2 1/2] xen/pci: Defer initialization of MSI ops on HVM guests until after x2APIC has been set up Boris Ostrovsky
2014-10-27 16:05 ` [PATCH v2 2/2] xen/pci: Use APIC directly when APIC virtualization is supported by hardware Boris Ostrovsky
2014-10-27 18:39   ` Konrad Rzeszutek Wilk
2014-10-27 18:58     ` Boris Ostrovsky
2014-10-29 13:59 ` David Vrabel [this message]

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=5450F2CE.8070104@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jun.nakajima@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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