Linus,
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
Necessary for KVM without irqchip to function on ARM64. Allows to use
software GICv2 emulation where hardware acceleration is not available.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
arch/arm/include/asm/kvm_host.h | 5 +
arch/arm64/include/asm/kvm_asm.h | 1 +
This patch set brings back functionality which was broken in v4.1. The
overall goal is to eventually enable using virtual timer too, but for now
changes affect only a possibility to run KVM itself. The guest currently
has to use another timer because there's no API to propagate interrupts
from
Makes qemu working again with kernel-irqchip=off option
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
arch/arm/kvm/arm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index d9631ec..5668c4e 100644
--- a/arch/arm/kvm/arm.c
+++
Allows to use KVM on hardware without vGIC. Interrupt controller has to be
emulated in userspace in this case.
-ENODEV return code from probe function means there's no GIC at all. -ENXIO
happens when, for example, there is GIC node in the device tree, but it does
not specify vGIC resources.
On 14/07/15 13:06, Pavel Fedin wrote:
Necessary for KVM without irqchip to function on ARM64. Allows to use
software GICv2 emulation where hardware acceleration is not available.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
arch/arm/include/asm/kvm_host.h | 5 +
Hello!
You may want to check commit 8a14849, which makes this whole patch
irrelevant.
Thank you very much for pointing out, i will recheck.
My patches are based on linux-stable.git, should i base them on something else?
Also, we do check whether or not the GIC is enabled for a given VM,
Hello!
You may want to check commit 8a14849, which makes this whole patch
irrelevant.
I have tested, the new code just works without patch No 0003. Simply throw it
away from the set.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe
(adding back the kvm mailing list)
On Tue, Jul 14, 2015 at 1:12 AM, C. Bröcker
c.broc...@intercollect.com wrote:
On 14-7-2015 10:04, Hansa wrote:
On 13-7-2015 20:57, David Matlack wrote:
On Thu, Jun 18, 2015 at 10:26 AM, David Matlack dmatl...@google.com
wrote:
On Thu, Jun 18, 2015 at
On Tue, 2015-07-14 at 20:43 +0200, Thomas Huth wrote:
Any suggestions how to fix this? Simply revert 587f83e8dd50d? Use
mdelay() instead of msleep() in rtas_busy_delay()? Something more
fancy?
A proper fix would be more fancy, the get_sensor should happen in a
kernel thread instead.
Cheers,
Cross-posting to edk2-devel.
Original sub-thread starts here:
http://thread.gmane.org/gmane.linux.kernel/1952205/focus=1994315
On 07/13/15 17:15, Xiao Guangrong wrote:
On 07/13/2015 11:13 PM, Paolo Bonzini wrote:
On 13/07/2015 16:45, Xiao Guangrong wrote:
+/* MTRR is completely
The long delay that Alex reported (for the case when all guest memory
was set to UC up-front) is due to the fact that the SEC phase of OVMF
decompresses an approximately 1712 KB sized, LZMA-compressed blob, to
approx. 896 KB worth of PEI drivers and 8192 KB worth of DXE and UEFI
drivers --
On 07/14/15 23:15, Paolo Bonzini wrote:
The long delay that Alex reported (for the case when all guest memory
was set to UC up-front) is due to the fact that the SEC phase of OVMF
decompresses an approximately 1712 KB sized, LZMA-compressed blob, to
approx. 896 KB worth of PEI drivers and 8192
On 14-7-2015 19:16, David Matlack wrote:
(adding back the kvm mailing list)
On Tue, Jul 14, 2015 at 1:12 AM, C. Bröcker
c.broc...@intercollect.com wrote:
On 14-7-2015 10:04, Hansa wrote:
On 13-7-2015 20:57, David Matlack wrote:
On Thu, Jun 18, 2015 at 10:26 AM, David Matlack
On 2015-07-14 14:29:11, Laszlo Ersek wrote:
On 07/14/15 23:15, Paolo Bonzini wrote:
The long delay that Alex reported (for the case when all guest memory
was set to UC up-front) is due to the fact that the SEC phase of OVMF
decompresses an approximately 1712 KB sized, LZMA-compressed blob,
Actually, MMIO will be used in OVMF SEC phase if local APIC is consumed.
(SecPeiDebugAgentLib will consume local APIC timer for communication between
debugger TARGET/HOST).
So, I suggest to keep MTRR default value to UC and set the code range to WB, or
set default value to WB and set Local
Hi all!
A colleague recently ran into some kernel BUG messages that happen when
hot-plugging a virtio disk to a KVM guest on powerpc (with virsh
attach-disk), and IIRC CONFIG_DEBUG_ATOMIC_SLEEP enabled. I've tried to
re-create the problem with an up-to-date kernel (4.2.0-rc2) and the
problem
17 matches
Mail list logo
