I need to specify the physical address because I need to ioremap the memory during boot. The production issue I think is a memory limitation. We certainly do use QEMU a lot; but for this the kvm tool is a better fit. \dae On Fri, Aug 26, 2011 at 12:11:03AM +0300, Avi Kivity wrote: > On 08/26/2011 12:00 AM, David Evensky wrote: > >I've tested ivshmem with the latest git pull (had minor trouble > >building on debian sid, vnc and unused var, but trivial to work > >around). > > > >QEMU's -device ivshmem,size=16,shm=/kvm_shmem > > > >seems to function as my proposed > > > > --shmem pci:0xfd000000:16M:handle=/kvm_shmem > > > >except that I can't specify the BAR. I am able to read what > >I'm given, 0xfd000000, from lspci -vvv; but for our application > >we need to be able to specify the address on the command line. > > > >If folks are open, I would like to request this feature in the > >ivshmem. > > It's not really possible. Qemu does not lay out the BARs, the guest > does (specifically the bios). You might be able to re-arrange the > layout after the guest boots. > > Why do you need the BAR at a specific physical address? > > >It would be cool to test our application with QEMU, > >even if we can't use it in production. > > Why can't you use qemu in production? > > -- > I have a truly marvellous patch that fixes the bug which this > signature is too narrow to contain. > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
