On Wed, Feb 18, 2015 at 04:38:43PM -0800, Ameya Palande wrote:
On Wed, Feb 18, 2015 at 12:15 PM, Kevin O'Connor <kevin(a)koconnor.net> wrote:
On Tue, Feb 17, 2015 at 02:00:49PM -0800, Ameya Palande wrote:
Use barrier() for memory mapped IO functions.
This fixes pvscsi driver to boot on QEMU's pvscsi controller.
qemu -m 512 --enable-kvm -device pvscsi,id=pvscsi0
Thanks. I didn't think it was standard for a barrier to be present in
these functions, but I now see that Linux also uses barrier here. So,
I've committed your patch (with a couple of minor changes).
Thanks for applying this patch!
Since memory mapped read and write are now protected by barriers, how
should we deal about use of (potentially redundant) barriers in:
I think redundant barriers should ultimately be removed.
doesn't use barrier() at all!
Wondering if that was correct?
That is a good quesiton. I had not noticed any issues in this area
before, but I wasn't looking explicitly for them.
for tracking down the PVSCSI problem.
I could get it booting only under QEMU. I wanted to test seabios under
ESXi to make sure it really boots under ESXi's pvscsi implementation.
Does anyone know a way to get seabios running under ESXi so that
pvscsi validity can be checked?
I'm not familiar with ESXi, so I can't help here.