lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 1 Jun 2015 02:18:05 +0000
From:	"Wu, Feng" <feng.wu@...el.com>
To:	"joro@...tes.org" <joro@...tes.org>,
	"dwmw2@...radead.org" <dwmw2@...radead.org>
CC:	"tglx@...utronix.de" <tglx@...utronix.de>,
	"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>,
	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Wu, Feng" <feng.wu@...el.com>
Subject: RE: [v8 0/9] Add VT-d Posted-Interrupts support - IOMMU part

Hi Joerg,

Any comments about this new version? Thanks a lot!

Thanks,
Feng

> -----Original Message-----
> From: Wu, Feng
> Sent: Wednesday, May 27, 2015 12:06 PM
> To: joro@...tes.org; dwmw2@...radead.org
> Cc: tglx@...utronix.de; jiang.liu@...ux.intel.com;
> iommu@...ts.linux-foundation.org; linux-kernel@...r.kernel.org; Wu, Feng
> Subject: [v8 0/9] Add VT-d Posted-Interrupts support - IOMMU part
> 
> VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
> With VT-d Posted-Interrupts enabled, external interrupts from
> direct-assigned devices can be delivered to guests without VMM
> intervention when guest is running in non-root mode.
> 
> You can find the VT-d Posted-Interrtups Spec. in the following URL:
> http://www.intel.com/content/www/us/en/intelligent-systems/intel-technolog
> y/vt-directed-io-spec.html
> 
> This series was part of
> http://thread.gmane.org/gmane.linux.kernel.iommu/7708. To make things
> clear, send out IOMMU part here.
> 
> This patch-set is based on the lastest x86/apic branch of tip tree.
> 
> Divide the whole series which contain multiple components into three parts:
> - Prerequisite changes to irq subsystem (already merged in tip tree x86/apic
> branch)
> - IOMMU part (in this series)
> - KVM and VFIO parts (will send out this part once the first two parts are
> accepted)
> 
> v7->v8:
> * Save the irq mode (posted or remapped) of an IRTE in struct irq_2_iommu.
> * Use this new mode to decide whether update the hardware when
> modifying irte in intel_ir_set_affinity().
> 
> v6->v7:
> * Add an static inline helper function set_irq_posting_cap() to set
> the PI capability.
> * Add some comments for the new member "ir_data->irte_pi_entry".
> 
> v5->v6:
> * Extend 'struct irte' for VT-d Posted-Interrupts, combine remapped
> and posted mode into one irte structure.
> 
> v4->v5:
> * Abstract modify_irte() to accept two format of irte.
> 
> v3->v4:
> * Change capability to a int variant flags instead of a function call.
> * Add hotplug case for VT-d PI.
> 
> Feng Wu (8):
>   iommu: Add new member capability to struct irq_remap_ops
>   iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip
>   iommu, x86: Save the mode (posted or remapped) of an IRTE
>   iommu, x86: No need to migrating irq for VT-d Posted-Interrupts
>   iommu, x86: Add cap_pi_support() to detect VT-d PI capability
>   iommu, x86: Setup Posted-Interrupts capability for Intel iommu
>   iommu, x86: define irq_remapping_cap()
>   iommu, x86: Properly handler PI for IOMMU hotplug
> 
> Thomas Gleixner (1):
>   iommu: dmar: Extend struct irte for VT-d Posted-Interrupts
> 
>  arch/x86/include/asm/irq_remapping.h | 11 +++++
>  drivers/iommu/intel_irq_remapping.c  | 93
> +++++++++++++++++++++++++++++++++++-
>  drivers/iommu/irq_remapping.c        | 11 +++++
>  drivers/iommu/irq_remapping.h        |  6 +++
>  include/linux/dmar.h                 | 70 +++++++++++++++++++++------
>  include/linux/intel-iommu.h          |  1 +
>  6 files changed, 176 insertions(+), 16 deletions(-)
> 
> --
> 2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ