Le 26/09/2017 à 03:44, Vaibhav Jain a écrit :
Hi Christophe,
A minor nitpick
Christophe Lombard writes:
+ for (dar = (addr & ~(page_size - 1)); dar < (addr + size); dar +=
page_size) {
+ if (dar < vma->vm_start || dar > vma->vm_end) {
Code comment in mm_types.h for vm_e
On 26/09/17 11:44, Vaibhav Jain wrote:
Hi Christophe,
A minor nitpick
Christophe Lombard writes:
+ for (dar = (addr & ~(page_size - 1)); dar < (addr + size); dar +=
page_size) {
+ if (dar < vma->vm_start || dar > vma->vm_end) {
Code comment in mm_types.h for vm_end says
Hi Christophe,
A minor nitpick
Christophe Lombard writes:
> + for (dar = (addr & ~(page_size - 1)); dar < (addr + size); dar +=
> page_size) {
> + if (dar < vma->vm_start || dar > vma->vm_end) {
Code comment in mm_types.h for vm_end says it "The first byte after our
end address
On 25/09/17 18:58, Christophe Lombard wrote:
The in-kernel 'library' API can be called by drivers to help
interaction with an IBM XSL on a POWER9 system.
The cxllib_handle_fault() API is used to handle memory fault. All memory
pages of the specified buffer have to be handled but under certain
co
Le 25/09/2017 à 10:58, Christophe Lombard a écrit :
The in-kernel 'library' API can be called by drivers to help
interaction with an IBM XSL on a POWER9 system.
The cxllib_handle_fault() API is used to handle memory fault. All memory
pages of the specified buffer have to be handled but under c
The in-kernel 'library' API can be called by drivers to help
interaction with an IBM XSL on a POWER9 system.
The cxllib_handle_fault() API is used to handle memory fault. All memory
pages of the specified buffer have to be handled but under certain
conditions,the last page may not be touched, and
