On Mon, Aug 26, 2019 at 6:25 AM Waldek Kozaczuk
wrote:
>
>
> On Saturday, August 24, 2019 at 3:26:15 PM UTC-4, Nadav Har'El wrote:
>>
>>
>> On Sat, Aug 24, 2019 at 7:02 PM Waldek Kozaczuk
>> wrote:
>>
>>>
>>>
>>> On Saturday, August 24, 2019 at 5:34:22 AM UTC-4, Nadav Har'El wrote:
On Sat, Aug 24, 2019 at 7:02 PM Waldek Kozaczuk
wrote:
>
>
> On Saturday, August 24, 2019 at 5:34:22 AM UTC-4, Nadav Har'El wrote:
>>
>>
>> On Sat, Aug 24, 2019 at 7:14 AM Waldemar Kozaczuk
>> wrote:
>>
>>> Most of the time the kernel code references memory using virtual
>>> addresses.
>>>
On Saturday, August 24, 2019 at 5:34:22 AM UTC-4, Nadav Har'El wrote:
>
>
> On Sat, Aug 24, 2019 at 7:14 AM Waldemar Kozaczuk > wrote:
>
>> Most of the time the kernel code references memory using virtual
>> addresses.
>> However some allocated system structures like page tables use physical
On Sat, Aug 24, 2019 at 7:14 AM Waldemar Kozaczuk
wrote:
> Most of the time the kernel code references memory using virtual addresses.
> However some allocated system structures like page tables use physical
> addresses.
> For that reason it is critical that physical addresses are never 0 which
Great, thanks for that! This patch certainly solved my issue - its no
longer crashing at that point and is making much better progress...
Rick
On Sat, 2019-08-24 at 00:14 -0400, Waldemar Kozaczuk wrote:
> Most of the time the kernel code references memory using virtual
> addresses.
> However
Most of the time the kernel code references memory using virtual addresses.
However some allocated system structures like page tables use physical
addresses.
For that reason it is critical that physical addresses are never 0 which for
example
in case of page table would mean that given entry is
