xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Feng Wu <feng.wu@intel.com>
To: xen-devel@lists.xen.org
Cc: Feng Wu <feng.wu@intel.com>, Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v10 7/7] Add a command line parameter for VT-d posted-interrupts
Date: Thu,  3 Dec 2015 16:35:34 +0800	[thread overview]
Message-ID: <1449131734-3578-8-git-send-email-feng.wu@intel.com> (raw)
In-Reply-To: <1449131734-3578-1-git-send-email-feng.wu@intel.com>

Enable VT-d Posted-Interrupts and add a command line
parameter for it.

CC: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Feng Wu <feng.wu@intel.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
---
v6:
- Change the default value to 'false' in xen-command-line.markdown

 docs/misc/xen-command-line.markdown | 9 ++++++++-
 xen/drivers/passthrough/iommu.c     | 3 +++
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index c103894..cbfb59d 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -868,7 +868,7 @@ debug hypervisor only).
 > Default: `new` unless directed-EOI is supported
 
 ### iommu
-> `= List of [ <boolean> | force | required | intremap | qinval | snoop | sharept | dom0-passthrough | dom0-strict | amd-iommu-perdev-intremap | workaround_bios_bug | igfx | verbose | debug ]`
+> `= List of [ <boolean> | force | required | intremap | intpost | qinval | snoop | sharept | dom0-passthrough | dom0-strict | amd-iommu-perdev-intremap | workaround_bios_bug | igfx | verbose | debug ]`
 
 > Sub-options:
 
@@ -895,6 +895,13 @@ debug hypervisor only).
 >> Control the use of interrupt remapping (DMA remapping will always be enabled
 >> if IOMMU functionality is enabled).
 
+> `intpost`
+
+> Default: `false`
+
+>> Control the use of interrupt posting, which depends on the availability of
+>> interrupt remapping.
+
 > `qinval` (VT-d)
 
 > Default: `true`
diff --git a/xen/drivers/passthrough/iommu.c b/xen/drivers/passthrough/iommu.c
index 3d02550..fae2547 100644
--- a/xen/drivers/passthrough/iommu.c
+++ b/xen/drivers/passthrough/iommu.c
@@ -32,6 +32,7 @@ static void iommu_dump_p2m_table(unsigned char key);
  *   off|no|false|disable       Disable IOMMU (default)
  *   force|required             Don't boot unless IOMMU is enabled
  *   no-intremap                Disable interrupt remapping
+ *   no-intpost                 Disable VT-d Interrupt posting
  *   verbose                    Be more verbose
  *   debug                      Enable debugging messages and checks
  *   workaround_bios_bug        Workaround some bios issue to still enable
@@ -105,6 +106,8 @@ static void __init parse_iommu_param(char *s)
             iommu_qinval = val;
         else if ( !strcmp(s, "intremap") )
             iommu_intremap = val;
+        else if ( !strcmp(s, "intpost") )
+            iommu_intpost = val;
         else if ( !strcmp(s, "debug") )
         {
             iommu_debug = val;
-- 
2.1.0

  parent reply	other threads:[~2015-12-03  8:35 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03  8:35 [PATCH v10 0/7] Add VT-d Posted-Interrupts support Feng Wu
2015-12-03  8:35 ` [PATCH v10 1/7] VT-d Posted-intterrupt (PI) design Feng Wu
2015-12-03  8:35 ` [PATCH v10 2/7] vmx: Suppress posting interrupts when 'SN' is set Feng Wu
2015-12-03  8:35 ` [PATCH v10 3/7] vt-d: Add API to update IRTE when VT-d PI is used Feng Wu
2015-12-10 10:52   ` Tian, Kevin
2015-12-03  8:35 ` [PATCH v10 4/7] Update IRTE according to guest interrupt config changes Feng Wu
2015-12-10 10:53   ` Tian, Kevin
2015-12-03  8:35 ` [PATCH v10 5/7] vmx: Properly handle notification event when vCPU is running Feng Wu
2015-12-03  8:35 ` [PATCH v10 6/7] vmx: VT-d posted-interrupt core logic handling Feng Wu
2015-12-10 11:40   ` Tian, Kevin
2015-12-11  1:58     ` Wu, Feng
2015-12-11  2:27       ` Tian, Kevin
2015-12-11  3:12         ` Wu, Feng
2015-12-21  6:43   ` Wu, Feng
2015-12-21  9:03     ` Dario Faggioli
2015-12-21  9:26       ` Wu, Feng
2015-12-23  2:21   ` Dario Faggioli
2015-12-23  2:28     ` Wu, Feng
2015-12-23  5:16       ` Tian, Kevin
2015-12-23  5:18         ` Wu, Feng
2015-12-23  4:58     ` Wu, Feng
2015-12-23 10:09       ` Jan Beulich
2016-01-18  1:20         ` Wu, Feng
2016-01-18  8:40           ` Jan Beulich
2016-01-18  8:45             ` Wu, Feng
2016-01-18  9:03               ` Jan Beulich
2016-01-19  8:48                 ` Wu, Feng
2016-01-18 15:14   ` Jan Beulich
2016-01-20  7:49     ` Wu, Feng
2016-01-20  8:35       ` Jan Beulich
2016-01-20 11:12         ` Dario Faggioli
2016-01-20 11:18           ` Wu, Feng
2016-01-20 11:20         ` Wu, Feng
2016-01-20 11:35           ` Jan Beulich
2016-01-20 13:30             ` Dario Faggioli
2016-01-20 13:42               ` Wu, Feng
2016-01-25  5:26               ` Wu, Feng
2016-01-25 13:59                 ` Jan Beulich
2016-01-20 13:48             ` Wu, Feng
2016-01-20 14:03               ` Jan Beulich
2016-01-21  9:05     ` Wu, Feng
2016-01-21 10:34       ` Jan Beulich
2015-12-03  8:35 ` Feng Wu [this message]
2015-12-03 11:19 ` [PATCH v10 0/7] Add VT-d Posted-Interrupts support Jan Beulich
2015-12-03 13:54   ` Wu, Feng
2015-12-10 10:48 ` Tian, Kevin
2015-12-10 13:40   ` Wu, Feng

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=1449131734-3578-8-git-send-email-feng.wu@intel.com \
    --to=feng.wu@intel.com \
    --cc=jbeulich@suse.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;
as well as URLs for NNTP newsgroup(s).