From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest portion of the device tree based host->guest
communication. Using the device tree infrastructure this patch implements
kvm_para_available and kvm_arch_para_features (in this patch just the
infrastructure, no specifi
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest handling for the magic page mechanism. A Hypervisor
can modify the device tree passed to the guest. Using that already existing
interface a guest can simply detect available hypervisor features and agree
on the supporte
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds the guest portion of the hypercall infrastructure, basically an
illegal instruction with a defined layout.
See http://kvm.qumranet.com/kvmwiki/PowerPC_Hypercall_ABI for more detail
on the hypercall ABI for powerpc.
Signed-off-by: Chr
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch to kvm-userspace connects the other host & guest patches in this
series. On guest initialization it checks the hosts capabilities for the
magicpage mechanism. If available the device tree passed to the guest gets the
"hypervi
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch series implements a paravirtualization interface using:
- the device tree mechanism to pass hypervisor informations to the guest
- hypercalls for guest->host calls
- an example exploiter of that interface (magic page)
This i
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds the host part of the magic page registration. This is a memory
area of the guest granted to the host.
The patch just introduces the infrastruture to receive the guest paddr.
This is work in progress and it is intended to later on us
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds the host portion of the hypercall infrastructure which receives
the guest calls - no specific hcall function is implemented in this patch.
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
---
[diffstat]
arch/powerpc/k
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds the guest portion of the hypercall infrastructure, basically an
illegal instruction with a defined layout.
See http://kvm.qumranet.com/kvmwiki/PowerPC_Hypercall_ABI for more detail
on the hypercall ABI for powerpc.
Signed-off-by: Chr
From: Christian Ehrhardt <[EMAIL PROTECTED]>
Dependent on the already existing CONFIG_KVM_GUEST config option this patch
changes wrteei to wrtee allowing the hypervisor to rewrite those to nontrapping
instructions. Maybe we should split the kvm guest otpimizations in two parts
one f
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch series implements a paravirtualization interface using:
- the device tree mechanism to pass hypervisor informations to the guest
- hypercalls for guest->host calls
- an example exploiter of that interface (magic page)
Version 2
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest handling for the magic page mechanism. A Hypervisor
can modify the device tree passed to the guest. Using that already existing
interface a guest can simply detect available hypervisor features and agree
on the supporte
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest portion of the device tree based host->guest
communication. Using the device tree infrastructure this patch implements
kvm_para_available and kvm_arch_para_features (in this patch just the
infrastructure, no specifi
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This adds the guest portion of the hypercall infrastructure.
Version 3 now follows the beat ABI, but proposes a new implementation style as
static inline asm functions instead of pure assembler code. That should allow
the compiler to be more fl
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest handling for the magic page mechanism. A Hypervisor
can modify the device tree passed to the guest. Using that already existing
interface a guest can simply detect available hypervisor features and agree
on the supporte
From: Christian Ehrhardt <[EMAIL PROTECTED]>
Version 3 updates:
- guest hypercall infrastructure is now generic (in epapr_hcalls.h)
while the kvm specific functions stay in kvm_para.h
- the hypercalls now use beat style ABI
- dropped the guest coop patch changing wrteei to wrtee (now mf
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds the guest portion of the device tree based host->guest
communication. Using the device tree infrastructure this patch implements
kvm_para_available and kvm_arch_para_features (in this patch just the
infrastructure, no specifi
that is attached, but I would like to wait for Hollis comments on
that before you apply that.
So further Kconfig restrictions are needed, or perhaps a patch. .config
attached.
[...]
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
--- arch/powerpc/kvm/
n 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
=> Region 2 is not detected with our kernel, this later break things like
radeonfb initialization.
--
Grüsse / regards,
Christian Ehr
Johan Borkhuis wrote:
Hello Christian,
Christian Ehrhardt wrote:
Hi,
I tried to use a radeon r200 based graphic card on a sequoia ppc
(440epx) board. I wondered about the initialization of radeonfb that
failed with
__ioremap(): phys addr 0x0 is RAM lr c029cf80
radeonfb (:00:0a.0
00077ff-77ff (f=200)
PCI: Cannot allocate resource region 1 of device :00:0a.1
PCI: Failed to allocate mem resource #0:[EMAIL PROTECTED] for :00:0a.1
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
PCI host bridge /plb/[EMAI
Sergei Shtylyov wrote:
Hello.
Christian Ehrhardt wrote:
Cheers,
Ben.
For comparison I defined DEBUG in the good kernel (arch=ppc) and that
is what the initialization prints (pci ...:0a:1 is the secondary head
of the same graphic card an it's not an issue if thats not allo
for further discussion e.g.
because I don't really know dts syntax ;-)
I hope both changes find their way into the kernel once you are all agreeing
with the new dts content.
I still have issues with my X11, but thats another story.
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Techn
Sergei Shtylyov wrote:
Hello.
Christian Ehrhardt wrote:
[...]
The Documentation of the 440EPx core lists these spaces:
PCI 1 Memory 1 8000 1 BFFF 1GB
I/O 1 E800 1 E800 64KB
I/O 1 E880 1 EBFF 56MB
Having 2
too).
I wanted to ask if there are any known workarounds atm that would allow me to
use my X11 for now?
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
SIZE(para_features) adequate?
yeah I already had this, bit the change was folded into the wrong patch,
fixed now
[...]
Yours Tony
linux.conf.auhttp://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
--
Grüsse / regards,
Christian Ehrhardt
IBM L
Tony Breeds wrote:
On Wed, Jul 23, 2008 at 10:36:44AM +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt <[EMAIL PROTECTED]>
Hi Christian,
This adds the guest portion of the hypercall infrastructure, basically an
illegal instruction with a defined layout.
Se
Tony Breeds wrote:
On Wed, Jul 23, 2008 at 10:36:41AM +0200, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch series implements a paravirtualization interface using:
- the device tree mechanism to pass hypervisor informations to the guest
- hypercal
hange it atm.
When we discussed about that I was too new to the power architecture to
really get all the details, but I assume Hollis and Jimi can answer you
that.
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
in two parts
one for the overhead free optimizations and on for the rest that might add
some complexity for non virtualized execution (like this one).
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
How significant is the performance impact of this change for non-virtualized
s
mon system to be sure.
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Kumar Gala wrote:
On Aug 19, 2008, at 5:36 AM, [EMAIL PROTECTED] wrote:
From: Christian Ehrhardt <[EMAIL PROTECTED]>
Dependent on the already existing CONFIG_KVM_GUEST config option this
patch
changes wrteei to wrtee allowing the hypervisor to rewrite those to
nontrapping
instru
d
(maybe a bit too hidden)
in the [0/4] mail of this series.
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
diff --git a/arch/powerpc/platforms/Kconfig.cputype
b/arch/powerpc/platforms/Kconfig.cputype
index 7f65127..a1386a4 100644
--- a/arch/powerpc/platforms/Kconfig.cputype
+++ b/arch/powerpc/platforms/Kconfig.cputype
@@ -202,7 +202,7 @@ config PPC_STD_MMU_32
config PPC_MM_SLICES
bool
-
-
Kernel panic - not syncing: Attempted to kill the idle task!
Rebooting in 180 seconds..
Christian Ehrhardt wrote:
Hi Ilya,
I just tried your patch on my 440 board because it would help us in
our environment.
Unfortunately I run into a bug on early boot (mark_bootmem).
A log can be found in t
34 matches
Mail list logo
