Yang, Sheng wrote:
On Thursday 31 July 2008 10:43:20 Yang, Sheng wrote:
From ba05b3c821400127074f65ee4d172fabbe3524cd Mon Sep 17 00:00:00
2001 From: Sheng Yang [EMAIL PROTECTED]
Date: Thu, 31 Jul 2008 10:39:24 +0800
Subject: [PATCH] kvm: bios: Put AP boot up code to 0x1000
Rather than
Am Dienstag, 29. Juli 2008 schrieb Avi Kivity:
They all start with 0 AFAIK (kvm also starts with 0, it just wants it to
be a special slot).
Now my brain hurts
Ok, so I read this as: ppc, ia64 and s390 can start with slot 0 and it is not a
special slot.
On x86 slot 0 is special, if
*
I will go offline starting tonight, for about a week. If all goes well,
I will have no Internet connectivity. I'll be back on August 10.
Stephen/Andrew, if kvm.git gives you trouble, please drop it temporarily
from linux-next.
Andrea, I see Linus hasn't pulled the kvm-mmu notifiers glue.
Linus, please pull from repo branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
kvm-updates-2.6.27
to receive the mmu notifiers support for kvm. This allows the full range
of Linux virtual memory management, such as swapping and page migration,
to apply to kvm virtual
Amit Shah wrote:
'opaque' fields can be later made to point to other structures
without changing the structure itself. This is an advantage. Will
the kvm_pic struct be needed to change in the future? Very
unlikely. So we can rename it to struct kvm *, however, that gives
us no real benefit as
On Thu, Jul 31, 2008 at 04:34:03AM +0100, TJ wrote:
This patch fails to achieve the intended aim since the values assigned
to audio-*-list are hard-reset in several places in qemu/configure, both
for initial variable 'declaration' and when setting sane defaults in the
absence of command-line
On Thursday 31 July 2008 14:41:04 Avi Kivity wrote:
Yang, Sheng wrote:
On Thursday 31 July 2008 10:43:20 Yang, Sheng wrote:
From ba05b3c821400127074f65ee4d172fabbe3524cd Mon Sep 17
00:00:00 2001 From: Sheng Yang [EMAIL PROTECTED]
Date: Thu, 31 Jul 2008 10:39:24 +0800
Subject: [PATCH]
Yang, Sheng wrote:
On Thursday 31 July 2008 14:41:04 Avi Kivity wrote:
Yang, Sheng wrote:
On Thursday 31 July 2008 10:43:20 Yang, Sheng wrote:
From ba05b3c821400127074f65ee4d172fabbe3524cd Mon Sep 17
00:00:00 2001 From: Sheng Yang [EMAIL PROTECTED]
Date: Thu, 31 Jul 2008
Carlo Marcelo Arenas Belon wrote:
Not really sure which patch you are referring to as there is none on this
email, but the one I sent originally in this thread with this subject and
that I got back from the list and that is in the mail archive seem to work
correctly as shown below :
kvm-72 $
Mohammed Gamal wrote:
This patch adds 'cld' and 'std' instructions to the emulator
I presume for big real mode? Which guest wants it?
@@ -1755,6 +1755,14 @@ special_insn:
ctxt-eflags |= X86_EFLAGS_IF;
c-dst.type = OP_NONE; /* Disable writeback. */
Andrew Morton wrote:
arch/ia64/kvm/../../../virt/kvm/ioapic.c:42:17: irq.h: No such file or directory
arch/ia64/kvm/../../../virt/kvm/ioapic.c: In function `__kvm_ioapic_update_eoi':
arch/ia64/kvm/../../../virt/kvm/ioapic.c:296: error: implicit declaration of
function `kvm_notify_acked_irq'
Nikola Ciprich wrote:
Hi, sure.
hope it's OK
Applied, thanks. Please signoff in the future.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Christian Borntraeger wrote:
Am Dienstag, 29. Juli 2008 schrieb Avi Kivity:
They all start with 0 AFAIK (kvm also starts with 0, it just wants it to
be a special slot).
Now my brain hurts
Ok, so I read this as: ppc, ia64 and s390 can start with slot 0 and it is not a
special
On Thu, Jul 31, 2008 at 11:39:03AM +0300, Avi Kivity wrote:
Andrea, I see Linus hasn't pulled the kvm-mmu notifiers glue. If that's
still the case in a few days, please resolve any issues and send it
yourself.
Ok.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
Avi Kivity wrote:
Christian Borntraeger wrote:
Am Dienstag, 29. Juli 2008 schrieb Avi Kivity:
They all start with 0 AFAIK (kvm also starts with 0, it just wants
it to be a special slot).
Now my brain hurts
Ok, so I read this as: ppc, ia64 and s390 can start with slot 0 and
it is
Christian Borntraeger wrote:
Something like that? But then I get the following warning on non-x86:
libkvm.c:77: warning: 'kvm_supports_set_tss_addr' defined but not used
Should I mask the wrapper with config x86 as well?
If we rename the helper, kvm_wants_special_memslot_0() (reversing the
Marcelo, the balloon was last seen drifting over your territory. Care
to brush it up and send it over?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo
Here is an update patch.
This adds 'cld' and 'std' instructions. The group table entries are
added.
Signed-off-by: Mohammed Gamal [EMAIL PROTECTED]
---
arch/x86/kvm/x86_emulate.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/x86_emulate.c
The emulator only supported opcode 0xb8 for mov r,imm. However 0xb9-0xbf
are also mov r,imm. This patch adds support for these instructions.
Signed-off-by: Mohammed Gamal [EMAIL PROTECTED]
---
arch/x86/kvm/x86_emulate.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff
I guess I am doing something very dumb, but when I try to compile kvm-72 on
z900 architecture (actually Hercules) I immediately get a compile error:
zgentoo kvm-72 # ./configure --disable-gfx-check --disable-sdl
Install prefix/usr/local
BIOS directory/usr/local/share/qemu
binary
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on both the
source and destination nodes. After migration has taken place
On Thu, Jul 31, 2008 at 04:50:51PM +0200, Chris Lalancette wrote:
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on
The irq ack during pic reset has three problems:
- Ignores slave/master PIC, using gsi 0-8 for both.
- Generates an ACK even if the APIC is in control.
- Depends upon IMR being clear, which is broken if the
irq was masked at the time it was generated.
The last one causes the BIOS to hang after
Chris Lalancette wrote:
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on both the
source and destination nodes. After
Yang, Sheng wrote:
Rather than 0x1, which can be overrided by userspace program like
grub.
Could you please explain this problem?
If i don't misunderstand this smp_ap_boot_code_start from rombios32start.S
gets copied to AP_BOOT_CODE and then there is a broadcast INIT and SIPI.
After the
On Friday 01 August 2008 05:15:11 Sebastian Herbszt wrote:
Yang, Sheng wrote:
Rather than 0x1, which can be overrided by userspace program
like grub.
Could you please explain this problem?
If i don't misunderstand this smp_ap_boot_code_start from
rombios32start.S gets copied to
Avi Kivity wrote:
Zhang, Xiantao wrote:
Avi Kivity wrote:
Zhang, Xiantao wrote:
From c8c8c5a6b3ff943cb645f9ac4ef169490f14cd08 Mon Sep 17 00:00:00
2001 From: Zhang Xiantao [EMAIL PROTECTED]
Date: Fri, 25 Jul 2008 16:50:30 +0800
Subject: [PATCH] KVM: external module: Moving x86-speicif
Ben-Ami Yassour wrote:
+#define assigned_dev_ioport_write(suffix)
\
+static void assigned_dev_ioport_write##suffix(void *opaque,
\ + uint32_t addr,
\
+ uint32_t value)
\
+{
\
+
28 matches
Mail list logo
