于 2012年05月22日 02:58, Eric Northup 写道:
> On Wed, May 16, 2012 at 12:50 AM, zhangyanfei
> wrote:
>>
>> This patch set exports offsets of VMCS fields as note information for
>> kdump. We call it VMCSINFO. The purpose of VMCSINFO is to retrieve
>> runtime state of guest machine image, such as register
于 2012年05月21日 17:36, Avi Kivity 写道:
> On 05/21/2012 12:08 PM, Yanfei Zhang wrote:
>> 于 2012年05月21日 16:34, Avi Kivity 写道:
>>> On 05/21/2012 05:32 AM, Yanfei Zhang wrote:
于 2012年05月21日 01:43, Avi Kivity 写道:
> On 05/16/2012 10:50 AM, zhangyanfei wrote:
>> This patch set exports offsets of
DMA transactions are tagged with the source ID of the device making
the request. Occasionally hardware screws this up and uses the
source ID of a different device (often the wrong function number of
a multifunction device). A specific Ricoh multifunction device is
a prime example of this problem
VFIO is a secure user level driver for use with both virtual machines
and user level drivers. VFIO makes use of IOMMU groups to ensure the
isolation of devices in use, allowing unprivileged user access. It's
intended that VFIO will replace KVM device assignment and UIO drivers
(in cases where the
For returning errors out to non-PCI code. Re-name xen's version.
Signed-off-by: Alex Williamson
Acked-by: Konrad Rzeszutek Wilk
---
drivers/xen/xen-pciback/conf_space.c |6 +++---
include/linux/pci.h | 26 ++
2 files changed, 29 insertions(+), 3
Fill in many missing definitions and add sizeof fields for many
sections allowing for more extensive config parsing.
Signed-off-by: Alex Williamson
---
include/linux/pci_regs.h | 112 +-
1 files changed, 100 insertions(+), 12 deletions(-)
diff --git
VFIO PCI support will make use of these for user initiated
PCI config accesses.
Signed-off-by: Alex Williamson
Acked-by: Bjorn Helgaas
---
drivers/pci/access.c |6 --
drivers/pci/pci.h|7 ---
include/linux/pci.h |8
3 files changed, 12 insertions(+), 9 deletio
x86 is probably the wrong name for this VFIO IOMMU driver, but x86
is the primary target for it. This driver support a very simple
usage model using the existing IOMMU API. The IOMMU is expected to
support the full host address space with no special IOVA windows,
number of mappings restrictions,
Signed-off-by: Alex Williamson
---
Documentation/vfio.txt | 315
1 files changed, 315 insertions(+), 0 deletions(-)
create mode 100644 Documentation/vfio.txt
diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt
new file mode 100644
inde
IOMMU groups allow IOMMU drivers to represent DMA visibility
and isolation of devices. Multiple devices may be grouped
together for the purposes of DMA. Placing a pointer on
struct device enable easy access for things like streaming
DMA programming and drivers like VFIO.
Signed-off-by: Alex Will
found here on top of 3.4:
git://github.com/awilliam/linux-vfio.git iommu-group-vfio-20120521
The Qemu tree has also been updated to Qemu 1.1 and can be found here:
git://github.com/awilliam/qemu-vfio.git iommu-group-vfio
I'd really like to make a push to get this in for 3.5, so let's talk
IOMMU device groups are currently a rather vague associative notion
with assembly required by the user or user level driver provider to
do anything useful. This patch intends to grow the IOMMU group concept
into something a bit more consumable.
To do this, we first create an object representing t
Add back group support for AMD & Intel. amd_iommu already tracks
devices and has init and uninit routines to manage groups.
intel-iommu does this on the fly, so we make use of the notifier
support built into iommu groups to create and remove groups.
Signed-off-by: Alex Williamson
---
drivers/i
Incorporate DMA quirking and ACS checking into amd_iommu and
intel-iommu. Note that IOMMU groups are not yet used for
streaming DMA, so this doesn't immediately solve the problems
with broken Ricoh devices. This a very strict implementation of
ACS checking, which will often result in multifunctio
In a PCI environment, transactions aren't always required to reach
the root bus before being re-routed. Intermediate switches between
an endpoint and the root bus can redirect DMA back downstream before
things like IOMMUs have a chance to intervene. Legacy PCI is always
susceptible to this as it
On Mon, May 21, 2012 at 04:30:41PM -0300, Marcelo Tosatti wrote:
> On Mon, May 21, 2012 at 04:15:50PM +0800, Xiao Guangrong wrote:
> > On 05/21/2012 04:08 PM, Gleb Natapov wrote:
> >
> > > On Mon, May 21, 2012 at 02:45:45PM +0800, Xiao Guangrong wrote:
> > >> If we map a readonly memory space from
On 22.05.2012, at 05:44, Alexey Kardashevskiy wrote:
> On 22/05/12 13:21, Alexander Graf wrote:
>>
>>
>> On 22.05.2012, at 04:02, Benjamin Herrenschmidt
>> wrote:
>>
>>> On Fri, 2012-05-18 at 15:12 +1000, Alexey Kardashevskiy wrote:
Alexander,
Is that any better? :)
>>>
>>
On 22/05/12 15:52, Alexander Graf wrote:
>
>
> On 22.05.2012, at 05:44, Alexey Kardashevskiy wrote:
>
>> On 22/05/12 13:21, Alexander Graf wrote:
>>>
>>>
>>> On 22.05.2012, at 04:02, Benjamin Herrenschmidt
>>> wrote:
>>>
On Fri, 2012-05-18 at 15:12 +1000, Alexey Kardashevskiy wrote:
On 22.05.2012, at 08:11, Alexey Kardashevskiy wrote:
> On 22/05/12 15:52, Alexander Graf wrote:
>>
>>
>> On 22.05.2012, at 05:44, Alexey Kardashevskiy wrote:
>>
>>> On 22/05/12 13:21, Alexander Graf wrote:
On 22.05.2012, at 04:02, Benjamin Herrenschmidt
wrote:
On 22.05.2012, at 08:11, Alexey Kardashevskiy wrote:
> On 22/05/12 15:52, Alexander Graf wrote:
>>
>>
>> On 22.05.2012, at 05:44, Alexey Kardashevskiy wrote:
>>
>>> On 22/05/12 13:21, Alexander Graf wrote:
On 22.05.2012, at 04:02, Benjamin Herrenschmidt
wrote:
101 - 120 of 120 matches
Mail list logo