Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Alexander Lochmann
On 18.12.18 11:32, Konstantin Belousov wrote: > On Tue, Dec 18, 2018 at 11:22:53AM +0100, Alexander Lochmann wrote: >> Some context: We are doing VM-based tracing in the FreeBSD kernel. For that, we observe parts of the kernel memory (allocations, accesses,...). Before 12.0 we simp

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Konstantin Belousov
On Tue, Dec 18, 2018 at 11:22:53AM +0100, Alexander Lochmann wrote: > > >> Some context: We are doing VM-based tracing in the FreeBSD kernel. For > >> that, we observe parts of the kernel memory (allocations, accesses,...). > >> Before 12.0 we simply knew that kernel addresses that we logged were

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Alexander Lochmann
>> Some context: We are doing VM-based tracing in the FreeBSD kernel. For >> that, we observe parts of the kernel memory (allocations, accesses,...). >> Before 12.0 we simply knew that kernel addresses that we logged were >> unique. Moreover, when a memory access to a region of interest happened >

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Konstantin Belousov
On Tue, Dec 18, 2018 at 10:16:35AM +0100, Alexander Lochmann wrote: > Am 18.12.18 um 06:27 schrieb Konstantin Belousov: > > On Mon, Dec 17, 2018 at 02:51:48PM +0100, Alexander Lochmann wrote: > >> Hi folks! > >> > >> According to git commit e3089a (https://reviews.freebsd.org/D1463) > >> FreeBSD 12

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Alexander Lochmann
Am 18.12.18 um 06:27 schrieb Konstantin Belousov: > On Mon, Dec 17, 2018 at 02:51:48PM +0100, Alexander Lochmann wrote: >> Hi folks! >> >> According to git commit e3089a (https://reviews.freebsd.org/D1463) >> FreeBSD 12.0 i386 uses separate address spaces for kernel and user >> space. So basically

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Konstantin Belousov
On Tue, Dec 18, 2018 at 08:34:25AM +, Brooks Davis wrote: > On Mon, Dec 17, 2018 at 03:58:05PM -0500, Kurt Lidl wrote: > > Alexander Lochmann writes: > > > According to git commit e3089a (https://reviews.freebsd.org/D1463) > > > FreeBSD 12.0 i386 uses separate address spaces for kernel and user

Re: Address Collision using i386 4G/4G Memory Split

2018-12-18 Thread Brooks Davis
On Mon, Dec 17, 2018 at 03:58:05PM -0500, Kurt Lidl wrote: > Alexander Lochmann writes: > > According to git commit e3089a (https://reviews.freebsd.org/D1463) > > FreeBSD 12.0 i386 uses separate address spaces for kernel and user > > space. So basically two memory areas, one in each space, can have

Re: Address Collision using i386 4G/4G Memory Split

2018-12-17 Thread Konstantin Belousov
On Mon, Dec 17, 2018 at 02:51:48PM +0100, Alexander Lochmann wrote: > Hi folks! > > According to git commit e3089a (https://reviews.freebsd.org/D1463) > FreeBSD 12.0 i386 uses separate address spaces for kernel and user > space. So basically two memory areas, one in each space, can have the > same

Re: Address Collision using i386 4G/4G Memory Split

2018-12-17 Thread Kurt Lidl
Alexander Lochmann writes: According to git commit e3089a (https://reviews.freebsd.org/D1463) FreeBSD 12.0 i386 uses separate address spaces for kernel and user space. So basically two memory areas, one in each space, can have the same address. Is this possible with FreeBSD 12.0? Is this likely t

Address Collision using i386 4G/4G Memory Split

2018-12-17 Thread Alexander Lochmann
Hi folks! According to git commit e3089a (https://reviews.freebsd.org/D1463) FreeBSD 12.0 i386 uses separate address spaces for kernel and user space. So basically two memory areas, one in each space, can have the same address. Is this possible with FreeBSD 12.0? Is this likely to happen? On my o