On 11/08/2014 01:00 AM, Thierry Reding wrote:
From: Thierry Reding tred...@nvidia.com
This is the sixth installment in the Tegra IOMMU and memory controller
support series. This version addresses the final outstanding comments from
Olof about using proper Kconfig symbols to track the
This patch fixes a bug in the accounting of the device_state.
In the current code, the device_state was put (decremented) too many times,
which sometimes lead to the driver getting stuck permanently in
put_device_state_wait(). That happen because the device_state-count would go
below zero, which
On Fri, Nov 07, 2014 at 03:26:18PM +, Thierry Reding wrote:
From: Thierry Reding tred...@nvidia.com
Currently the driver registers IOMMU bus operations for all busses even
if no ARM SMMU is present on a system. Depending on the driver probing
order this prevents the driver for the real
On Mon, 2014-11-10 at 14:26 +0800, Feng Wu wrote:
When guest changes its interrupt configuration (such as, vector, etc.)
for direct-assigned devices, we need to update the associated IRTE
with the new guest vector, so external interrupts from the assigned
devices can be injected to guests
On 2014/11/11 2:15, Thomas Gleixner wrote:
On Mon, 10 Nov 2014, Feng Wu wrote:
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
-Original Message-
From: Jiang Liu [mailto:jiang@linux.intel.com]
Sent: Tuesday, November 11, 2014 10:29 AM
To: Thomas Gleixner; Wu, Feng
Cc: g...@kernel.org; pbonz...@redhat.com; David Woodhouse;
j...@8bytes.org; mi...@redhat.com; H. Peter Anvin; x...@kernel.org;
