Displaying 13 results from an estimated 13 matches for "962,10".
Did you mean:
92,10
2018 Nov 15
1
[PATCH v3 6/7] iommu/virtio: Add probe request
...@@ -734,6 +863,7 @@ static void viommu_remove_device(struct device *dev)
>
> iommu_group_remove_device(dev);
> iommu_device_unlink(&vdev->viommu->iommu, dev);
> + viommu_put_resv_regions(dev, &vdev->resv_regions);
> kfree(vdev);
> }
>
> @@ -832,6 +962,10 @@ static int viommu_probe(struct virtio_device *vdev)
> struct virtio_iommu_config, domain_bits,
> &viommu->domain_bits);
>
> + virtio_cread_feature(vdev, VIRTIO_IOMMU_F_PROBE,
> + struct virtio_iommu_config, probe_size,
> + &viommu...
2018 Oct 12
0
[PATCH v3 6/7] iommu/virtio: Add probe request
...egions);
kfree(vdev);
return ret;
@@ -734,6 +863,7 @@ static void viommu_remove_device(struct device *dev)
iommu_group_remove_device(dev);
iommu_device_unlink(&vdev->viommu->iommu, dev);
+ viommu_put_resv_regions(dev, &vdev->resv_regions);
kfree(vdev);
}
@@ -832,6 +962,10 @@ static int viommu_probe(struct virtio_device *vdev)
struct virtio_iommu_config, domain_bits,
&viommu->domain_bits);
+ virtio_cread_feature(vdev, VIRTIO_IOMMU_F_PROBE,
+ struct virtio_iommu_config, probe_size,
+ &viommu->probe_size);
+
viommu-&...
2018 Nov 08
1
[PATCH v3 6/7] iommu/virtio: Add probe request
...@@ -734,6 +863,7 @@ static void viommu_remove_device(struct device *dev)
>
> iommu_group_remove_device(dev);
> iommu_device_unlink(&vdev->viommu->iommu, dev);
> + viommu_put_resv_regions(dev, &vdev->resv_regions);
> kfree(vdev);
> }
>
> @@ -832,6 +962,10 @@ static int viommu_probe(struct virtio_device *vdev)
> struct virtio_iommu_config, domain_bits,
> &viommu->domain_bits);
>
> + virtio_cread_feature(vdev, VIRTIO_IOMMU_F_PROBE,
> + struct virtio_iommu_config, probe_size,
> + &viommu...
2023 Jun 08
6
[PATCH v3 0/4] PCI/VGA: introduce is_boot_device function callback to vga_client_register
From: Sui Jingfeng <suijingfeng at loongson.cn>
Patch 1,2 and 3 do basic clean up to the vgaarb module.
Patch 4 introduce is_boot_device function callback to vga_client_register
Sui Jingfeng (4):
PCI/VGA: tidy up the code and comment format
PCI/VGA: Use unsigned type for the io_state variable
PCI/VGA: only deal with VGA class devices
PCI/VGA: introduce is_boot_device function
2012 Jan 28
1
PATCH: Support for encrypted host keys
...t(&m, num_host_keys);
+ for (i = 0; i < options.num_host_key_files; i++) {
+ if (sensitive_data.host_keys[i] != NULL)
+ buffer_put_key(&m, sensitive_data.host_keys[i]);
+ }
+
if (ssh_msg_send(fd, 0, &m) == -1)
fatal("%s: ssh_msg_send failed", __func__);
@@ -946,8 +962,10 @@ static void
recv_rexec_state(int fd, Buffer *conf)
{
Buffer m;
+ Key *hk;
char *cp;
u_int len;
+ int i, num_host_keys;
debug3("%s: entering fd = %d", __func__, fd);
@@ -981,6 +999,30 @@ recv_rexec_state(int fd, Buffer *conf)
rexec_recv_rng_seed(&m);
#endif
+ n...
2014 Jul 26
0
[RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
...sked as initial states */
mask = msi_mask(desc->msi_attrib.multi_cap);
@@ -884,7 +915,8 @@ void pci_disable_msi(struct pci_dev *dev)
return;
pci_msi_shutdown(dev);
- free_msi_irqs(dev);
+ free_msi_irqs(dev->msi);
+ free_msi_sysfs(dev);
}
EXPORT_SYMBOL(pci_disable_msi);
@@ -930,9 +962,10 @@ int pci_enable_msix(struct pci_dev *dev, struct msix_entry *entries, int nvec)
void __iomem *base;
u16 control;
- if (!entries || !dev->msix_cap || dev->current_state != PCI_D0)
+ if (!entries || !dev->msix_cap || !dev->msi
+ || dev->current_state != PCI_D0)
retur...
2018 Oct 12
18
[PATCH v3 0/7] Add virtio-iommu driver
Implement the virtio-iommu driver, following specification v0.8 [1].
Changes since v2 [2]:
* Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU
would like to phase out the MMIO transport. This produces a complex
topology where the programming interface of the IOMMU could appear
lower than the endpoints that it translates. It's not unheard of (e.g.
AMD IOMMU), and the
2018 Oct 12
18
[PATCH v3 0/7] Add virtio-iommu driver
Implement the virtio-iommu driver, following specification v0.8 [1].
Changes since v2 [2]:
* Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU
would like to phase out the MMIO transport. This produces a complex
topology where the programming interface of the IOMMU could appear
lower than the endpoints that it translates. It's not unheard of (e.g.
AMD IOMMU), and the
2014 Aug 20
1
[RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
...msi_attrib.multi_cap);
> @@ -884,7 +915,8 @@ void pci_disable_msi(struct pci_dev *dev)
> return;
>
> pci_msi_shutdown(dev);
> - free_msi_irqs(dev);
> + free_msi_irqs(dev->msi);
> + free_msi_sysfs(dev);
> }
> EXPORT_SYMBOL(pci_disable_msi);
>
> @@ -930,9 +962,10 @@ int pci_enable_msix(struct pci_dev *dev, struct msix_entry
> *entries, int nvec)
> void __iomem *base;
> u16 control;
>
> - if (!entries || !dev->msix_cap || dev->current_state != PCI_D0)
> + if (!entries || !dev->msix_cap || !dev->msi
> + || dev->...
2014 Aug 20
1
[RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
...msi_attrib.multi_cap);
> @@ -884,7 +915,8 @@ void pci_disable_msi(struct pci_dev *dev)
> return;
>
> pci_msi_shutdown(dev);
> - free_msi_irqs(dev);
> + free_msi_irqs(dev->msi);
> + free_msi_sysfs(dev);
> }
> EXPORT_SYMBOL(pci_disable_msi);
>
> @@ -930,9 +962,10 @@ int pci_enable_msix(struct pci_dev *dev, struct msix_entry
> *entries, int nvec)
> void __iomem *base;
> u16 control;
>
> - if (!entries || !dev->msix_cap || dev->current_state != PCI_D0)
> + if (!entries || !dev->msix_cap || !dev->msi
> + || dev->...
2001 Aug 15
0
[ossh patch] principal name/patterns in authorized_keys2
...ouble
+quotes if they contain whitespace. Named key types may include:
+.Dq krb4 ,
+.Dq krb5
+and/or
+.Dq gsi ,
+depending on what features are compiled in to OpenSSH.
.Pp
Note that lines in this file are usually several hundred bytes long
(because of the size of the RSA key modulus).
@@ -949,6 +962,10 @@
Environment variables set this way
override other default environment values.
Multiple options of this type are permitted.
+.It Cm deny-access
+This option ends authorized_keys2 processing if the key matches. This
+option is only really useful with named key and named key pattern
+entries....
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use