Hi, all
I am trying to figure out why QEMU put some constraints on block
linking (chaining). Take x86 as an example, there are two places
put constraints on block linking, gen_goto_tb and cpu_exec.
- gen_goto_tb (target-i386/translate.c) ---
/* NOTE: we handle the
Le mercredi 17 août 2011 à 17:35 -0500, Anthony Liguori a écrit :
On 08/17/2011 03:46 PM, Bryce Lanham wrote:
These patches greatly expand Motorola 68k emulation within qemu, and are
what I used as a basis for my
Google Summer of Code project to add NeXT hardware support to QEMU.
Please
Hi, all
I am trying to figure out why QEMU put some constraints on block
linking (chaining). Take x86 as an example, there are two places
put constraints on block linking, gen_goto_tb and cpu_exec.
- gen_goto_tb (target-i386/translate.c) ---
/* NOTE: we handle
If we link a TB with another TB from the different page, then the
second TB may disappear when the memory mapping changes and the
subsequent direct jump from the first TB will crash qemu.
Perhaps the guest OS swap the second TB out of the guest memory,
is it what you mean?
I meant TLB
Le -10/01/-28163 20:59, Laurent Vivier a écrit :
Le mercredi 17 août 2011 à 17:35 -0500, Anthony Liguori a écrit :
On 08/17/2011 03:46 PM, Bryce Lanham wrote:
These patches greatly expand Motorola 68k emulation within qemu, and are what I
used as a basis for my
Google Summer of Code project
Le 18 août 2011 à 13:12, François Revol re...@free.fr a écrit :
Le -10/01/-28163 20:59, Laurent Vivier a écrit :
Le mercredi 17 août 2011 à 17:35 -0500, Anthony Liguori a écrit :
On 08/17/2011 03:46 PM, Bryce Lanham wrote:
These patches greatly expand Motorola 68k emulation within
On Wed, Aug 17, 2011 at 08:40:57PM +0200, Kevin Wolf wrote:
Am 17.08.2011 18:41, schrieb Stefan Hajnoczi:
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
Thanks, applied to the block branch.
(But is it really helpful to include sector numbers in the error
message? Especially
Hi,
I'm running VM on kvm-qemu hyper visor . I need to access the serail port on
the VM ,
I tried the sample code to read/write com port but I get port error when
ever I tried write something to the port(dev/ttyS0) .
the same code work fine on the normal OS .. is it the same way as normal OS
On 08/17/2011 06:30 PM, Bryce Lanham wrote:
Ugh, I'm sorry about that. This is why I should test before using
unfamiliar tools. Someone suggested using git format-patch/git
send-email instead of a big patch.
That's definitely preferred actually, but you should look at breaking
this into
On Tue, 16 Aug 2011, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
Cc: malc av1...@comtv.ru
This patchset breaks both gus and sb16 for me.
[..snip..]
--
mailto:av1...@comtv.ru
This makes the tracing infrastructure available to users of g_new().
Signed-off-by: Avi Kivity a...@redhat.com
---
qemu-common.h |1 +
qemu-malloc.c | 15 +++
vl.c |1 +
3 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/qemu-common.h b/qemu-common.h
I've been experimenting with multiple USB2 buses, and device physical port
addressing. It seems if you have 2 devices of the same type on the same
port, but in different buses, you get a bogus VMState assertion failure
# qemu-system-x86_64 \
-nodefconfig -nodefaults \
-vnc
Confirmed under Win 7 64-bit.
Also does same thing on v10.6, v11.1, v12.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/567380
Title:
qemu-img fails to create images = 4G
Status in QEMU:
Hi Laurent,
El 18/08/2011, a las 15:02, Laurent Vivier escribió:
Le 18 août 2011 à 13:12, François Revol re...@free.fr a écrit :
Le -10/01/-28163 20:59, Laurent Vivier a écrit :
Le mercredi 17 août 2011 à 17:35 -0500, Anthony Liguori a écrit :
On 08/17/2011 03:46 PM, Bryce
Le jeudi 18 août 2011 à 20:42 +0100, Natalia Portillo a écrit :
Hi Laurent,
Hi Natalia,
El 18/08/2011, a las 15:02, Laurent Vivier escribió:
Le 18 août 2011 à 13:12, François Revol re...@free.fr a écrit :
Le -10/01/-28163 20:59, Laurent Vivier a écrit :
Le mercredi 17
Hi Laurent,
El 18/08/2011, a las 20:57, Laurent Vivier escribió:
Le jeudi 18 août 2011 à 20:42 +0100, Natalia Portillo a écrit :
Hi Laurent,
Hi Natalia,
El 18/08/2011, a las 15:02, Laurent Vivier escribió:
Le 18 août 2011 à 13:12, François Revol re...@free.fr a écrit :
Le
For this functionality to work with KVM, this kernel patch is required:
http://www.spinics.net/lists/kvm-ppc/msg03053.html
Scott Wood (4):
kvm: update linux-headers
kvm: ppc: booke206: use MMU API
ppc: booke206: use MAV=2.0 TSIZE definition, fix 4G pages
ppc: booke206: add info tlb
Needed for PPC MMU API support.
Signed-off-by: Scott Wood scottw...@freescale.com
---
v2: new to v2
linux-headers/asm-powerpc/kvm.h | 54 -
linux-headers/asm-x86/kvm_para.h | 14 ++
linux-headers/linux/kvm.h| 41
Share the TLB array with KVM. This allows us to set the initial TLB
both on initial boot and reset, is useful for debugging, and could
eventually be used to support migration.
Signed-off-by: Scott Wood scottw...@freescale.com
---
v2 (was 1/3 in v1):
updated for kernel API change, removed kernel
Signed-off-by: Scott Wood scottw...@freescale.com
---
v2 (was 3/3 in v1): no change
hmp-commands.hx |2 +-
monitor.c |5 ++-
target-ppc/cpu.h|2 +
target-ppc/helper.c | 88 +++
4 files changed, 94 insertions(+), 3
This definition is backward compatible with MAV=1.0 as long as
the guest does not set reserved bits in MAS1/MAS4.
Also, fix the shift in booke206_tlb_to_page_size -- it's the base
that should be able to hold a 4G page size, not the shift count.
Signed-off-by: Scott Wood scottw...@freescale.com
Le jeudi 18 août 2011 à 21:13 +0100, Natalia Portillo a écrit :
Hi Laurent,
El 18/08/2011, a las 20:57, Laurent Vivier escribió:
Le jeudi 18 août 2011 à 20:42 +0100, Natalia Portillo a écrit :
Hi Laurent,
Hi Natalia,
El 18/08/2011, a las 15:02, Laurent Vivier escribió:
On 2011-08-17 16:48, Avi Kivity wrote:
On 08/17/2011 04:38 PM, Avi Kivity wrote:
The mmio code has
s-plane_updated |= mask; /* only used to detect font
change */
aren't we losing it? we could easily recover it via dirty logging.
Yes, I forgot to forward-port plane_updated =
Am 15.08.2011 11:00, schrieb Nicholas Thomas:
Current behaviour if a read fails is for the acb to not get finished.
This causes an infinite loop in bdrv_read_em (block.c). The read failure
never gets reported to the guest and if the error condition clears, the
process never recovers.
With
Je suis le fils de l'ancien ministre de la Guinée (Mariame Sy Diallo) mais je
vis actuellement en Angleterre, j'ai trouvé votre adresse à la chambre de
commerce ici à Londres, j'ai besoin de votre aide pour investir au Maroc ou Algérie ou en Tunisie.
Si vous êtes intéressé à ma demandes'il vous
Add dots keypresses support to the baum braille device.
Signed-off-by: Samuel Thibault samuel.thiba...@ens-lyon.org
diff --git a/hw/baum.c b/hw/baum.c
index 21326ae..131348c 100644
--- a/hw/baum.c
+++ b/hw/baum.c
@@ -1,7 +1,7 @@
/*
* QEMU Baum Braille Device
*
- * Copyright (c) 2008, 2011
Hi,
El 18/08/2011, a las 21:51, Laurent Vivier escribió:
Le jeudi 18 août 2011 à 21:13 +0100, Natalia Portillo a écrit :
Hi Laurent,
El 18/08/2011, a las 20:57, Laurent Vivier escribió:
Le jeudi 18 août 2011 à 20:42 +0100, Natalia Portillo a écrit :
Hi Laurent,
Hi Natalia,
El
Oops, sorry, the previous patch had a debugging leftover, here it is
again.
Add dots keypresses support to the baum braille device.
Signed-off-by: Samuel Thibault samuel.thiba...@ens-lyon.org
diff --git a/hw/baum.c b/hw/baum.c
index 21326ae..0b29498 100644
--- a/hw/baum.c
+++ b/hw/baum.c
@@
On Thu, Aug 18, 2011 at 12:28 PM, Peter Maydell
peter.mayd...@linaro.org wrote:
On 18 August 2011 05:16, Zhi Yong Wu zwu.ker...@gmail.com wrote:
I have also met this problem on fedora 15 today. Currently i disable
werror option to build successfully. How to completely this problem
regardless
More generally and not x86-specific, there are problems with
the multithreaded user-mode support which I suspect exist because
nobody has ever sat down and worked out a coherent design for it,
including what might need to be thread-local and what locking
is required. So the result is that it
On 19 August 2011 03:59, 陳韋任 che...@iis.sinica.edu.tw wrote:
More generally and not x86-specific, there are problems with
the multithreaded user-mode support which I suspect exist because
nobody has ever sat down and worked out a coherent design for it,
including what might need to be
On Thu, Aug 18, 2011 at 6:48 PM, Avi Kivity a...@redhat.com wrote:
This makes the tracing infrastructure available to users of g_new().
Signed-off-by: Avi Kivity a...@redhat.com
---
qemu-common.h | 1 +
qemu-malloc.c | 15 +++
vl.c | 1 +
3 files changed, 17
On 18 August 2011 18:48, Avi Kivity a...@redhat.com wrote:
+static GMemVTable gmemvtable = {
+ .malloc = qemu_malloc,
+ .realloc = qemu_realloc,
+ .free = qemu_free,
+};
+
+/**
+ * qemu_malloc_init: initialize memory management
+ */
+void qemu_malloc_init(void)
+{
+
At 08/18/2011 11:15 PM, Avi Kivity Write:
On 08/17/2011 08:22 PM, Wen Congyang wrote:
At 08/17/2011 04:37 PM, Wen Congyang Write:
At 07/04/2011 05:43 PM, Michael S. Tsirkin Write:
This adds support for a standard pci to pci bridge,
enabling support for more than 32 PCI devices in the
34 matches
Mail list logo
