Re: [PATCH v3] Handle wrap around in limit calculation

2024-01-22 Thread Peter Maydell
On Sun, 21 Jan 2024 at 16:48, Shlomo Pongratz wrote: > > From: Shlomo Pongratz > > Hanlde wrap around when calculating the viewport size > caused by the fact that perior to version 460A the limit variable > was 32bit quantity and not 64 bits quantity. > In the i.MX 6Dual/6Quad App

Re: [PATCH v3] Handle wrap around in limit calculation

2024-01-22 Thread Shlomo Pongratz
Y(cr, DesignwarePCIEViewport, 2),   VMSTATE_END_OF_LIST()   } Regards, Phil. *From:* Philippe Mathieu-Daudé [mailto:phi...@linaro.org] *Sent:* Monday, January 22, 2024, 1:17 AM *To:* Shlomo Pongratz; qemu-devel@nongn

Re: [PATCH v3] Handle wrap around in limit calculation

2024-01-21 Thread Peter Xu
On Mon, Jan 22, 2024 at 12:17:24AM +0100, Philippe Mathieu-Daudé wrote: > > @@ -560,7 +569,7 @@ static const VMStateDescription > > vmstate_designware_pcie_viewport = { > > .fields = (const VMStateField[]) { > > VMSTATE_UINT64(base, DesignwarePCIEViewport), > > VMSTATE_UI

Re: [PATCH v3] Handle wrap around in limit calculation

2024-01-21 Thread Philippe Mathieu-Daudé
Hi Shlomo, On 21/1/24 17:47, Shlomo Pongratz wrote: From: Shlomo Pongratz Hanlde wrap around when calculating the viewport size caused by the fact that perior to version 460A the limit variable was 32bit quantity and not 64 bits quantity. In the i.MX 6Dual/6Quad Application

[PATCH v3] Handle wrap around in limit calculation

2024-01-21 Thread Shlomo Pongratz
From: Shlomo Pongratz Hanlde wrap around when calculating the viewport size caused by the fact that perior to version 460A the limit variable was 32bit quantity and not 64 bits quantity. In the i.MX 6Dual/6Quad Applications Processor Reference Manual document on which the orig