I wish to discuss a very confidential business proposition with you.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
A VFIO userspace driver will start by opening the VFIO device
that corresponds to an IOMMU group, and will use the ioctl interface
to get the basic device info, such as number of memory regions and
interrupts, and their properties.
This patch enables the IOCTLs:
- VFIO_DEVICE_GET_INFO
- VFIO_DEV
Adds support to mask interrupts, and also for automasked interrupts.
Level sensitive interrupts are exposed as automasked interrupts and
are masked and disabled automatically when they fire.
Signed-off-by: Antonios Motakis
Tested-by: Alvise Rigo
---
drivers/vfio/platform/vfio_platform_irq.c
Return information for the interrupts exposed by the device.
This patch extends VFIO_DEVICE_GET_INFO with the number of IRQs
and enables VFIO_DEVICE_GET_IRQ_INFO
Signed-off-by: Antonios Motakis
---
drivers/vfio/platform/Makefile| 2 +-
drivers/vfio/platform/vfio_platform.c
This patch allows to set an eventfd for a patform device's interrupt,
and also to trigger the interrupt eventfd from userspace for testing.
Signed-off-by: Antonios Motakis
Tested-by: Alvise Rigo
---
drivers/vfio/platform/vfio_platform.c | 36 +++-
drivers/vfio/platform/vfio_platfor
Allow to memory map the MMIO regions of the device so userspace can
directly access them.
Signed-off-by: Antonios Motakis
Tested-by: Alvise Rigo
---
drivers/vfio/platform/vfio_platform.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/vfio/platform
VFIO returns a file descriptor which we can use to manipulate the memory
regions of the device. Since some memory regions we cannot mmap due to
security concerns, we also allow to read and write to this file descriptor
directly.
Signed-off-by: Antonios Motakis
Tested-by: Alvise Rigo
---
drivers
This patch forms the skeleton for platform devices support with VFIO.
We implement a new 'vfio_bind' sysfs file, that, once written
with a device ID, binds the platform driver to the device directly.
Bypassing the driver core's traditional bind file allows this
platform driver to bind to any device
From: Kim Phillips
Needed by drivers, such as the vfio platform driver [1], seeking to
bypass bind_store()'s driver_match_device(), and bind to any device
via a private sysfs bind file.
[1] https://lkml.org/lkml/2013/12/11/522
note: the EXPORT_SYMBOL is needed because vfio-platform can be built
The ARM SMMU driver expects the IOMMU_EXEC flag, otherwise it will
set the page tables for a device as XN (execute never). This affects
devices such as the ARM PL330 DMA Controller, which fails to operate
if the XN flag is set on the memory it tries to fetch its instructions
from.
We introduce the
This is a workaround to make the VFIO_IOMMU_TYPE1 driver usable with
platform devices instead of PCI. A future permanent fix should support
both. This is required in order to use the Exynos SMMU, or ARM SMMU
driver with VFIO.
Signed-off-by: Antonios Motakis
---
drivers/vfio/Kconfig|
v4 of this series is functionally identical to v3 for VFIO_PLATFORM. The only
change is the inclusion of Kim Phillips' patch to expose driver_probe_device()
and the implementation of a binding mechanism for arbitrary devices via a file
in sysfs. The latter has been folded in the skeleton patch (04/
On 02/07/2014 07:32 PM, Paolo Bonzini wrote:
> Il 07/02/2014 14:07, Andrey Korolyov ha scritto:
>> Ok, I will do, but looks like libvirt version(1.0.2) in not relevant -
>> it meets criteria set by debian packagers
>
> Then Debian's qemu packaging it's wrong, QEMU 1.6 or newer should conflict
> wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/23/2014 07:55 PM, Dave Hansen wrote:
> On 01/21/2014 08:38 AM, Toralf Förster wrote:
>> Jan 21 17:18:57 n22 kernel: INFO: rcu_sched self-detected stall on CPU { 2}
>> (t=60001 jiffies g=18494 c=18493 q=183951)
>> Jan 21 17:18:57 n22 kernel: s
Il 08/02/2014 08:51, Andi Kleen ha scritto:
kvm_rebooting is referenced from assembler code, thus
needs to be visible.
Cc: g...@redhat.com
Cc: pbonz...@redhat.com
Cc: kvm@vger.kernel.org
Signed-off-by: Andi Kleen
---
virt/kvm/kvm_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
08.02.2014 03:55, Brian Jackson пишет:
What latest? There are a few different places to get drivers (Fedora
site, RHEL subscription, build yourself, etc). From the graphs, it looks
like the speed isn't too bad at times. But it's hard to tell with the
information you've given about your particular
16 matches
Mail list logo