similar to: [PATCH v3] vfio error recovery: kernel support

This is a design and an initial patch for kernel side for AER support in VFIO. 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the VM eventually, but not immediately because it's detected and reported asynchronously. Interrupts are forwarded as usual. Correctable errors are not reported to guest at all.

This is a design and an initial patch for kernel side for AER support in VFIO. 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the VM eventually, but not immediately because it's detected and reported asynchronously. Interrupts are forwarded as usual. Correctable errors are not reported to guest at all.

Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM to signal they are safe to use with an IOMMU. Without this bit, exposing the device to userspace is unsafe, so probe and fail VFIO initialization unless noiommu is enabled. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vfio/pci/vfio_pci_private.h | 1 + drivers/vfio/pci/vfio_pci.c | 11 +++

Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM to signal they are safe to use with an IOMMU. Without this bit, exposing the device to userspace is unsafe, so probe and fail VFIO initialization unless noiommu is enabled. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/vfio/pci/vfio_pci_private.h | 1 + drivers/vfio/pci/vfio_pci.c | 14 ++++

On Mon, 29 Aug 2016 21:23:25 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Tue, 30 Aug 2016 05:27:17 +0300 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > > to signal they are safe to use with an IOMMU. > > > > Without this bit, exposing the device to

On Mon, Aug 29, 2016 at 10:53:04PM -0600, Alex Williamson wrote: > On Mon, 29 Aug 2016 21:52:20 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Mon, 29 Aug 2016 21:23:25 -0600 > > Alex Williamson <alex.williamson at redhat.com> wrote: > > > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > > "Michael S. Tsirkin"

On Mon, 18 Apr 2016 12:58:28 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.

On Mon, 18 Apr 2016 12:58:28 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.

On Mon, 29 Aug 2016 21:52:20 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Mon, 29 Aug 2016 21:23:25 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > > > Modern virtio pci devices can set

On Mon, 29 Aug 2016 21:52:20 -0600 Alex Williamson <alex.williamson at redhat.com> wrote: > On Mon, 29 Aug 2016 21:23:25 -0600 > Alex Williamson <alex.williamson at redhat.com> wrote: > > > On Tue, 30 Aug 2016 05:27:17 +0300 > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > > > Modern virtio pci devices can set

On Tue, 30 Aug 2016 05:27:17 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.

On Tue, 30 Aug 2016 05:27:17 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Modern virtio pci devices can set VIRTIO_F_IOMMU_PLATFORM > to signal they are safe to use with an IOMMU. > > Without this bit, exposing the device to userspace is unsafe, so probe > and fail VFIO initialization unless noiommu is enabled. > > Signed-off-by: Michael S.

Legacy virtio devices always bypassed an IOMMU, so using them with vfio was never safe. This adds a quirk detecting these and disabling VFIO unless the noiommu mode is used. At the moment, this only applies to virtio-pci devices. The patch might make sense on stable as well. Michael S. Tsirkin (2): vfio: report group noiommu status vfio: add virtio pci quirk

Legacy virtio devices always bypassed an IOMMU, so using them with vfio was never safe. This adds a quirk detecting these and disabling VFIO unless the noiommu mode is used. At the moment, this only applies to virtio-pci devices. The patch might make sense on stable as well. Michael S. Tsirkin (2): vfio: report group noiommu status vfio: add virtio pci quirk

This is an attempt to allow enabling IOMMU for DMA. Design: - new feature bit IOMMU_PLATFORM which means host won't bypass IOMMU - virtio core uses DMA API if it sees IOMMU_PLATFORM - add quirk for vfio to disable device unless IOMMU_PLATFORM is set or the no-iommu mode is enabled - while I'm not sure how it will be used, it seems like a good idea to also have

This is an attempt to allow enabling IOMMU for DMA. Design: - new feature bit IOMMU_PLATFORM which means host won't bypass IOMMU - virtio core uses DMA API if it sees IOMMU_PLATFORM - add quirk for vfio to disable device unless IOMMU_PLATFORM is set or the no-iommu mode is enabled - while I'm not sure how it will be used, it seems like a good idea to also have

Hi, After running configure, my /source3/include/autoconf/config.h is not showing these flags: #define HAVE_KRB5 1 #define HAVE_LDAP 1 How to fix config.log so that it will work: Please reply as sooon as possible: Nirmit Kansal .........................................

Hi, Actually I am working on a project in which we are migrating from 3.x to 4, so Please tell me the difference in versions and also give me information that how we can use active directory of 4.0 effectively as we are having CIFS and Kerberos feature in 3.x, And how this active directory can be helpful in our implementation. And I am also having a question as we are using 3.x so only because of

Hi, I am using samba4 and libsmbclient.h and libsmbclient.so. I have implemented the below apis locally within linux machines, but now I want to connect to my windows machine for this I am giving my windows machine username and password In below get_auth_data_fn() function: static void get_auth_data_fn(const char * m_pserver, const char * m_pshare,

On 2016?08?30? 10:27, Michael S. Tsirkin wrote: > Legacy virtio devices always bypassed an IOMMU, so using them with vfio was > never safe. And it actually won't work since GPA is assumed in the device. So I'm not sure this is must since we should get a IOMMU fault in this case. > This adds a quirk detecting these and disabling VFIO unless the > noiommu mode is used. At