If I do this:
qemu-system-sparc -nographic -no-reboot -kernel image -hda hda.sqf
-append 'root=/dev/sda rw init=/sbin/init.sh panic=1
PATH=/usr/distcc:/bin:/sbin console=ttyS0 HOST=sparc CPUS=1
DISTCC_HOSTS=10.0.2.2:31322/1 FTP_SERVER=10.0.2.2 FTP_PORT=31307
NATIVE_BUILD=lfs-bootstrap '
On 03/22/2013 07:08 PM, Eric Blake wrote:
On 03/22/2013 01:30 AM, Orit Wasserman wrote:
+static int socket_writev_buffer(void *opaque, struct iovec *iov, int
iovcnt)
Returning int...
+{
+QEMUFileSocket *s = opaque;
+ssize_t len;
+ssize_t size = iov_size(iov, iovcnt);
+
Am 22.03.2013 um 22:24 schrieb Paolo Bonzini pbonz...@redhat.com:
Il 22/03/2013 20:20, Peter Lieven ha scritto:
I think patch 4 is a bit overengineered. I would prefer the simple
patch you had using three/four non-vectorized accesses. The setup cost
of the vectorized buffer_is_zero is
On 22 March 2013 20:22, Eric Blake ebl...@redhat.com wrote:
Note that qemu.git already has a .exrc file that enables default vi
settings for vim users; I'm not sure if there is a counterpart
.dir-locals.el file to set up emacs settings
My .emacs has the following config:
On 22 March 2013 22:05, Scott Wood scottw...@freescale.com wrote:
On 03/22/2013 08:08:57 AM, Peter Maydell wrote:
The memory API flattens the tree of memory regions down into a flat
view of the address space. These callbacks get called for the
final flattened view (so you'll never see a pure
Hi Eric,
thanks for the reply. This indeed solved my issue. Suspending is much
faster without the artificial throttle.
On a related note: I'm curious about the baseline resume latency. It takes
about 5 seconds to resume an instance with a tiny amount of state (500 MB
dump size). The data is all
On Thu, Mar 14, 2013 at 5:49 PM, Markus Armbruster arm...@redhat.com wrote:
This should unbreak make check on machines where char is unsigned.
Blue, please give it a whirl.
Patches no longer apply, please rebase.
The JSON parser is still as broken as ever. Left for another day.
Markus
Can you add a flag or something to indicate that the iov pointer
belongs to RAM and not to device state?
That way, I could re-use this code for RDMA - if I see this flag, I will
know to send to RDMA.
- Michael
On 03/21/2013 05:09 AM, Orit Wasserman wrote:
This allow us to add a buffer
On 22 March 2013 17:41, Kevin Wolf kw...@redhat.com wrote:
The new parameter is unused yet.
Signed-off-by: Kevin Wolf kw...@redhat.com
Reviewed-by: Eric Blake ebl...@redhat.com
--- a/include/block/block_int.h
+++ b/include/block/block_int.h
@@ -83,7 +83,8 @@ struct BlockDriver {
void
Thanks, pulled.
On Mon, Mar 18, 2013 at 7:15 PM, Michael Walle mich...@walle.cc wrote:
Hi Anthony, Hi Blue,
these are various bugfixes for the lm32 target. Please pull.
The following changes since commit e531761d63b7f8fe6b6423fafb3616ebbff768aa:
Merge remote-tracking branch
On Mon, Mar 18, 2013 at 7:49 PM, Anthony Green gr...@moxielogic.com wrote:
This version of the patch addresses recent changes in the upstream
qemu sources (where interrupt_request resides).
Please consider applying this version of the patch.
Thanks, applied all.
Thank you!
AG
Anthony
Thanks, applied.
On Tue, Mar 19, 2013 at 7:11 PM, Richard Henderson r...@twiddle.net wrote:
We can compute the value in cpu_dump_state anyway, and gratuitous
modifications to eflags creates heisenbugs.
Cc: Blue Swirl blauwir...@gmail.com
Signed-off-by: Richard Henderson r...@twiddle.net
---
Thanks, applied.
On Tue, Mar 19, 2013 at 4:40 PM, Richard Henderson r...@twiddle.net wrote:
When starting from CC_OP_DYNAMIC, and issuing adox before adcx,
a typo used the wrong value for the resulting CC_OP.
Cc: Blue Swirl blauwir...@gmail.com
Reported-by: Torbjorn Granlund t...@gmplib.org
Thanks, applied.
On Thu, Mar 21, 2013 at 4:13 PM, Richard Henderson r...@twiddle.net wrote:
Cc: Blue Swirl blauwir...@gmail.com
Signed-off-by: Richard Henderson r...@twiddle.net
---
V2 properly does a reset_temp on the output of the neg.
This was the cause of the sparc32 boot problem.
r~
On Sat, Mar 23, 2013 at 06:22:39PM +, Blue Swirl wrote:
On Mon, Mar 18, 2013 at 7:49 PM, Anthony Green gr...@moxielogic.com wrote:
This version of the patch addresses recent changes in the upstream
qemu sources (where interrupt_request resides).
Please consider applying this version
When CONFIG_FDT is enabled, qemu-system-moxie fails to build with
the following error:
$ make
make[1]: *** No rule to make target `hw/moxie/../device_tree.o', needed by
`qemu-system-moxie'. Stop.
make: *** [subdir-moxie-softmmu] Error 2
Since commit 320ba5f, device_tree.o is always
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
tcg/mips/tcg-target.c |6 ++
tcg/mips/tcg-target.h |2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/tcg/mips/tcg-target.c b/tcg/mips/tcg-target.c
index bd8c858..373c364 100644
--- a/tcg/mips/tcg-target.c
+++
Here's a fix for the build problem identified by Aurelien Jano here:
http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg04177.html
I hadn't tested with FDT enabled recently.
Thanks!
AG
Signed-off-by: Anthony Green gr...@moxielogic.com
---
hw/moxie/Makefile.objs | 1 -
1 file changed, 1
Low priority ping on this patchset...?
-hpa
19 matches
Mail list logo
