public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 0/7] PV on HVM: receive interrupts as xen events
Date: Thu, 02 Sep 2010 12:04:24 -0700	[thread overview]
Message-ID: <4C7FF538.7020704@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1008301134160.2545@kaball-desktop>

 On 08/30/2010 04:20 AM, Stefano Stabellini wrote:
> Hi all,
> this patch series introduces some performance improvements for xen PV on
> HVM guests: interacting with the emulated APIC is slow because it causes
> traps in the hypervisor while receiving xen events using the vector callback
> mechanism allow us to skip all that. For this reason we remap interrupts
> and MSIs into xen pirqs so that from that point on we can receive them
> as xen events instead.
> This series is based on Konrad's pcifront series (not upstream yet):
>
> http://lkml.org/lkml/2010/8/4/374
>
> and requires a patch to xen and a patch to qemu-xen (just sent to
> xen-devel).

My only concern with this series is the pirq remapping stuff.  Why do
pirq and irq need to be non-identical?  Is it because pirq is a global
namespace, and dom0 has already assigned it?

Why do guests need to know about max pirq?  Would it be better to make
Xen use a more dynamic structure for pirqs so that any arbitrary value
can be used?

    J

>
> The list of patches with diffstat follows:
>
> Jeremy Fitzhardinge (2):
>  xen: add xen hvm acpi_register_gsi variant
>  acpi: use indirect call to register gsi in different modes
>
> Stefano Stabellini (5):
>  xen: xen: map MSIs into pirqs
>  xen: support GSI -> pirq remapping in PV on HVM guests
>  xen: implement xen_hvm_register_pirq
>  xen: get the maximum number of pirqs from xen
>  xen: support pirq != irq
>
>
>  arch/x86/include/asm/acpi.h      |    3 +
>  arch/x86/include/asm/xen/pci.h   |   10 +++
>  arch/x86/kernel/acpi/boot.c      |   60 ++++++++++++++------
>  arch/x86/pci/xen.c               |  114 ++++++++++++++++++++++++++++++++++++++
>  drivers/pci/xen-pcifront.c       |    2 +-
>  drivers/xen/events.c             |  106 +++++++++++++++++++++++++++++++----
>  include/xen/events.h             |    3 +
>  include/xen/interface/features.h |    3 +
>  include/xen/interface/physdev.h  |   36 ++++++++++++
>  9 files changed, 308 insertions(+), 29 deletions(-)
>
>
> A git tree with this series and Konrad's pcifront series on top of Linux
> 2.6.36-rc1 is available here:
>
> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 2.6.36-rc1-pvhvm-pirq-v3
>
> Cheers,
>
> Stefano Stabellini
>


  parent reply	other threads:[~2010-09-02 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 11:20 [PATCH 0/7] PV on HVM: receive interrupts as xen events Stefano Stabellini
2010-08-30 11:21 ` [PATCH 1/7] xen: support pirq != irq stefano.stabellini
2010-08-30 11:21 ` [PATCH 2/7] xen: get the maximum number of pirqs from xen stefano.stabellini
2010-08-30 11:21 ` [PATCH 3/7] xen: implement xen_hvm_register_pirq stefano.stabellini
2010-08-30 11:21 ` [PATCH 4/7] acpi: use indirect call to register gsi in different modes stefano.stabellini
2010-10-06 17:00   ` Stefano Stabellini
2010-10-06 17:31     ` H. Peter Anvin
2010-10-06 18:48       ` Thomas Gleixner
2010-10-07 10:41         ` Stefano Stabellini
2010-08-30 11:21 ` [PATCH 5/7] xen: add xen hvm acpi_register_gsi variant stefano.stabellini
2010-08-30 11:21 ` [PATCH 6/7] xen: support GSI -> pirq remapping in PV on HVM guests stefano.stabellini
2010-08-30 11:21 ` [PATCH 7/7] xen: map MSIs into pirqs stefano.stabellini
2010-09-02 19:04 ` Jeremy Fitzhardinge [this message]
2010-09-03 13:51   ` [PATCH 0/7] PV on HVM: receive interrupts as xen events Stefano Stabellini

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=4C7FF538.7020704@goop.org \
    --to=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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