index 73d898383e51..7fc7a14c1a20 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -23075,12 +23075,11 @@ L:k...@vger.kernel.org
S:Maintained
F:drivers/vfio/pci/mlx5/
-VFIO VIRTIO PCI DRIVER
-M: Yishai Hadas
+VFIO NVIDIA GRACE GPU DRIVER
+M: Ankit Agrawal
L:k...
g_cnt,
+loff_t *buf_offset,
+size_t *intersect_count,
+size_t *register_offset);
#define VFIO_IOWRITE_DECLATION(size) \
int vfio_pci_core_iowrite##size(struct vfio_pci_core_device *vdev,\
bool test_mem, u##size val, void __iomem *io);
Reviewed-by: Yishai Hadas
ruct vfio_pci_core_device *vdev,\
bool test_mem, u##size val, void __iomem *io);
Reviewed-by: Yishai Hadas
On 6/17/2020 11:34 AM, Christoph Hellwig wrote:
On Wed, Jun 17, 2020 at 11:31:38AM +0300, Leon Romanovsky wrote:
On Wed, Jun 17, 2020 at 01:29:16AM -0700, Christoph Hellwig wrote:
I think you are talking about UABIs (which in linux we actually call
uapis).
Yes, I used Yishai's cover letter as
On 11/16/2016 8:25 PM, Bjorn Helgaas wrote:
Hi Yishai,
Johannes has been working on an mlx4 initialization problem on an
IBM x3850 X6. The underlying problem is a PCI core issue -- we're
setting RCB in the Mellanox device, which means it thinks it can
generate 128-byte Completions, even though
[-Werror=maybe-uninitialized]
The problem here is that gcc won't track the state of the variable
across a spin_unlock. Moving the assignment out of the lock is
safe here and avoids the warning.
Signed-off-by: Arnd Bergmann
Reviewed-by: Yishai Hadas
---
drivers/net/ethernet/mellanox
On 9/16/2016 9:31 PM, Knut Omang wrote:
The ib_uverbs_reg_mr_resp structure was not 64 bit end aligned
as required by the protocol. This causes alignment issues
if a device specific driver needs to transfer extra response
arguments.
Avoid breaking backward compatibility by improving the handling
On 3/19/2016 6:42 AM, David Miller wrote:
There is a merge conflict against the RDMA tree pull wrt the mlx4 driver,
which I don't know how to resolve.
Can you please point on the conflict ? is it still open that needs our
input ?
On 2/9/2016 10:11 PM, Rasmus Villemoes wrote:
The while loop after err_slaves should use post-decrement; otherwise
we'll fail to do the kfrees for i==0, and will run into out-of-bounds
accesses if the setup above failed already at i==0.
The predecrement in the --port is ok, since ->vlan_filter i
On 5/23/2015 2:12 AM, Benjamin Poirier wrote:
The test in mlx4_load_one() to remove MLX4_FLAG_MSI_X expects mlx4_NOP() to
fail with -EBUSY. It is also necessary to avoid the reset since the device
is not fully reinitialized before calling mlx4_start_hca() a second time.
Note that this will also
Hi List,
I'm using NPTL multi-threaded library and kernel 2.4.
When a new thread is created using the pthread_create call the returned
thread handle is pthread_t.
I want to get the kernel thread id for this pthread - means similar to
what gettid returns when it's called by the thread itself.
Ho
Hi List,
I'm looking for any mechanism in a multi-threaded process to monitor the
health of its running threads - or by a specific monitor thread or by
any other mechanism.
It includes the following aspects:
1) Threads are running and not stuck on any lock.
2) Threads are running and ha
12 matches
Mail list logo
