On Thu, Aug 4, 2011 at 4:20 PM, Lucas Meneghel Rodrigues l...@redhat.com
wrote:
On 08/04/2011 12:17 PM, Stefan Hajnoczi wrote:
On Sat, Jul 30, 2011 at 1:39 AM, Anthony Liguorianth...@codemonkey.ws
wrote:
On behalf of the entire QEMU team, I'm please to announce the release of
QEMU
Hi,
Now I understand why read-only IDE support was dropped. I will investigate
if I could use read-only virtio disks for my purpose.
Thank you for your response and for the hints,
Best regards,
Frederic
Le 4 août 2011 20:20, Markus Armbruster arm...@redhat.com a écrit :
Frédéric Dreier
On 2011-08-05 06:02, David Gibson wrote:
At present, an explicit test disallows use of -mem-path when kvm is enabled
but KVM_CAP_SYNC_MMU is not set. In particular, this prevents the user
from using hugetlbfs to back the guest memory.
I can see no reason for this check, and when I asked
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function 'coroutine_new':
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:160:16: error: 'arg.i[1]' may
be used uninitialized in this function
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:136:18: note: 'arg.i[1]' was
declared here
Public bug reported:
qemu-0.14.1
./configure --target-list=i386-softmmu,x86_64-softmmu,arm-softmmu
qemu(-system-(x86_64|arm))
Segmentation fault: 11
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
2011/8/4 Kevin Wolf kw...@redhat.com:
When loading an internal snapshot whose L1 table is smaller than the current
L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size in
memory, but not on disk. This lead to incorrect refcount updates and
eventuelly
to image
On Thu, 4 Aug 2011 22:57:34 +0100, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Aug 4, 2011 at 7:45 PM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Thu, 4 Aug 2011 15:31:08 +0100, Stefan Hajnoczi stefa...@gmail.com
wrote:
On Thu, Aug 4, 2011 at 1:03 PM, Aneesh Kumar
Enhance info block to display hostcache setting for each
block device.
Example:
(qemu) info block
ide0-hd0: type=hd removable=0 file=../rhel6-32.qcow2 ro=0 drv=qcow2
encrypted=0
Enhanced to display hostcache setting:
(qemu) info block
ide0-hd0: type=hd removable=0 hostcache=1
New error classes defined for file reopen failure and data
sync error
Signed-off-by: Supriya Kannery supri...@linux.vnet.ibm.com
---
qerror.c |8
qerror.h |6 ++
2 files changed, 14 insertions(+)
Index: qemu/qerror.c
New command block_set_hostcache added for dynamically changing
host pagecache setting of a block device.
Signed-off-by: Supriya Kannery supri...@linux.vnet.ibm.com
---
block.c | 54 ++
block.h |2 ++
blockdev.c |
qemu command option 'hostcache' added to -drive for block devices.
While starting a VM from qemu commandline, this option can be used
for setting host cache usage for block data access. It is not
allowed to specify both 'hostcache' and 'cache' options in the same
commandline.
Signed-off-by:
Currently cache setting of a block device cannot be changed
without restarting a running VM. Following patchset is for
enabling dynamic change of cache setting for block devices
through qemu monitor. Code changes are based on patches
from Christoph Hellwig and Prerna Saxena.
This patchset
05.08.2011 02:19, Jan Kiszka wrote:
[]
Resume on error in migrate_fd_put_buffer raced with migrate_fd_cleanup
triggered via migrate_fd_put_ready called from migrate_fd_connect.
This migration code is a horrible maze. Patch below tries to move
monitor_resume a bit out of this. Please check if
From: Jan Kiszka jan.kis...@siemens.com
If migration failed in migrate_fd_put_buffer, the monitor may have been
resumed not only in the error path of that function but also once again
in migrate_fd_put_ready which is called unconditionally by
migrate_fd_connect.
Fix this by establishing a
On 2011-08-05 08:51, Michael Tokarev wrote:
05.08.2011 02:19, Jan Kiszka wrote:
[]
Resume on error in migrate_fd_put_buffer raced with migrate_fd_cleanup
triggered via migrate_fd_put_ready called from migrate_fd_connect.
This migration code is a horrible maze. Patch below tries to move
Luiz Capitulino lcapitul...@redhat.com writes:
On Wed, 3 Aug 2011 15:07:59 +0200
Markus Armbruster arm...@redhat.com wrote:
Signed-off-by: Markus Armbruster arm...@redhat.com
---
hw/ide/internal.h |1 +
hw/ide/qdev.c | 12
2 files changed, 13 insertions(+), 0
Am 05.08.2011 08:22, schrieb malc:
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function
'coroutine_new':
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:160:16: error: 'arg.i[1]'
may be used uninitialized in this function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
05.08.2011 11:11, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
If migration failed in migrate_fd_put_buffer, the monitor may have been
resumed not only in the error path of that function but also once again
in migrate_fd_put_ready
Hi all,
I have installed qemu on mac with these options:
tar -xf qemu-0.14.1.tar
cd qemu-0.14.1
/configure --target-list=i386-softmmu,x86_64-softmmu,arm-softmmu
make
make install
When I try to run any of them (i386, x86_64 or arm) I get:
Segmentation fault: 11
Any help ?
Also when I do not
This function seems to be not that safe.
The first problem is that the first thing it does if free refcount
calling qcow2_update_snapshot_refcount(bs, s-l1_table_offset,
s-l1_size, -1). Now if something goes wrong (crash, disk errors) this
could lead to refcount == 0 (depending on L1 size, cache,
Am 05.08.2011 09:34, schrieb Frediano Ziglio:
This function seems to be not that safe.
The first problem is that the first thing it does if free refcount
calling qcow2_update_snapshot_refcount(bs, s-l1_table_offset,
s-l1_size, -1). Now if something goes wrong (crash, disk errors) this
could
Am 05.08.2011 08:35, schrieb Frediano Ziglio:
2011/8/4 Kevin Wolf kw...@redhat.com:
When loading an internal snapshot whose L1 table is smaller than the current
L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size
in
memory, but not on disk. This lead to incorrect
2011/8/5 Kevin Wolf kw...@redhat.com:
Am 05.08.2011 08:35, schrieb Frediano Ziglio:
2011/8/4 Kevin Wolf kw...@redhat.com:
When loading an internal snapshot whose L1 table is smaller than the
current L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size
in
memory,
Am 04.08.2011 13:26, schrieb Stefan Hajnoczi:
This patch introduces bdrv_parse_cache_flags() which sets open flags
given a cache mode. Previously this was duplicated in blockdev.c and
qemu-img.c.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
Thanks, applied both to the block
We've discussed safe methods for reopening image files (e.g. useful for
changing the hostcache parameter). The problem is that closing the file first
and then opening it again exposes us to the error case where the open fails.
At that point we cannot get to the file anymore and our options are to
On Fri, Aug 5, 2011 at 8:29 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 08:22, schrieb malc:
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function
'coroutine_new':
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:160:16: error: 'arg.i[1]'
may be used uninitialized in
On Thu, Aug 04, 2011 at 08:15:35PM +0200, Gerd Hoffmann wrote:
Hi,
I recently had black screen problems with QXL in 0.14.x that turned out to
actually be a Seabios bug due to the default 64MB vram QXL has.
It is a seabios issue indeed.
I suspect
this would hit 0.15.x builds too. If
Hi folks,
I need to do some changes to qemu-kvm. However, on the kvm website, it is
suggested to develop against qemu.git. I am wondering if I develop against
qemu.git, because my fix may depend on some new patch that is only in
qemu.git, it seems very hard to generate a patch for the qemu-kvm.
On Fri, Aug 5, 2011 at 7:22 AM, malc av1...@comtv.ru wrote:
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function
'coroutine_new':
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:160:16: error: 'arg.i[1]'
may be used uninitialized in this function
On Fri, Aug 5, 2011 at 9:56 AM, cheetah xuw...@gmail.com wrote:
I need to do some changes to qemu-kvm. However, on the kvm website, it is
suggested to develop against qemu.git. I am wondering if I develop against
qemu.git, because my fix may depend on some new patch that is only in
qemu.git,
Hi,
Patches are all upstream, so just fetching the latest seabios bits
(git master branch) and building yourself will work too.
Great, is there an intention to rebase Seabios in QEMU to pull this in
before the release of 0.15 ?
Anthony doesn't want change the bios that shortly before
On Fri, Aug 05, 2011 at 11:02:00AM +0200, Gerd Hoffmann wrote:
Hi,
Patches are all upstream, so just fetching the latest seabios bits
(git master branch) and building yourself will work too.
Great, is there an intention to rebase Seabios in QEMU to pull this in
before the release of
On 08/05/2011 10:40 AM, Stefan Hajnoczi wrote:
4. Implement bdrv_reopen()
First call bdrv_extract_fds() to stash the file descriptors, then close the
block device. Try opening the new image but if that fails, reopen using the
stashed file descriptors.
Why not do the latter unconditionally?
Thanks for the quickly reply.
I am going to change/add the block driver and some image format code. If I
develop against the qemu.git, can I easily generate a patch to apply to
qemu-kvm.git too? Do you have some best practices to recommend? ;) Thanks!
Regards,
Peter
On Fri, Aug 5, 2011 at 2:00
Am 05.08.2011 10:40, schrieb Stefan Hajnoczi:
We've discussed safe methods for reopening image files (e.g. useful for
changing the hostcache parameter). The problem is that closing the file first
and then opening it again exposes us to the error case where the open fails.
At that point we
Am 05.08.2011 10:48, schrieb Stefan Hajnoczi:
On Fri, Aug 5, 2011 at 8:29 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 08:22, schrieb malc:
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function
'coroutine_new':
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c:160:16:
On 08/05/2011 11:04 AM, cheetah wrote:
Thanks for the quickly reply.
I am going to change/add the block driver and some image format code. If
I develop against the qemu.git, can I easily generate a patch to apply
to qemu-kvm.git too?
Yes, or vice versa too. You can develop against
Sounds great. Thanks.
I am a newbie and still confusing on how to do it. Please excuse my
ignorance.
If I forked a my own branch on qemu.git and develop against it.
For instance I change qcow2.c which depends on some functions in block.c
which are different from qemu-kvm.git because qemu-kvm.git
When slot status register is cleared, PCIDevice::exp.hpev_notify
needs to be cleared.
Otherwise, PCIDevice::exp.hpev_notify is never set to false resulting
in no more hot plug event once it's raised.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/pcie.c | 12
1 files
various fixes to make aer inject error command work.
- wrong assert
- command line parser
- err.status needs initialization
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/pcie_aer.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/hw/pcie_aer.c
On Fri, Aug 5, 2011 at 7:40 AM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Thu, 4 Aug 2011 22:57:34 +0100, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Aug 4, 2011 at 7:45 PM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Thu, 4 Aug 2011 15:31:08 +0100,
On Fri, Aug 5, 2011 at 10:04 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 08/05/2011 10:40 AM, Stefan Hajnoczi wrote:
4. Implement bdrv_reopen()
First call bdrv_extract_fds() to stash the file descriptors, then close
the
block device. Try opening the new image but if that fails, reopen
On 5 August 2011 01:05, An-Cheng Huang anch...@ubnt.com wrote:
Ok the following patch changes the number of arguments for sys_syscall
to 8 in mips_syscall_args and also skips the do_syscall() call if any
of the get_user() calls fails. Do you think combining these makes sense
or should they be
On Fri, Aug 5, 2011 at 10:07 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 10:40, schrieb Stefan Hajnoczi:
We've discussed safe methods for reopening image files (e.g. useful for
changing the hostcache parameter). The problem is that closing the file
first
and then opening it again
On Fri, Aug 5, 2011 at 10:19 AM, cheetah xuw...@gmail.com wrote:
Sounds great. Thanks.
I am a newbie and still confusing on how to do it. Please excuse my
ignorance.
If I forked a my own branch on qemu.git and develop against it.
For instance I change qcow2.c which depends on some functions
On Fri, Aug 5, 2011 at 10:09 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 10:48, schrieb Stefan Hajnoczi:
On Fri, Aug 5, 2011 at 8:29 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 08:22, schrieb malc:
/home/malc/x/rcs/git/qemuorg/coroutine-ucontext.c: In function
Thanks for the advice.
I will formalize my plan and send to the maillist.
Peter
On Fri, Aug 5, 2011 at 2:33 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Aug 5, 2011 at 10:19 AM, cheetah xuw...@gmail.com wrote:
Sounds great. Thanks.
I am a newbie and still confusing on how to do
2011/8/5 Frediano Ziglio fredd...@gmail.com:
2011/8/5 Kevin Wolf kw...@redhat.com:
Am 05.08.2011 08:35, schrieb Frediano Ziglio:
2011/8/4 Kevin Wolf kw...@redhat.com:
When loading an internal snapshot whose L1 table is smaller than the
current L1
table, the size of the current L1 would be
Dear,
Is anyone can help me? I'm deeply in trouble. I want boot by kernel by
qemu, i want boot from dhcp, but i got error,
i have no idea on this, two days... i cannot find the solution. Anyone knows
why? Thanks very much.
*command:*
/tftpboot/i686/usbqemu# qemu-system-i386 -M pc -kernel
Am 05.08.2011 11:29, schrieb Stefan Hajnoczi:
On Fri, Aug 5, 2011 at 10:07 AM, Kevin Wolf kw...@redhat.com wrote:
Am 05.08.2011 10:40, schrieb Stefan Hajnoczi:
We've discussed safe methods for reopening image files (e.g. useful for
changing the hostcache parameter). The problem is that
On 08/05/2011 11:27 AM, Stefan Hajnoczi wrote:
First call bdrv_extract_fds() to stash the file descriptors, then close
the block device. Try opening the new image but if that fails, reopen using
the stashed file descriptors.
Why not do the latter unconditionally?
Because you cannot change
CCslirp/arp_table.o
/home/kraxel/projects/qemu/slirp/arp_table.c: In function 'arp_table_add':
/home/kraxel/projects/qemu/slirp/arp_table.c:29: error: expected '=',
',', ';', 'asm' or '__attribute__' before 'broadcast_addr'
/home/kraxel/projects/qemu/slirp/arp_table.c:29: error:
When loading an internal snapshot whose L1 table is smaller than the current L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size in
memory, but not on disk. This lead to incorrect refcount updates and eventuelly
to image corruption.
Instead of writing the new L1 size to
On 31 July 2011 22:40, Johannes Schauer j.scha...@email.de wrote:
Rework option parsing code for linux-user in a table-driven manner to allow
environment variables for all commandline options.
Also generate usage() output from option table.
Thanks for this, it looks good. A couple of minor
Dear,
Is anyone can help me? I'm deeply in trouble. I want boot by kernel by
qemu, i want boot from dhcp, but i got error,
i have no idea on this, two days... i cannot find the solution. Anyone knows
why? Thanks very much.
[...]
bellow is kernel error message:
[ 13.087298] VFS:
Hello,
Greetings for the day!
I am Pooja and I am contacting you after looking at your website- .
We are a Leading Indian Based SEO Web Development Company and one of the
very few company which offer organic SEO services with a full range of
supporting services such as one way themed
Secondary CPU bootloader enables interrupt and issues wfi until start
address is written to system controller. The position where to find this
start address is hardcoded to 0x1030. This commit adds new
bootloader for secondary CPU which allows a target board to cpecify a
position where to
On 2011-08-05 11:57, Gerd Hoffmann wrote:
CCslirp/arp_table.o
/home/kraxel/projects/qemu/slirp/arp_table.c: In function 'arp_table_add':
/home/kraxel/projects/qemu/slirp/arp_table.c:29: error: expected '=',
',', ';', 'asm' or '__attribute__' before 'broadcast_addr'
From 851173b22dc2c5d5f8bb46eef07c452af78f61e8 Mon Sep 17 00:00:00 2001
From: Evgeny Voevodin e.voevo...@samsung.com
Date: Fri, 29 Jul 2011 09:36:21 +0400
Subject: [PATCH 1/2] arm: Add new secondary CPU bootloader
Secondary CPU bootloader enables interrupt and issues wfi until start address
is
From 851173b22dc2c5d5f8bb46eef07c452af78f61e8 Mon Sep 17 00:00:00 2001
From: Evgeny Voevodin e.voevo...@samsung.com
Date: Fri, 29 Jul 2011 09:36:21 +0400
Subject: [PATCH 1/2] arm: Add new secondary CPU bootloader
Secondary CPU bootloader enables interrupt and issues wfi until start address
is
From 851173b22dc2c5d5f8bb46eef07c452af78f61e8 Mon Sep 17 00:00:00 2001
From: Evgeny Voevodin e.voevo...@samsung.com
Date: Fri, 29 Jul 2011 09:36:21 +0400
Subject: [PATCH 1/2] arm: Add new secondary CPU bootloader
Secondary CPU bootloader enables interrupt and issues wfi until start address
is
Sorry for flooding. Looks like my e-mail preferences have been broken.
Am 04.08.2011 17:10, schrieb Gerd Hoffmann:
Fill the spefified area with zeros.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Looks like we're starting to duplicate everything in qemu_iovec_* and
iov_*...
Any reason not to use QEMUIOVector?
Kevin
Hello,
Does QEMU support the Freescale MPC8xx (MPC850) processors or platforms
(e.g FADS860) ??
Googling shows some code that suggests that it is not supported.
cpu_abort(env, /MPC8xx/ MMU model is not implemented\n);
If not supported, does anyone have any idea how much work there would
On Fri, 5 Aug 2011 10:24:42 +0100, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Aug 5, 2011 at 7:40 AM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Thu, 4 Aug 2011 22:57:34 +0100, Stefan Hajnoczi stefa...@gmail.com
wrote:
On Thu, Aug 4, 2011 at 7:45 PM, Aneesh Kumar
Am 04.08.2011 23:38, schrieb Anthony Liguori:
Hi,
It took a little longer than I had hoped to converge on a work around
for the migration issue. -rc2 is out but I don't think 24 hours is
enough time to get proper testing for the final release.
So I'm pushing 0.15.0 to Monday. Please
On 5 August 2011 11:37, Evgeny Voevodin e.voevo...@samsung.com wrote:
Secondary CPU bootloader enables interrupt and issues wfi until start
address is written to system controller. The position where to find this
start address is hardcoded to 0x1030. This commit adds new bootloader
for
Am 04.08.2011 19:22, schrieb Philipp Hahn:
By introducing BlockDriverState compiling qcow2 with DEBUG_ALLOC and DEBUG_EXT
defined got broken.
Define a BdrvCheckResult structure locally which is now needed as the second
argument.
Also fix qcow2_read_extensions() needing BDRVQcowState.
On 08/05/2011 03:35 PM, Peter Maydell wrote:
On 5 August 2011 11:37, Evgeny Voevodine.voevo...@samsung.com wrote:
Secondary CPU bootloader enables interrupt and issues wfi until start
address is written to system controller. The position where to find this
start address is hardcoded to
On 08/05/2011 06:38 AM, Kevin Wolf wrote:
Am 04.08.2011 23:38, schrieb Anthony Liguori:
Hi,
It took a little longer than I had hoped to converge on a work around
for the migration issue. -rc2 is out but I don't think 24 hours is
enough time to get proper testing for the final release.
So I'm
On 08/05/2011 05:06 AM, Kevin Wolf wrote:
When loading an internal snapshot whose L1 table is smaller than the current L1
table, the size of the current L1 would be shrunk to the snapshot's L1 size in
memory, but not on disk. This lead to incorrect refcount updates and eventuelly
to image
Am 03.08.2011 15:39, schrieb Frediano Ziglio:
2011/8/2 Kevin Wolf kw...@redhat.com:
Am 02.08.2011 17:29, schrieb Frediano Ziglio:
- L2 allocation can be done with relative data (this is not easy to do
with current code)
What do you mean by that?
Let's take an example. By allocation I mean
On Fri, Aug 5, 2011 at 12:32 PM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Fri, 5 Aug 2011 10:24:42 +0100, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Aug 5, 2011 at 7:40 AM, Aneesh Kumar K.V
aneesh.ku...@linux.vnet.ibm.com wrote:
On Thu, 4 Aug 2011 22:57:34 +0100,
On Fri, Aug 5, 2011 at 10:55 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 08/05/2011 11:27 AM, Stefan Hajnoczi wrote:
First call bdrv_extract_fds() to stash the file descriptors, then close
the block device. Try opening the new image but if that fails, reopen
using
the stashed file
On 5 August 2011 13:10, Evgeny Voevodin e.voevo...@samsung.com wrote:
On 08/05/2011 03:35 PM, Peter Maydell wrote:
What's the motivation for this? (ie what target board needs this?)
The motivation is that Samsung s5pc210 board which is under development
needs this. Also, I believe that more
On Fri, Aug 05, 2011 at 10:27:00AM +0100, Stefan Hajnoczi wrote:
On Fri, Aug 5, 2011 at 10:04 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 08/05/2011 10:40 AM, Stefan Hajnoczi wrote:
4. Implement bdrv_reopen()
First call bdrv_extract_fds() to stash the file descriptors, then close
Am 05.08.2011 15:16, schrieb Frediano Ziglio:
2011/8/5 Kevin Wolf kw...@redhat.com:
Am 03.08.2011 15:39, schrieb Frediano Ziglio:
2011/8/2 Kevin Wolf kw...@redhat.com:
Am 02.08.2011 17:29, schrieb Frediano Ziglio:
- L2 allocation can be done with relative data (this is not easy to do
with
The expiration timeout must only affect packets that are queued due to
pending ARP resolutions. The old version broke ping e.g.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
slirp/if.c|3 ---
slirp/slirp.c |3 +++
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
No need to update the current time for each packet we send from the
queue. Processing time is comparably short.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
slirp/if.c |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/slirp/if.c b/slirp/if.c
index
The following changes since commit 81e34a2401f7ffd519bb7f093e833cb48734169f:
Merge remote-tracking branch 'mst/for_anthony' into staging (2011-08-04
17:15:22 -0500)
are available in the git repository at:
git://git.kiszka.org/qemu.git queues/slirp
Fixes some fall-outs from the latest
Should be uint32_t for IPv4, not int. Also avoid in_addr_t without
proper includes. Fixes build regression on mingw32.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
slirp/arp_table.c | 16
slirp/slirp.h |4 ++--
2 files changed, 10 insertions(+), 10 deletions(-)
From 4c843ce18a7534e722670ecb892a2dedd3eae5b3 Mon Sep 17 00:00:00 2001
From: Evgeny Voevodin e.voevo...@samsung.com
Date: Fri, 5 Aug 2011 17:24:48 +0400
Subject: [PATCH 1/1] target-arm: Add new secondary CPU bootloader
Secondary CPU bootloader enables interrupt and issues wfi until start
On 08/04/2011 08:05 AM, Avi Kivity wrote:
From: Michael S. Tsirkinm...@redhat.com
We originally did get config on map, so that
following write accesses are done on an updated config.
New memory API doesn't give us a callback
on map, and arguably, devices don't know when
cpu really can access
On 08/04/2011 08:05 AM, Avi Kivity wrote:
This is a hack, for devices that have a back-channel to read this
address back outside the normal configuration mechanisms, such
as VMware svga.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Can we add a
On 08/04/2011 08:05 AM, Avi Kivity wrote:
We're going to remove the callback, so we can't use it to save the
address. Use the pci API instead.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Convert all vga memory to the memory API. Note we need to fall back to
get_system_memory(), since the various buses don't pass the vga window
as a memory region.
We no longer need to sync the dirty bitmap of the cirrus mapped memory
banks, since the
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
---
hw/cirrus_vga.c | 78
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
-static uint64_t cirrus_mmio_read(void *opaque,
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
We have to keep vga_mem_{read,write}b() since they're used by cirrus.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Make use of the memory API's ability to satisfy multi-byte accesses via
multiple single-byte accesses.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
On 08/04/2011 08:06 AM, Avi Kivity wrote:
get_system_io() returns the root I/O memory region.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
---
exec-memory.h |2 ++
exec.c| 10 ++
2 files changed, 12 insertions(+), 0
On 08/04/2011 08:06 AM, Avi Kivity wrote:
This lets us register BARs in the I/O address space.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
---
hw/pci.c | 43 +++
hw/pci.h
On 08/05/11 13:30, Kevin Wolf wrote:
Am 04.08.2011 17:10, schrieb Gerd Hoffmann:
Fill the spefified area with zeros.
Signed-off-by: Gerd Hoffmannkra...@redhat.com
Looks like we're starting to duplicate everything in qemu_iovec_* and
iov_*...
Any reason not to use QEMUIOVector?
I *do* use
On 08/04/2011 08:06 AM, Avi Kivity wrote:
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
---
hw/rtl8139.c | 72 ++---
1 files changed, 38 insertions(+), 34 deletions(-)
diff --git a/hw/rtl8139.c
On 08/04/2011 08:06 AM, Avi Kivity wrote:
fixes BAR sizing as well.
Reviewed-by: Richard Hendersonr...@twiddle.net
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Malc, please Ack
Regards,
Anthony Liguori
---
hw/ac97.c | 88
On Fri, Aug 05, 2011 at 10:27:00AM +0100, Stefan Hajnoczi wrote:
Why not do the latter unconditionally?
Because you cannot change O_DIRECT on an open fd :(. This is why
we're going through this pain.
You can. What you can't right now is O_SYNC, but we're going to change
that.
On Fri, Aug 05, 2011 at 02:12:48PM +0100, Daniel P. Berrange wrote:
Because you cannot change O_DIRECT on an open fd :(. This is why
we're going through this pain.
Hmm, I remember hearing that before, but looking at the current fcntl()
manpage, it claims you *can* change O_DIRECT using
1 - 100 of 165 matches
Mail list logo
