644
> index ..3ca8c187897a
> --- /dev/null
> +++ b/drivers/vfio/pci/nvgrace-gpu/Makefile
> @@ -0,0 +1,3 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +obj-$(CONFIG_NVGRACE_GPU_VFIO_PCI) += nvgrace-gpu-vfio-pci.o
> +nvgrace-gpu-vfio-pci-y := main.o
>
On Tue, 6 Feb 2024 04:31:23 +0530
wrote:
> From: Ankit Agrawal
>
> NVIDIA's upcoming Grace Hopper Superchip provides a PCI-like device
> for the on-chip GPU that is the logical OS representation of the
> internal proprietary chip-to-chip cache coherent interconnect.
>
> The device is peculiar
Hi:
Thanks for the patches. :) Several places needs to be improved:
1. The prefix of the patch should be: "drm/i915/gvt:".
2. You can just cc the maintainers of gvt since the gvt is a sub-module
of i915.
3. Better refine the tittle of the patch and also the commit message. An
informative
Hi:
Thanks for the patches. :) Several places needs to be improved:
1. The prefix of the patch should be: "drm/i915/gvt:".
2. You can just cc the maintainers of gvt since the gvt is a sub-module
of i915.
3. Better refine the tittle of the patch and also the commit message. An
informative
Is is possible to put per-task PTI control interface into cgroup or
other interfaces? Enabling/disabling per-task PTI should be a decision
from the system administrator not the application itself.
On 2018/1/9 18:02, Willy Tarreau wrote:
Hi Eric,
On Tue, Jan 09, 2018 at 09:31:27AM -0600,
Is is possible to put per-task PTI control interface into cgroup or
other interfaces? Enabling/disabling per-task PTI should be a decision
from the system administrator not the application itself.
On 2018/1/9 18:02, Willy Tarreau wrote:
Hi Eric,
On Tue, Jan 09, 2018 at 09:31:27AM -0600,
Thanks, applied!
On 10/16/17 10:32, Jérémy Lefaure wrote:
Using the ARRAY_SIZE macro improves the readability of the code. Also,
it's useless to use a variable to store this constant calculated at
compile time.
Found with Coccinelle with the following semantic patch:
@r depends on (org ||
Thanks, applied!
On 10/16/17 10:32, Jérémy Lefaure wrote:
Using the ARRAY_SIZE macro improves the readability of the code. Also,
it's useless to use a variable to store this constant calculated at
compile time.
Found with Coccinelle with the following semantic patch:
@r depends on (org ||
Thanks, applied! :)
On 10/16/17 06:32, Christos Gkekas wrote:
Delete variables 'gma_bottom' that are set but never used.
Signed-off-by: Christos Gkekas
---
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
Thanks, applied! :)
On 10/16/17 06:32, Christos Gkekas wrote:
Delete variables 'gma_bottom' that are set but never used.
Signed-off-by: Christos Gkekas
---
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
if we
can extend that channel and notify the userspace application that guest
framebuffer changed via that channel. So userspace application even
doesn't need to call the ioctl periodically. :) If VM runs a
single-buffered application.
Thanks,
Zhi.
On Fri, 2017-06-23 at 15:49 +0800, Zhi Wang
if we
can extend that channel and notify the userspace application that guest
framebuffer changed via that channel. So userspace application even
doesn't need to call the ioctl periodically. :) If VM runs a
single-buffered application.
Thanks,
Zhi.
On Fri, 2017-06-23 at 15:49 +0800, Zhi Wang
Hi:
Thanks for the discussions! If the userspace application has
already maintained a LRU list, it looks like we don't need generation
anymore, as userspace application will lookup the guest framebuffer from
the LRU list by "offset". No matter how, it would know if this is a new
guest
Hi:
Thanks for the discussions! If the userspace application has
already maintained a LRU list, it looks like we don't need generation
anymore, as userspace application will lookup the guest framebuffer from
the LRU list by "offset". No matter how, it would know if this is a new
guest
would have much more available elements to allocate.
After the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang
Who is going to call that function? Adding a new interace usually
comes with a user,
would have much more available elements to allocate.
After the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang <zhi.a.w...@intel.com>
Who is going to call that function? Adding a new interace usua
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2 files changed, 46 insertions
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang <zhi.a.w...@intel.com>
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2 files changed, 46 insertions
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang <zhi.a.w...@intel.com>
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2 files changed, 46 insertions
the refactor, mempool_refill() can also executes with mempool_resize()
/mempool_alloc/mempool_free() or another mempool_refill().
Signed-off-by: Zhi Wang <zhi.a.w...@intel.com>
---
include/linux/mempool.h | 1 +
mm/mempool.c| 61 -
2
22 matches
Mail list logo