All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH 0/3] x86: enable x2APIC mode regardless of interrupt remapping support
Date: Thu, 21 Nov 2019 16:54:08 +0100	[thread overview]
Message-ID: <20191121155411.13250-1-roger.pau@citrix.com> (raw)

Hello,

The following series aims to allow enabling x2APIC mode without
interrupt remapping support. The main usage of this would be in
virtualized environments, that usually provide x2APIC support but not
interrupt remapping.

See the last patch for some performance numbers of using x2APIC over
xAPIC when running Xen in pvshim mode.

Thanks, Roger.

Roger Pau Monne (3):
  x86/ioapic: only use dest32 with x2apic and interrupt remapping
    enabled
  x86/smp: check APIC ID on AP bringup
  x86/apic: allow enabling x2APIC mode regardless of interrupt remapping

 xen/arch/x86/apic.c    | 94 +++++++++++++++++++++---------------------
 xen/arch/x86/io_apic.c | 12 +++---
 xen/arch/x86/smpboot.c |  7 ++++
 3 files changed, 59 insertions(+), 54 deletions(-)

-- 
2.24.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-11-21 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 15:54 Roger Pau Monne [this message]
2019-11-21 15:54 ` [Xen-devel] [PATCH 1/3] x86/ioapic: only use dest32 with x2apic and interrupt remapping enabled Roger Pau Monne
2019-11-21 15:54 ` [Xen-devel] [PATCH 2/3] x86/smp: check APIC ID on AP bringup Roger Pau Monne
2019-11-21 15:54 ` [Xen-devel] [PATCH 3/3] x86/apic: allow enabling x2APIC mode regardless of interrupt remapping Roger Pau Monne

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=20191121155411.13250-1-roger.pau@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.