> -----Original Message----- > From: Rahul Kulkarni [mailto:rkulk...@force10networks.com] > Sent: Thursday, April 02, 2009 7:47 AM > To: Hollis Blanchard > Cc: Liu Yu-B13201; kvm-ppc@vger.kernel.org > Subject: RE: PowerPC KVM build directions > > Thanks Hollis. See inline.. > > -----Original Message----- > From: Hollis Blanchard [mailto:holl...@us.ibm.com] > Sent: Wednesday, April 01, 2009 1:07 PM > To: Rahul Kulkarni > Cc: Liu Yu-B13201; kvm-ppc@vger.kernel.org > Subject: Re: PowerPC KVM build directions > > (CCing kvm-ppc list.) > > Great, so you've managed to get Linux running under KVM on e500? > Rahul>> Yes. I can run Linux under kvm on a e500 based platform > > Option 2 requires that qemu set up the initial VM state > exactly how firmware > would have. That means loading the same kernel executable > into the same memory > location, same initial register state, initial TLB mappings, > same (emulated) > system hardware state, etc. > > For Linux, we used option 2. After loading the ELF file into > guest memory, > qemu creates the device tree (hierarchical data structure > describing the > physical system) and passes its address to Linux in a GPR, > which is a job > usually performed by u-boot. The decision really depends on > the functionality > and complexity of your firmware. > > Rahul>>I'll start with option 2. Initial goal would be to > run a NetBSD guest on an emulated e500/8544 platform - which > Liu has added support for recently in qemu/kvm to run as a > linux guest. Our eventual goal is to emulate an e500/8548 CDS > based platform..
Guest 8544 is just a name of e500 VM. Actually it hasn't implement most of 8544's devices and it can have device which real 8544 doesn't have. I once had named it to be 85xx... The reason I chose 8544 as it's name is that the e500 kvm is first developed on 8544 board and 8544 has pci controller which virtual devices in qemu only connect with... So if that name dosen't bother you, you can just add the device you want to support into the guest 8544. > Since KVM supports a NetBSD 4.0 guest (I > think) and 8544/e500 emulation is already present in qemu -- > theoretically the first part should work...but I recall Liu > mentioning that there might be some OS specific quirks > present in the port...and that was what I my question was > hinting at earlier.. There must be a lot of differences between Linux and NetBSD. So the design of kvmppc may not be careful considerate. The main trick is to hijack the system interrupts. You should check if this part of code cater to NetBSD. Context switch needs to be taken care as well. At least there is one thing I can point out. See comments in the file booke_interrupts.S line 195. :-) -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
