Il 13/07/2014 18:17, Alexander Graf ha scritto:
The NVRAM in our Core99 machine really supports 2byte and 4byte accesses
just as well as 1byte accesses. In fact, Mac OS X uses those.
Add support for higher register size granularities.
Signed-off-by: Alexander Graf ag...@suse.de
---
Il 14/07/2014 04:42, Fam Zheng ha scritto:
On Tue, 06/10 14:55, Fam Zheng wrote:
In the case that the lun number is taken by another scsi device, don't
release the existing device siliently, but report an error to user.
Signed-off-by: Fam Zheng f...@redhat.com
Do we want this in 2.1?
Fam
Pascal Heinrich pascalheinrich...@googlemail.com writes:
Hi,
I am trying to implement a qtprogram to bind and unbind usb devices from
an qemu instance.
Via device_add I am able to bind a device to the vm but there is no
command in qmp to list binded devices or I do not find them.
I am
Hi Benjamin,
On 11.07.2014 12:24, Gerd Hoffmann wrote:
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Commit b2eb849d4b1fdb6f35d5c46958c7f703cf64cfef
CVE-2007-1320 - Cirrus LGD-54XX bitblt heap overflow broke
cpu to video blits.
When the ROP function is called from
From: Jason J. Herne jjhe...@us.ibm.com
Add code to kvm_arch_get_registers and kvm_arch_put_registers to
save/restore floating point registers. This missing sync was
unnoticed until migration of userspace that uses fprs.
Signed-off-by: Jason J. Herne jjhe...@us.ibm.com
Signed-off-by: Christian
The following changes since commit ab6d3749c4915cd5692633e321f7745dce06fe77:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20140711-1' into
staging (2014-07-11 17:50:38 +0100)
are available in the git repository at:
git://github.com/cohuck/qemu.git tags/s390x-20140714
On Mon, 2014-07-14 at 09:24 +0200, Peter Lieven wrote:
it seems you have digged into the cirrus code recently. Have you an idea how
to
fix the issue with the graphics corruption for cirrus vga and recent X Server
versions?
E.g. take an Ubuntu 14.04 Desktop CD, boot it into live mode and
On Mon, 2014-07-14 at 17:29 +1000, Benjamin Herrenschmidt wrote:
On Mon, 2014-07-14 at 09:24 +0200, Peter Lieven wrote:
it seems you have digged into the cirrus code recently. Have you an idea
how to
fix the issue with the graphics corruption for cirrus vga and recent X
Server versions?
We've resolved our issues by disabling KSM on the affected nodes. All of
the non-affected nodes didn't have KSM enabled (due to a packaging bug
elsewhere). After disabling KSM, our problems went away gradually in ~3
days.
This means we're no longer affected by this issue (and given the other
On Sat, Jul 12, 2014 at 11:43:37AM +0800, arei.gong...@huawei.com wrote:
From: Gonglei arei.gong...@huawei.com
when hotplug virtio-scsi disks using laio, the aio_nr will
increase in laio_init() by io_setup(), we can see the number by
# cat /proc/sys/fs/aio-nr
128
if the aio_nr attach
Il 13/07/2014 16:41, Alexey Kardashevskiy ha scritto:
Current object_child_foreach() uses QTAILQ_FOREACH() to walk
through children and that makes children removal from the callback
impossible.
This makes object_child_foreach() use QTAILQ_FOREACH_SAFE().
Signed-off-by: Alexey Kardashevskiy
On 14.07.2014 09:29, Benjamin Herrenschmidt wrote:
On Mon, 2014-07-14 at 09:24 +0200, Peter Lieven wrote:
it seems you have digged into the cirrus code recently. Have you an idea how to
fix the issue with the graphics corruption for cirrus vga and recent X Server
versions?
E.g. take an Ubuntu
Il 11/07/2014 13:20, Stefan Hajnoczi ha scritto:
The thread pool has a race condition if two elements complete before
thread_pool_completion_bh() runs:
If element A's callback waits for element B using aio_poll() it will
deadlock since pool-completion_bh is not marked scheduled when the
On Mon, Jul 14, 2014 at 01:55:05AM +, Wangkai (Kevin,C) wrote:
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@redhat.com]
Sent: Friday, July 11, 2014 9:04 PM
To: Wangkai (Kevin,C)
Cc: qemu-devel@nongnu.org; aligu...@amazon.com; Lee yang
Subject: Re: [PATCH]
Get trap instruction opcode from KVM and this opcode will
be used for setting software breakpoint in following patch
Signed-off-by: Bharat Bhushan bharat.bhus...@freescale.com
---
v7-v8
- No change
target-ppc/kvm.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-ppc/kvm.c
This patch synchronizes env-excp_vectors[] with env-iovr[].
This is required for using the existing interrupt injection mechanism
for kvm.
Signed-off-by: Bharat Bhushan bharat.bhus...@freescale.com
---
v7-v8
- No change
target-ppc/kvm.c | 27 +++
1 file changed, 27
This patch allow insert/remove software breakpoint.
When QEMU is not able to handle debug exception then we inject
program exception to guest because for software breakpoint QEMU
uses a ehpriv-1 instruction;
So there cannot be any reason that we are in qemu with exit reason
KVM_EXIT_DEBUG for
This patchset add support for
- software breakpoint
- h/w breakpoint
- h/w watchpoint
Please find description in individual patch.
v7-v8
- Decrement nip by 4 before calling ppc_cpu_do_interrupt()
as pointed by Madhavan Srinivasan
- Also added missing cpu_sync()
v6-v7
- Removed
This patch adds hardware breakpoint and hardware watchpoint support
for ppc.
On BOOKE architecture we cannot share debug resources between QEMU
and guest because:
When QEMU is using debug resources then debug exception must
be always enabled. To achieve this we set MSR_DE and also set
Hi,
Do you see a way to work around this in the graphics driver. E.g.
blacklisting 24bpp modes
etc. Even if X.Org people actually merge the fixes there are 2 years of Linux
releases out
there that have corrupted graphics.
For anything using kernel 3.14+ IMO the answer to pretty much
add defines and data structure for MIPS SIMD Architecture
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/cpu.h | 79 +--
target-mips/mips-defs.h |1 +
target-mips/op_helper.c |1 +
3 files changed, 78 insertions(+), 3
move commonly used functions to cpu.h
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/cpu.h | 72 +++
target-mips/gdbstub.c |7
target-mips/op_helper.c | 60 +-
3 files changed,
The following patchset implements MIPS SIMD Architecture module.
MSA adds new instructions to MIPS Architecture that allow efficient
parallel processing of vector operations.
For more information refer to:
MIPS Architecture Reference Manual
Volume IV-j: The MIPS32 SIMD Architecture Module
The
disassemble MIPS SIMD Architecture instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
disas/mips.c | 721 +-
1 files changed, 719 insertions(+), 2 deletions(-)
diff --git a/disas/mips.c b/disas/mips.c
index
stop translation as ctc1 instruction can change hflags
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/translate.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index 994e85d..cccbc44 100644
---
add 8, 16, 32, 64 bits load and store
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/cpu.h |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/target-mips/cpu.h b/target-mips/cpu.h
index 68ce383..51d1c88 100644
--- a/target-mips/cpu.h
+++
add MSA I8 format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h | 11
target-mips/msa_helper.c | 140 ++
target-mips/translate.c | 94 ++-
3 files changed, 243
add MSA exceptions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/target-mips/helper.c b/target-mips/helper.c
index 8a997e4..ed796ff 100644
--- a/target-mips/helper.c
+++
add msa_helper.c
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/Makefile.objs |2 +-
target-mips/msa_helper.c | 196 +
2 files changed, 197 insertions(+), 1 deletions(-)
create mode 100644 target-mips/msa_helper.c
diff --git
add MSA I5 format instructions:
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h | 12 ++
target-mips/msa_helper.c | 273 ++
target-mips/translate.c | 91 +++
3 files changed, 376 insertions(+), 0
add MSA support to mips32r5-generic core definition
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/translate_init.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-mips/translate_init.c b/target-mips/translate_init.c
index 9e0f67b..034a3f8
add msa_reset() and global msa register (d type only)
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/translate.c | 74 ++
target-mips/translate_init.c | 45 +
2 files changed, 119 insertions(+), 0
add MSA BIT format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h | 12 ++
target-mips/msa_helper.c | 292 ++
target-mips/translate.c | 100
3 files changed, 404 insertions(+), 0
add MSA branch instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/translate.c | 107 ++-
1 files changed, 105 insertions(+), 2 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index
add MSA ELM format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h |9 ++
target-mips/msa_helper.c | 239 ++
target-mips/translate.c | 136 ++
3 files changed, 384
add MSA opcode enum
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/translate.c | 248 +++
1 files changed, 248 insertions(+), 0 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index cccbc44..6b4a82c
add MSA VEC/2R format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h | 11 ++
target-mips/msa_helper.c | 244 ++
target-mips/translate.c | 98 ++
3 files changed, 353 insertions(+), 0
add MSA MI10 format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h |2 +
target-mips/msa_helper.c | 75 ++
target-mips/translate.c | 43 ++
3 files changed, 120
add MSA 2RF format instructions
Signed-off-by: Yongbok Kim yongbok@imgtec.com
---
target-mips/helper.h | 16 ++
target-mips/msa_helper.c | 656 ++
target-mips/translate.c | 76 ++
3 files changed, 748 insertions(+), 0 deletions(-)
I have the similar issue, the KVM 2.0 keeps crashing, here is the stack
I captured with GDB
(gdb) c
Continuing.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffede1f9700 (LWP )]
0x7ffeee4d4f79 in __GI_raise (sig=sig@entry=6) at
On 14.07.14 08:41, Paolo Bonzini wrote:
Il 13/07/2014 18:17, Alexander Graf ha scritto:
The NVRAM in our Core99 machine really supports 2byte and 4byte accesses
just as well as 1byte accesses. In fact, Mac OS X uses those.
Add support for higher register size granularities.
Signed-off-by:
The NVRAM in our Core99 machine really supports 2byte and 4byte accesses
just as well as 1byte accesses. In fact, Mac OS X uses those.
Add support for higher register size granularities.
Signed-off-by: Alexander Graf ag...@suse.de
---
v1 - v2:
- Leave single-byte accesses, but mark the MMIO
Right now starting a machine with virtio-scsi and a = 2.0 machine type
fails with:
qemu-system-x86_64: -device virtio-scsi-pci: Property .any_layout not found
This is because the any_layout bit was actually never set after
virtio-scsi was changed to support arbitrary layout for virtio
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@redhat.com]
Sent: Monday, July 14, 2014 4:43 PM
To: Wangkai (Kevin,C)
Cc: qemu-devel@nongnu.org; aligu...@amazon.com; Lee yang
Subject: Re: [PATCH] Tap: fix vcpu long time io blocking on tap
On Mon, Jul 14, 2014 at
Il 14/07/2014 10:36, Paolo Bonzini ha scritto:
to
/* In case elem-common.cb() makes a nested aio_poll() call,
* next may become invalid as well. Instead of just
* restarting the QLIST_FOREACH_SAFE, go through the BH
* once more, which also
repository at:
git://github.com/cohuck/qemu.git tags/s390x-20140714
for you to fetch changes up to 85ad6230b3af048109b3e949ca95ade4dd9a0bfa:
s390x/kvm: synchronize guest floating point registers (2014-07-14 09:15:38
+0200
Watch this:
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
(qemu) device_del gg
(qemu) upstream-qemu: /work/armbru/qemu/memory.c:1259:
memory_region_finalize:
On Mon, Jul 14, 2014 at 12:20 AM, Alexander Graf a...@antistatix.de wrote:
Hi,
I developed a software in the loop simulator for the Lego Mindstorms NXT
brick. It uses the Qemu ARM emulator to run the Robot's Firmware. I plan to
release the simulator as an open source project. Now, I wonder if
* Paolo Bonzini (pbonz...@redhat.com) wrote:
Right now starting a machine with virtio-scsi and a = 2.0 machine type
fails with:
qemu-system-x86_64: -device virtio-scsi-pci: Property .any_layout not
found
This is because the any_layout bit was actually never set after
virtio-scsi was
v2:
- Fixed assertion failure on 32 bit hosts triggered by qtests
(32 bit truncation of image file size in patch block: Make qiov
match the request size until EOF)
The following changes since commit 675879f6f3c9463e103735a4e41e9deb0bee9b39:
Update version for v2.1.0-rc1 release
From: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c| 2 +-
blockjob.c | 2 +-
qemu-io-cmds.c | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block.c b/block.c
index
From: Paolo Bonzini pbonz...@redhat.com
The main AioContext should be accessed explicitly via qemu_get_aio_context().
Most of the time, using it is not the right thing to do.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
aio-posix.c
From: Stefan Hajnoczi stefa...@redhat.com
VirtQueueElement is allocated in vring_pop() so it seems to make sense
that vring_push() should free it. Alas, virtio-blk frees
VirtQueueElement itself in virtio_blk_free_request().
This patch solves a double-free assertion in glib's g_slice_free().
When doing a block backup of an image with an unaligned size (with
respect to the BACKUP_CLUSTER_SIZE), qemu would check the allocation
status of sectors after the end of the image. bdrv_is_allocated()
returns a result that is valid for 0 sectors in this case, so the backup
job ran into an endless
From: Nikolay Nikolaev n.nikol...@virtualopensystems.com
Mising G_TIME_SPAN_SECOND definition breaks the RHEL6 compilation as GLib
version before 2.26 does not have it. In such case just define it.
Reported-by: Kevin Wolf kw...@redhat.com
Signed-off-by: Nikolay Nikolaev
bdrv_is_allocated() should return either 0 or 1 in successful cases.
We're lucky that currently, the callers that rely on this (e.g. because
they check for ret == 1) don't seem to break badly. They just might skip
some optimisation or in the case of qemu-io 'map' print separate lines
where a
If a QED image has a shorter backing file and a read request to
unallocated clusters goes across EOF of the backing file, the backing
file sees a shortened request and the rest is filled with zeros.
However, the original too long qiov was used with the shortened request.
This patch makes the qiov
At least raw-posix relies on this because it can allocate bounce buffers
based on the request length, but access it using all of the qiov entries
later.
Signed-off-by: Kevin Wolf kw...@redhat.com
Reviewed-by: Max Reitz mre...@redhat.com
---
block.c | 2 ++
block/raw-posix.c | 15
From: Paolo Bonzini pbonz...@redhat.com
The current test depends too much on the implementation of the AioContext
GSource. Just iterate on the main loop until the callback has been invoked
the right number of times.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Kevin Wolf
From: Paolo Bonzini pbonz...@redhat.com
Currently, whenever aio_poll(ctx, true) has completed all pending
work it returns true *and* the next call to aio_poll(ctx, true)
will not block.
This invariant has its roots in qemu_aio_flush()'s implementation
as while (qemu_aio_wait()) {}. However,
From: Paolo Bonzini pbonz...@redhat.com
In many cases, the call to event_notifier_set in aio_notify is unnecessary.
In particular, if we are executing aio_dispatch, or if aio_poll is not
blocking, we know that we will soon get to the next loop iteration (if
necessary); the thread that hosts the
If a read request goes across EOF, the block driver sees a shortened
request that stops at EOF (the rest is memsetted in block.c), however
the original qiov was used for this request.
This patch makes the qiov size match the request size, avoiding a
potential buffer overflow in raw-posix.
From: Stefan Hajnoczi stefa...@redhat.com
VirtIOBlockReq is freed later by virtio_blk_free_request() in
hw/block/virtio-blk.c. Remove this extraneous g_slice_free().
This patch fixes the following segfault:
0x556373af in virtio_blk_rw_complete (opaque=0x565ff5e0, ret=0)
at
If a qcow2 image has a shorter backing file and a read request to
unallocated clusters goes across EOF of the backing file, the backing
file sees a shortened request and the rest is filled with zeros.
However, the original too long qiov was used with the shortened request.
This patch makes the
From: Markus Armbruster arm...@redhat.com
The block layer fails such reads and writes just fine. However, they
then get treated like valid operations that fail: the error action
gets executed. Unwanted; reporting the error to the guest is the only
sensible action.
Reject them before passing
From: Stefan Hajnoczi stefa...@redhat.com
In commit de6c8042ec55da18702fa51f09072fcaa315edc3 (virtio-blk: Avoid
zeroing every request structure) we avoided the 40 KB memset when
allocating VirtIOBlockReq.
The memset was reintroduced in commit
671ec3f056559f22a2531a91dce3a258b9b5eb8a (virtio-blk:
From: Markus Armbruster arm...@redhat.com
The block layer fails such reads and writes just fine. However, they
then get treated like valid operations that fail: the error action
gets executed. Unwanted; reporting the error to the guest is the only
sensible action.
Reject them before passing
From: Andreas Färber afaer...@suse.de
The buffer was being allocated of size string length plus two.
Around the string two quotes were being added, but no terminating NUL.
It was then compared using g_assert_cmpstr(), resulting in fairly random
assertion failures:
From: Stefan Hajnoczi stefa...@redhat.com
The memory allocation between hw/block/virtio-blk.c,
hw/block/dataplane/virtio-blk.c, and hw/virtio/dataplane/vring.c is
messy. Structs are allocated in different files than they are freed in.
This is risky and makes memory leaks easier.
Embed
Il 13/07/2014 16:20, Alexander Graf ha scritto:
The problem is that the qemu board I designed is not self-contained. It
allows the firmware to read/write IO memory in order to read back sensor
values from the simulated environment and to control actuators. The
environment simulator is an
If the size of the scatter/gather list isn't a multiple of 512, the
number of sectors for the block layer request is rounded down, resulting
in a qiov that doesn't match the request length. Truncate the qiov to the
new length of the request.
This fixes the IDE qtest case
On Mon, Jul 14, 2014 at 9:10 PM, Markus Armbruster arm...@redhat.com wrote:
Watch this:
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
(qemu) device_del gg
From: Markus Armbruster arm...@redhat.com
Signed-off-by: Markus Armbruster arm...@redhat.com
Reviewed-by: Fam Zheng f...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/block/virtio-blk.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git
From: Markus Armbruster arm...@redhat.com
When a device model's I/O operation fails, we execute the error
action. This lets layers above QEMU implement thin provisioning, or
attempt to correct errors before they reach the guest. But when the
I/O operation fails because it's invalid, reporting
Il 14/07/2014 13:10, Markus Armbruster ha scritto:
Watch this:
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
(qemu) device_del gg
(qemu) upstream-qemu:
On Monday 14 July 2014 02:45 PM, Bharat Bhushan wrote:
This patch allow insert/remove software breakpoint.
When QEMU is not able to handle debug exception then we inject
program exception to guest because for software breakpoint QEMU
uses a ehpriv-1 instruction;
So there cannot be any
On Monday 14 July 2014 02:45 PM, Bharat Bhushan wrote:
Get trap instruction opcode from KVM and this opcode will
be used for setting software breakpoint in following patch
Signed-off-by: Bharat Bhushan bharat.bhus...@freescale.com
---
v7-v8
- No change
Reviewed By: Madhavan Srinivasan
The permission of TCE entry should exclude physical base address.
Otherwise, unmapping TCE entry can be interpreted to mapping TCE
entry wrongly for VFIO devices.
Signed-off-by: Gavin Shan gws...@linux.vnet.ibm.com
---
hw/misc/vfio.c | 2 +-
hw/ppc/spapr_iommu.c | 4 ++--
2 files changed,
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
On Mon, Jul 14, 2014 at 9:10 PM, Markus Armbruster arm...@redhat.com wrote:
Watch this:
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add
Paolo Bonzini pbonz...@redhat.com writes:
Il 14/07/2014 13:10, Markus Armbruster ha scritto:
Watch this:
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
(qemu)
On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster arm...@redhat.com wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Otherwise, hot-unplug of pci-serial-2x trips the assertion
in memory_region_destroy:
(qemu) device_del gg
(qemu) qemu-system-x86_64:
On 14.07.2014 11:53, Gerd Hoffmann wrote:
Hi,
Do you see a way to work around this in the graphics driver. E.g. blacklisting
24bpp modes
etc. Even if X.Org people actually merge the fixes there are 2 years of Linux
releases out
there that have corrupted graphics.
For anything using
On 07/14/2014 06:14 PM, Paolo Bonzini wrote:
Il 13/07/2014 16:41, Alexey Kardashevskiy ha scritto:
Current object_child_foreach() uses QTAILQ_FOREACH() to walk
through children and that makes children removal from the callback
impossible.
This makes object_child_foreach() use
On 07/11/2014 01:03 AM, Alexey Kardashevskiy wrote:
This does small RMA allocation rework and enables huge pages.
Please comment, especially commit logs. Thanks!
Changes:
v3:
* split to 2 patches, one mechanical
* tested on PPC970
v2:
* moved RMA memory region out of KVM code
This
Quoting Ondergetekende (1307...@bugs.launchpad.net):
We've resolved our issues by disabling KSM on the affected nodes. All of
the non-affected nodes didn't have KSM enabled (due to a packaging bug
elsewhere). After disabling KSM, our problems went away gradually in ~3
days.
This means we're
Il 14/07/2014 15:13, Alexey Kardashevskiy ha scritto:
On 07/11/2014 01:03 AM, Alexey Kardashevskiy wrote:
This does small RMA allocation rework and enables huge pages.
Please comment, especially commit logs. Thanks!
Changes:
v3:
* split to 2 patches, one mechanical
* tested on PPC970
v2:
*
Hi Peter,
On 10/07/14 13:17, Peter Maydell wrote:
On 17 June 2014 23:10, James Hogan james.ho...@imgtec.com wrote:
The patchset depends on v4 of target-mips: implement UserLocal
Register. I'm aiming for QEMU 2.1, hopefully it isn't too late to get
some final review.
Thanks to everybody who
On Fri, 07/11 12:11, Paolo Bonzini wrote:
qemu_chr_be_generic_open cannot be called with the write lock taken,
because it calls client code that may call qemu_chr_fe_write. This
actually happens for the monitor:
0x727dbf79 in __GI_raise (sig=sig@entry=6)
0x727df388
Richard Henderson writes:
On 07/11/2014 09:43 AM, Alex Bennée wrote:
+/* if I could put this in a header easily */
+void tb_enable_perfmap(void);
How about next to tb_flush in exec/exec-all.h?
Including exec/exec-all.h trips up some sort of include prevention
magic:
CCvl.o
In
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I stumbled
over a few issues that prevented it from doing so.
With these patches applied I still can't properly boot Mac OS X with -M mac99,
but I get a lot further than before. The
On 14.07.14 15:58, Mark Cave-Ayland wrote:
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I
stumbled
over a few issues that prevented it from doing so.
With these patches applied I still can't properly boot Mac OS X with
-M mac99,
On 13/07/14 21:36, Alexander Graf wrote:
Mac OS X calibrates a number of frequencies on bootup based on reading
tb values on bootup and comparing them to via cuda timer values.
The only variable we can really steer well (thanks to KVM) is the cuda
frequency. So let's use that one to fake Mac
On 14/07/14 15:00, Alexander Graf wrote:
On 14.07.14 15:58, Mark Cave-Ayland wrote:
On 13/07/14 17:17, Alexander Graf wrote:
While trying to get Mac OS X booting with our -M mac99 emulation I
stumbled
over a few issues that prevented it from doing so.
With these patches applied I still
Il 14/07/2014 14:36, Peter Crosthwaite ha scritto:
On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster arm...@redhat.com wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Otherwise, hot-unplug of pci-serial-2x trips the assertion
in memory_region_destroy:
(qemu) device_del gg
(qemu)
On Tue, Jul 15, 2014 at 12:20 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 14/07/2014 14:36, Peter Crosthwaite ha scritto:
On Thu, Jun 26, 2014 at 5:32 PM, Markus Armbruster arm...@redhat.com
wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Otherwise, hot-unplug of pci-serial-2x trips
I executed test-i386 from tests folder from QEMU rep and according to the
result, instructions fistl and fistpll returns maximum positive result
(0x7fff...), if a FPU register stores a positive infinity, and minimum negative
result (0x80...), if a negative infinity stores in a register. Real
On 14 July 2014 14:33, James Hogan james.ho...@imgtec.com wrote:
On 10/07/14 13:17, Peter Maydell wrote:
More generally, there doesn't really seem to be provision in the
KVM KVM_EXIT_MMIO API for returning this access failed.
I guess in theory userspace could do all the figure out how
to
The popular binfmt-wrapper patch adds an additional
executable which mangle argv suitable for binfmt flag P.
In a chroot you need the both (statically linked) qemu-$arch
and qemu-$arch-binfmt-wrapper. This is sub optimal and a
better approach is to recognize the -binfmt-wrapper extension
within
On 14 July 2014 12:42, Kevin Wolf kw...@redhat.com wrote:
v2:
- Fixed assertion failure on 32 bit hosts triggered by qtests
(32 bit truncation of image file size in patch block: Make qiov
match the request size until EOF)
The following changes since commit
On 14 July 2014 15:35, Dmitry Poletaev poletaev-q...@yandex.ru wrote:
I executed test-i386 from tests folder from QEMU rep and according to the
result, instructions fistl and fistpll returns maximum positive result
(0x7fff...), if a FPU register stores a positive infinity, and minimum
1 - 100 of 184 matches
Mail list logo
