search for: assert32flat

...> It's not tracking allocation. It is that accessing memory above 1 MiB > is incredibly painful in the BIOS environment, which basically means > MMIO is inaccessible. Oh, you mean in real mode. SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. There are loads of ASSERT32FLAT()s in the code to make sure of this. Regards, Anthony Liguori > > -hpa > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordom...

...> It's not tracking allocation. It is that accessing memory above 1 MiB > is incredibly painful in the BIOS environment, which basically means > MMIO is inaccessible. Oh, you mean in real mode. SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. There are loads of ASSERT32FLAT()s in the code to make sure of this. Regards, Anthony Liguori > > -hpa > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordom...

On 06/06/13 08:34, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk > reads/writes are done in 16bit mode since it should work from int13 > interrupt handler. Exactly. It's "only" the initialization code which has ASSERt32FLAT() all...

On 06/06/13 08:34, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk > reads/writes are done in 16bit mode since it should work from int13 > interrupt handler. Exactly. It's "only" the initialization code which has ASSERt32FLAT() all...

...mory above 1 MiB >> > is incredibly painful in the BIOS environment, which basically means >> > MMIO is inaccessible. >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk > reads/writes are done in 16bit mode since it should work from int13 > interrupt handler. The only way I know to access MMIO bars from 16 bit > is to use SMM which we do not ha...

...mory above 1 MiB >> > is incredibly painful in the BIOS environment, which basically means >> > MMIO is inaccessible. >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk > reads/writes are done in 16bit mode since it should work from int13 > interrupt handler. The only way I know to access MMIO bars from 16 bit > is to use SMM which we do not ha...

...BIOS environment, which basically means > > >> > MMIO is inaccessible. > > >> > > >> Oh, you mean in real mode. > > >> > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > >> > > > Well, not exactly. Initialization is done in 32bit, but disk > > > reads/writes are done in 16bit mode since it should work from int13 > > > interrupt handler. The only way I know to access MMIO bars from 16 b...

...BIOS environment, which basically means > > >> > MMIO is inaccessible. > > >> > > >> Oh, you mean in real mode. > > >> > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > >> > > > Well, not exactly. Initialization is done in 32bit, but disk > > > reads/writes are done in 16bit mode since it should work from int13 > > > interrupt handler. The only way I know to access MMIO bars from 16 b...

...n 06/06/13 08:34, Gleb Natapov wrote: > > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: > >> > >> Oh, you mean in real mode. > >> > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > >> > > Well, not exactly. Initialization is done in 32bit, but disk > > reads/writes are done in 16bit mode since it should work from int13 > > interrupt handler. > > Exactly. It's "only" the initialization code...

...>> > MMIO is inaccessible. > > > > >> > > > > >> Oh, you mean in real mode. > > > > >> > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > >> > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > > interrupt handler. The only...

...>> > MMIO is inaccessible. > > > > >> > > > > >> Oh, you mean in real mode. > > > > >> > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > >> > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > > interrupt handler. The only...

...> > > >> > > > > > > >> Oh, you mean in real mode. > > > > > > >> > > > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > > > >> > > > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > &gt...

...> > > >> > > > > > > >> Oh, you mean in real mode. > > > > > > >> > > > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > > > >> > > > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > &gt...

...on. It is that accessing memory above 1 MiB > > is incredibly painful in the BIOS environment, which basically means > > MMIO is inaccessible. > > Oh, you mean in real mode. > > SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > There are loads of ASSERT32FLAT()s in the code to make sure of this. > Well, not exactly. Initialization is done in 32bit, but disk reads/writes are done in 16bit mode since it should work from int13 interrupt handler. The only way I know to access MMIO bars from 16 bit is to use SMM which we do not have in KVM. -- Gleb.

...is incredibly painful in the BIOS environment, which basically means > >> > MMIO is inaccessible. > >> > >> Oh, you mean in real mode. > >> > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > >> > > Well, not exactly. Initialization is done in 32bit, but disk > > reads/writes are done in 16bit mode since it should work from int13 > > interrupt handler. The only way I know to access MMIO bars from 16 bit > > is to u...

...lly means > > > >> > MMIO is inaccessible. > > > >> > > > >> Oh, you mean in real mode. > > > >> > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > >> > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > interrupt handler. The only way I know to access...

...ccessible. > > > > > >> > > > > > >> Oh, you mean in real mode. > > > > > >> > > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > > >> > > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > > reads/writes are done in 16bit mode since it should work from int13 > > > > > > interrup...

...> > > > > > > > >> Oh, you mean in real mode. > > > > > > > >> > > > > > > > >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. > > > > > > > >> There are loads of ASSERT32FLAT()s in the code to make sure of this. > > > > > > > >> > > > > > > > > Well, not exactly. Initialization is done in 32bit, but disk > > > > > > > > reads/writes are done in 16bit mode since it should work from int13 > &gt...

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/05/2013 02:50 PM, Anthony Liguori wrote: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> On 06/05/2013 09:20 AM, Michael S. Tsirkin wrote: >>>> >>>> Spec says IO and memory can be enabled/disabled, separately. >>>> PCI Express spec says devices

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/05/2013 02:50 PM, Anthony Liguori wrote: >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> On 06/05/2013 09:20 AM, Michael S. Tsirkin wrote: >>>> >>>> Spec says IO and memory can be enabled/disabled, separately. >>>> PCI Express spec says devices