Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-22 Thread Vitaly Kuznetsov
Vitaly Kuznetsov writes: > QEMU/KVM guests running nested on top of Hyper-V fail to boot with > virtio-blk-pci disks, the debug log ends with > > Booting from Hard Disk... > call32_smm 0x000edd01 e97a0 > handle_smi cmd=b5 smbase=0x000a > vp notify fe007000 (2) -- 0x0 > vp read fe005000 (1)

Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-04 Thread Laszlo Ersek
On 01/04/18 15:29, Vitaly Kuznetsov wrote: > Laszlo Ersek writes: > In fact, the only writew() needs patching is in vp_notify(), when I > replace it with 'asm volatile' everything works. > >> * Does it make a difference if you disable EPT in the L1 KVM >> configuration? (EPT is probably primaril

Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-04 Thread Vitaly Kuznetsov
Laszlo Ersek writes: > On 01/04/18 11:24, Vitaly Kuznetsov wrote: >> Laszlo Ersek writes: >> >>> Is it possible that the current barrier() is not sufficient for the >>> intended purpose in an L2 guest? >>> >>> What happens if you drop your current patch, but replace >>> >>> __asm__ __volatile

Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-04 Thread Laszlo Ersek
On 01/04/18 11:24, Vitaly Kuznetsov wrote: > Laszlo Ersek writes: > >> Is it possible that the current barrier() is not sufficient for the >> intended purpose in an L2 guest? >> >> What happens if you drop your current patch, but replace >> >> __asm__ __volatile__("": : :"memory") >> >> in the

Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-04 Thread Vitaly Kuznetsov
Laszlo Ersek writes: > Is it possible that the current barrier() is not sufficient for the > intended purpose in an L2 guest? > > What happens if you drop your current patch, but replace > > __asm__ __volatile__("": : :"memory") > > in the barrier() macro definition, with a real, heavy-weight b

Re: [SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-03 Thread Laszlo Ersek
On 01/03/18 14:41, Vitaly Kuznetsov wrote: > QEMU/KVM guests running nested on top of Hyper-V fail to boot with > virtio-blk-pci disks, the debug log ends with > > Booting from Hard Disk... > call32_smm 0x000edd01 e97a0 > handle_smi cmd=b5 smbase=0x000a > vp notify fe007000 (2) -- 0x0 > vp read

[SeaBIOS] [PATCH RFC] x86: use volatile asm for read/write{b, w, l} implementations

2018-01-03 Thread Vitaly Kuznetsov
QEMU/KVM guests running nested on top of Hyper-V fail to boot with virtio-blk-pci disks, the debug log ends with Booting from Hard Disk... call32_smm 0x000edd01 e97a0 handle_smi cmd=b5 smbase=0x000a vp notify fe007000 (2) -- 0x0 vp read fe005000 (1) -> 0x0 handle_smi cmd=b5 smbase=0x000a