pseries: interrupt controller should not have a 'reg' property
The interrupt controller presented in the device tree for the pseriesmachine is manipulated by the guest only through hypervisor calls. Ithas no real or emulated registers for the guest to access....
MPC8544DS: Generate CPU nodes on init
With this patch, we generate CPU nodes in the machine initialization, givingus the freedom to generate as many nodes as we want and as the machine supports,but only those.
This is a first step towards a much cleaner device tree generation...
PPC: E500: Bump CPU count to 15
Now that we have everything in place, make the machine descriptionaware of the fact that we can now handle 15 virtual CPUs!
Signed-off-by: Alexander Graf <agraf@suse.de>
v1 -> v2:
- Max cpus is 15 because of MPIC
PPC: Enable to use PAPR with PR style KVM
When running PR style KVM, we need to tell the kernel that we wantto run in PAPR mode now. This means that we need to pass some moreregister information down and enable papr mode. We also need to alignthe HTAB to htab_size boundary....
PPC: SPAPR: Use KVM function for time info
One of the things we can't fake on PPC is the timer speed. Sowe need to extract the frequency information from the host andput it back into the guest device tree.
Luckily, we already have functions for that from the non-pseries...
pseries: Bugfixes for interrupt numbering in XICS code
The implementation of the XICS interrupt controller contains several(difficult to trigger) bugs due to the fact that we were not 100%consistent with which irq numbering we used. In most places, global...
pseries: Add a phandle to the xicp interrupt controller device tree node
Future devices we will be adding to the pseries machine (e.g. PCI) willneed nodes in the device tree which explicitly reference the top-levelinterrupt controller via interrupt-parent or interrupt-map properties....
PPC: E500: Update cpu-release-addr property in cpu nodes
The guest OS wants to know where the guest spins, so let's tell him whileupdating the CPU nodes with the frequencies anyways.
- use new spin table address
PPC: E500: Add PV spinning code
CPUs that are not the boot CPU need to run in spinning code to check if theyshould run off to execute and if so where to jump to. This usually happensby leaving secondary CPUs looping and checking if some variable in memory...
PPC: E500: Remove unneeded CPU nodes
We should only keep CPU nodes in the device tree around that we really havevirtual CPUs for. So remove all superfluous entries that we just keep therein case someone wants to create a lot of vCPUs.
View revisions
Also available in: Atom