Re: [PATCH v4] windows/virt2phys: fix block MDL not updated

2024-11-20 Thread Thomas Monjalon
16/10/2024 08:32, Dmitry Kozlyuk: > 2024-10-15 16:04 (UTC-0700), Stephen Hemminger: > > This looks ok, but I know nothing about windows drivers. > > Could we get a review by Dmitry? > > v3 got Reviewed-by almost a year ago, v4 only did a bit of renaming: > > http://inbox.dpdk.org/dev/202311

Re: [PATCH v4] windows/virt2phys: fix block MDL not updated

2024-10-15 Thread Dmitry Kozlyuk
2024-10-15 16:04 (UTC-0700), Stephen Hemminger: > This looks ok, but I know nothing about windows drivers. > Could we get a review by Dmitry? v3 got Reviewed-by almost a year ago, v4 only did a bit of renaming: http://inbox.dpdk.org/dev/20231130071001.4c7931c8@sovereign/ There were no ot

Re: [PATCH v4] windows/virt2phys: fix block MDL not updated

2024-10-15 Thread Stephen Hemminger
On Mon, 4 Dec 2023 18:32:14 +0800 Ric Li wrote: > The virt2phys_translate function previously scanned existing blocks, > returning the physical address from the stored MDL info if present. > This method was problematic when a virtual address pointed to a freed > and reallocated memory segment, p

[PATCH v4] windows/virt2phys: fix block MDL not updated

2023-12-04 Thread Ric Li
The virt2phys_translate function previously scanned existing blocks, returning the physical address from the stored MDL info if present. This method was problematic when a virtual address pointed to a freed and reallocated memory segment, potentially changing the physical address mapping. Yet, virt

[PATCH v4] windows/virt2phys: fix block MDL not updated

2023-12-04 Thread Ric Li
The virt2phys_translate function previously scanned existing blocks, returning the physical address from the stored MDL info if present. This method was problematic when a virtual address pointed to a freed and reallocated memory segment, potentially changing the physical address mapping. Yet, virt