- 27 Jan, 2021 26 commits
-
-
Ofir Bitton authored
Driver must print sync manager SEI information upon receiving interrupt from FW. Signed-off-by:
Ofir Bitton <obitton@habana.ai> Reviewed-by:
Oded Gabbay <ogabbay@kernel.org> Signed-off-by:
-
Christophe JAILLET authored
Axe 'hl_pci_set_dma_mask()' and replace it with an equivalent 'dma_set_mask_and_coherent()' call. This makes the code a bit less verbose. It also removes an erroneous comment, because 'hl_pci_set_dma_mask()' does not try to use a fall-back value. Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Reviewed-by:
-
Ofir Bitton authored
Due to HW limitation we must remove all direct access to SM registers, in order to do that we will access SM registers using the HW QMANS. When possible and no user context is present, we can directly access the HW QMANS. Whenever there is an active user, driver will prepare a pending command buffer list which will be sent upon user submissions. Signed-off-by:
-
Ofir Bitton authored
In order to support scnenarios in which driver needs access to HW components but it cannot access them directly, we add support for scheduling command buffers internally. These command buffers will be transmitted upon next user command submission context. Signed-off-by:
-
Ofir Bitton authored
A CS must increment the relevant context reference count. We want to increment the reference inside the CS allocation function as opposed for today where we increment it outside. This is logical since we want to avoid explicitly incrementing the context every time we call the CS allocate function. Signed-off-by:
-
Ofir Bitton authored
We separate some of the common code source files to different folders for a better maintainability and testability. Signed-off-by:
-
Ofir Bitton authored
Boot cpu can report errors in various boot stages. Current implementaion does not take into consideration errors reported in late stages, hence we will check for errors at the most late stage when fetching cpucp information. Signed-off-by:
-
Ofir Bitton authored
In case MMU is enabled, we must take MMU page size into consideration when reporting dram size to the user. This is because the MMU page size can be a value which is NOT a power-of-2 value. As a result, the total DRAM size (which is always a power-of-2 value) needed to be rounded-down. Signed-off-by:
-
Moti Haimovski authored
DRAM physical page sizes depend of the amount of HBMs available in the device. this number is device-dependent and may also be subject to binning when one or more of the DRAM controllers are found to to be faulty. Such a configuration may lead to partitioning the DRAM to non-power-of-2 pages. To support this feature we also need to add infrastructure of address scarmbling. Signed-off-by:
Moti Haimovski <mhaimovski@habana.ai> Reviewed-by:
-
Ofir Bitton authored
Accessing kernel allocated memory through debugfs should not be allowed as it introduces a security vulnerability. We remove the option to read/write kernel memory for all asics. Signed-off-by:
-
Ofir Bitton authored
Initialize local variable that is returned by the function, in case it is never assigned. Signed-off-by:
-
Alon Mizrahi authored
When working with DRAM MMU, we should supply the userspace with the virtual start address of the DRAM instead of the physical one. This is because the physical one has no meaning for the user as he only knows the virtual address range. Signed-off-by:
Alon Mizrahi <amizrahi@habana.ai> Reviewed-by:
-
Oded Gabbay authored
Update the latest version of this file that the F/W exports Signed-off-by: -
Oded Gabbay authored
The number of functional HBMs in the same ASIC can be different due to malfunctioning HBM banks. Signed-off-by: -
Ofir Bitton authored
In order to have more information while debugging boot issues, we should print the firmware security status at every boot stage. Signed-off-by:
-
Omer Shpigelman authored
For consistency, modify all memory ioctl functions to get the ioctl arguments structure rather than the arguments themselves. Signed-off-by:
Omer Shpigelman <oshpigelman@habana.ai> Reviewed-by:
-
Omer Shpigelman authored
Change all memory functions documentation according to kernel doc format. Signed-off-by:
-
Alon Mizrahi authored
Often WARN is defined in data-centers as BUG and we would like to avoid hanging the entire server on some internal error of the driver (important as it might be). Therefore, use dev_crit instead. Signed-off-by:
-
Moti Haimovski authored
Instead of having it hard-coded as a define, pass it to the user in runtime. Signed-off-by:
-
Ohad Sharabi authored
Currently mmu_prepare is located at context switch. Since we support a single context, no reason to reconfigure the MMU registers every context switch. Signed-off-by:
Ohad Sharabi <osharabi@habana.ai> Reviewed-by:
-
Ofir Bitton authored
As all packets use the same CTL register masks, we remove duplicated masks and use common masks instead. Signed-off-by:
-
Ofir Bitton authored
In order to support the staged submission feature, user must be allowed to use the same CS sequence for all submissions in the same staged submission. Signed-off-by:
-
Ofir Bitton authored
As part of the staged submission feature, we need Gaudi to support command submissions that will never get a completion. Signed-off-by:
-
Ofir Bitton authored
In order for reserving VA ranges for kernel memory, we need to allow the VM module to be initiated with kernel context. Signed-off-by:
-
Ohad Sharabi authored
remove mmu_cache_lock as it protects a section which is already protected by mmu_lock. in addition, wrap mmu cache invalidate calls in hl_vm_ctx_fini with mmu_lock. Signed-off-by:
-
Oded Gabbay authored
Update to latest firmware hl_boot_if.h file. Signed-off-by:
-
- 26 Jan, 2021 8 commits
-
-
Michal Simek authored
There is no reason to keep PM_API_MAX around. The commit acfdd185 ("firmware: xilinx: Use hash-table for api feature check") removed its usage that's why it is not used anywhere now. Signed-off-by:
Michal Simek <michal.simek@xilinx.com> Link: https://lore.kernel.org/r/86e94593a29a1b5b1958c539a1bfabdd08c0948e.1610959734.git.michal.simek@xilinx.comSigned-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Tom Rix authored
This change fixes the checkpatch warning described in this commit commit cbacb5ab ("docs: printk-formats: Stop encouraging use of unnecessary %h[xudi] and %hh[xudi]") Standard integer promotion is already done and %hx and %hhx is useless so do not encourage the use of %hh[xudi] or %h[xudi]. Reviewed-By:
Steve Wahl <steve.wahl@hpe.com> Signed-off-by:
Tom Rix <trix@redhat.com> Link: https://lore.kernel.org/r/20210123160003.1777766-1-trix@redhat.comSigned-off-by:
-
Rikard Falkeborn authored
The only usage of these is to put their addresses in arrays of pointers to const attribute_groups. Make them const to allow the compiler to put them in read-only memory. Signed-off-by:
Rikard Falkeborn <rikard.falkeborn@gmail.com> Link: https://lore.kernel.org/r/20210108221512.18811-1-rikard.falkeborn@gmail.comSigned-off-by:
-
Johan Hovold authored
There's no need to check for short USB control transfers when sending data using so remove the redundant sanity checks. Reviewed-by:
Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by:
Johan Hovold <johan@kernel.org> Link: https://lore.kernel.org/r/20210118144629.25533-1-johan@kernel.orgSigned-off-by:
-
Jorgen Hansen authored
When create the VMCI queue pair tracking data structures on the host side, the IOCTL for creating the VMCI queue pair didn't validate the queue pair size parameters. This change adds checks for this. This avoids a memory allocation issue in qp_host_alloc_queue, as reported by nslusarek@gmx.net. The check in qp_host_alloc_queue has also been updated to enforce the maximum queue pair size as defined by VMCI_MAX_GUEST_QP_MEMORY. The fix has been verified using sample code supplied by nslusarek@gmx.net. Reported-by: nslusarek@gmx.net Reviewed-by:
Vishnu Dasa <vdasa@vmware.com> Signed-off-by:
Jorgen Hansen <jhansen@vmware.com> Link: https://lore.kernel.org/r/1611160420-30573-1-git-send-email-jhansen@vmware.comSigned-off-by:
-
Jorgen Hansen authored
When the VMCI host support releases guest memory in the case where the VM was killed, the pinned guest pages aren't locked. Use set_page_dirty_lock() instead of set_page_dirty(). Testing done: Killed VM while having an active VMCI based vSocket connection and observed warning from ext4. With this fix, no warning was observed. Ran various vSocket tests without issues. Fixes: 06164d2b ("VMCI: queue pairs implementation.") Reviewed-by:
-
Jorgen Hansen authored
VMCI queue pair allocation is disabled, if a VM is in FT mode. In these cases, VMware Tools may still once in a while attempt to create a vSocket stream connection, resulting in multiple warnings in the kernel logs. Therefore downgrade the error log to a debug log. Reviewed-by:
-
mateng authored
change 'addres' to 'address' Signed-off-by:
mateng <mateng@yulong.com> Link: https://lore.kernel.org/r/20210126084010.1941-1-ayowoe@163.comSigned-off-by:
-
- 25 Jan, 2021 6 commits
-
-
Scott Branden authored
Add ttyVK support to driver to allow console access to VK card from host. Device node will be in the follow form /dev/bcm-vk.x_ttyVKy where: x is the instance of the VK card y is the tty device number on the VK card Acked-by:
Olof Johansson <olof@lixom.net> Signed-off-by:
Scott Branden <scott.branden@broadcom.com> Link: https://lore.kernel.org/r/20210120175827.14820-14-scott.branden@broadcom.comSigned-off-by:
-
Scott Branden authored
Add maintainer entry for new Broadcom VK Driver Acked-by:
-
Scott Branden authored
Add mmap function that allows host application to open up BAR2 memory for remote spooling out messages from the VK logger. Co-developed-by:
Desmond Yan <desmond.yan@broadcom.com> Acked-by:
-
Scott Branden authored
Add reset support via ioctl. Kill user processes that are open when VK card is reset. If a particular PID has issued the reset request do not kill that process as it issued the ioctl. Co-developed-by:
-
Scott Branden authored
Add message support in order to be able to communicate to VK card via message queues. This info is used for debug purposes via collection of logs via direct read of BAR space and by sysfs access (in a follow on commit). Co-developed-by:
-
Scott Branden authored
Add support to get card_info (details about card), peerlog_info (to get details of peerlog on card), and proc_mon_info (process monitoring on card). This info is used for collection of logs via direct read of BAR space and by sysfs access (in a follow on commit). Co-developed-by:
-
