Hi, all
I am not a good painter or an artist, but here you go
http://people.cs.nctu.edu.tw/~chenwj/slide/QEMU/QEMU_Mascot.png
Let me know what you think. :)
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Am 11.11.2011 05:06, schrieb Zhi Yong Wu:
On Fri, Nov 11, 2011 at 1:32 AM, Kevin Wolf kw...@redhat.com wrote:
qcow2 has a writeback metadata cache, so flushing a qcow2 image actually
consists of writing back that cache to the protocol and only then flushes the
protocol in order to get
Am 11.11.2011 07:27, schrieb Mark Wu:
On 11/11/2011 08:11 AM, Anthony Liguori wrote:
I did a brain dump of my understanding of the various storage
requirements for live migration. I think it's accurate but I may have
misunderstand some details so I would appreciate review.
I think given
Am 11.11.2011 01:11, schrieb Anthony Liguori:
I did a brain dump of my understanding of the various storage requirements
for
live migration. I think it's accurate but I may have misunderstand some
details
so I would appreciate review.
I think given sections (1) and (2), the only
Ping?
Markus Armbruster arm...@redhat.com writes:
Compile-tested only, buyer beware.
Markus Armbruster (2):
net: socket backend passes junk size to getsockname(), fix
net: socket backend shows junk in info network, fix
net/socket.c | 14 ++
1 files changed, 10
Spotted by Coverity.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
ui/keymaps.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/ui/keymaps.c b/ui/keymaps.c
index f54a114..f55a2aa 100644
--- a/ui/keymaps.c
+++ b/ui/keymaps.c
@@ -92,15 +92,17 @@ static
As usual, shit happens on error paths.
Markus Armbruster (5):
qemu-char: Plug memory leak on qemu_chr_open_pty() error path
ui: Plug memory leaks on parse_keyboard_layout() error path
qemu-sockets: Plug fd leak on unix_connect_opts() error path
posix-aio-compat: Plug memory leak on
Spotted by Coverity.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qemu-char.c | 19 ++-
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/qemu-char.c b/qemu-char.c
index 9fd94d1..b562bf8 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -985,7 +985,7 @@
Spotted by Coverity.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qemu-sockets.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu-sockets.c b/qemu-sockets.c
index 183a9cb..61b2247 100644
--- a/qemu-sockets.c
+++ b/qemu-sockets.c
@@ -572,6 +572,7 @@ int
Spotted by Coverity.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
posix-aio-compat.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/posix-aio-compat.c b/posix-aio-compat.c
index d3c1174..0c0035c 100644
--- a/posix-aio-compat.c
+++ b/posix-aio-compat.c
@@
Spotted by Coverity.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
os-posix.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index dbf3b24..dc4a6bb 100644
--- a/os-posix.c
+++ b/os-posix.c
@@ -372,13 +372,16 @@ int
On Fri, Nov 11, 2011 at 10:38:20AM +0100, Kevin Wolf wrote:
Am 11.11.2011 01:11, schrieb Anthony Liguori:
I did a brain dump of my understanding of the various storage requirements
for
live migration. I think it's accurate but I may have misunderstand some
details
so I would
Am 11.11.2011 10:55, schrieb Daniel P. Berrange:
On Fri, Nov 11, 2011 at 10:38:20AM +0100, Kevin Wolf wrote:
Am 11.11.2011 01:11, schrieb Anthony Liguori:
I did a brain dump of my understanding of the various storage requirements
for
live migration. I think it's accurate but I may have
On 11/11/2011 12:17 PM, Supriya Kannery wrote:
Enhance info block to display hostcache setting for each
block device.
##
Index: qemu/qapi-types.h
===
--- qemu.orig/qapi-types.h
+++ qemu/qapi-types.h
@@ -383,6 +383,7 @@
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even with proper clustered storage. I think doing a block level
flush
cache interface and letting block devices decide how to do it is the best
approach.
On Thu, Nov 10, 2011 at 5:12 PM, srinivasan Sundararajan
sr...@cisco.com wrote:
Trying the following and can’t seem to make it work ? This is with qemu-kvm
15 . What am I doing wrong here ? I get this id1 not found error.
qemu-system-x86_64 \
-enable-kvm -cpu qemu64,+vmx -boot c -m 16000M
On 11/08/2011 11:12 AM, Thomas Huth wrote:
Am Tue, 8 Nov 2011 16:52:16 +1100
schrieb David Gibsonda...@gibson.dropbear.id.au:
The SLOF firmware used on the pseries machine needs a reasonable amount of
(guest) RAM in order to run, so we have a check in the machine init
function to check that
On Fri, Nov 11, 2011 at 8:57 AM, 陳韋任 che...@iis.sinica.edu.tw wrote:
I am not a good painter or an artist, but here you go
http://people.cs.nctu.edu.tw/~chenwj/slide/QEMU/QEMU_Mascot.png
Neat idea to combine the emu with the Q shape. It would be nice to
find a high resolution emu, this one
On 11 November 2011 11:20, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Nov 11, 2011 at 8:57 AM, 陳韋任 che...@iis.sinica.edu.tw wrote:
I am not a good painter or an artist, but here you go
http://people.cs.nctu.edu.tw/~chenwj/slide/QEMU/QEMU_Mascot.png
Neat idea to combine the emu with
Neat idea to combine the emu with the Q shape. It would be nice to
find a high resolution emu, this one is quite pixelated.
See my link from the other thread:
http://commons.wikimedia.org/wiki/File:Emu_(PSF).png
Actually, I borrow that picture and do some cut/paste. ;-)
I am a M$ user,
Am 11.11.2011 12:31, schrieb 陳韋任:
Neat idea to combine the emu with the Q shape. It would be nice to
find a high resolution emu, this one is quite pixelated.
See my link from the other thread:
http://commons.wikimedia.org/wiki/File:Emu_(PSF).png
Actually, I borrow that picture and do some
** Attachment added: patch
https://bugs.launchpad.net/qemu/+bug/889053/+attachment/2593058/+files/patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/889053
Title:
x86: FPU_MAX, FPU_MIN
misprint:
spec sphinx3 test data
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/889053
Title:
x86: FPU_MAX, FPU_MIN incorrect
Status in QEMU:
New
Bug description:
Dear All,
Bug was found
Public bug reported:
Dear All,
Bug was found in qemu.git.
Now (0.15, 1.0) all fpu is softfpu.
See target-i386/ops_sse.h:
#define FPU_MIN(size, a, b) (a) (b) ? (a) : (b)
#define FPU_MAX(size, a, b) (a) (b) ? (a) : (b)
It is incorrect now, becouse float64 (or 32) is (typedef) uint64_t (or 32).
This patch allows the hostfwd option to override the restrict=y setting in
the user network stack, as explicitly stated in the documentation on the
restrict option:
restrict=on|off
If this option is enabled, the guest will be isolated, i.e. it
will not be able to contact
On 11/10/2011 07:17 PM, Thomas Schmitt wrote:
Hi,
I only tested CD-RW DAO burning of an ISO image, plus invoking a bunch
of commands from Thomas's logs). The burning succeeded but reading
the resulting medium failed consistently at 26 MB. However, the same
happened even when doing CD
** Patch added: test.useprof.exe
https://bugs.launchpad.net/bugs/889053/+attachment/2593057/+files/test.useprof.exe
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/889053
Title:
x86: FPU_MAX,
482.sphinx3: http://www.spec.org/cpu2006/CFP2006/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/889053
Title:
x86: FPU_MAX, FPU_MIN incorrect
Status in QEMU:
New
Bug description:
Dear All,
The attached patch is incorrect (using the softfloat _min/_max functions will
give wrong answers for some special cases). The correct macros are
#define FPU_MIN(size, a, b) float ## size ## _lt(a, b, env-sse_status) ? (a)
: (b)
#define FPU_MAX(size, a, b) float ## size ## _lt(b, a,
From: Daniel P. Berrange berra...@redhat.com
When doing migration to an FD, a NULL 'mon' parameter
is being accessed, resulting in SEGV
* migration.c: Always set 's-mon'
Signed-off-by: Daniel P. Berrange berra...@redhat.com
NB, I've no idea if this is the right way to solve this,
since I
Libvirt recently introduced a change to the way it does 'save to file'
with QEMU. Historically QEMU has a 32MB/s I/O limit on migration by
default. When saving to file, we didn't want any artificial limit,
but rather to max out the underlying storage. So when doing save to
file, we set a large
On Fri, Nov 11, 2011 at 01:03:20PM +, Daniel P. Berrange wrote:
Libvirt recently introduced a change to the way it does 'save to file'
with QEMU. Historically QEMU has a 32MB/s I/O limit on migration by
default. When saving to file, we didn't want any artificial limit,
but rather to max
You might use Inkscape for M$ from http://inkscape.org/download/
and the highest resolution image from Wikipedia
(http://upload.wikimedia.org/wikipedia/commons/7/7d/Emu_%28PSF%29.png).
I have tried my best. :-)
http://people.cs.nctu.edu.tw/~chenwj/slide/QEMU/QEMU_Mascot.svg
Regards,
There are only three counter/timers on the integrator board:
correct the bounds check to avoid an array overrun. (Spotted
by Coverity, see bug 887883).
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/arm_timer.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff
On 11/11/2011 02:03 PM, Daniel P. Berrange wrote:
Or perhaps moving migration to a separate thread, out of the mainloop
is what we need to strive for ?
Yes, this is planned. This way the I/O does not even need to be
non-blocking.
Patches have been posted (and I have up-to-date versions)
Am 10.11.2011 17:01, schrieb Paolo Bonzini:
Mode page 2A of emulated ATAPI DVD-ROM should have page length 0x14
like SCSI CD-ROM, rather than 0x12.
Mode page length is off by 8, as it should contain the length of the
payload after the first two bytes.
MODE SENSE(6) should be thrown out of
On 11/11/2011 02:36 PM, Kevin Wolf wrote:
@@ -717,11 +712,10 @@ static void cmd_mode_sense(IDEState *s, uint8_t *buf)
buf[12] = 0x00;
buf[13] = 0x00;
buf[14] = 0x00;
-buf[15] = 0x00;
Why did you drop this? It still seems to be part
On 11/11/2011 03:36 AM, Markus Armbruster wrote:
Ping?
I assumed Compile-tested only, buyer beware. was code for, I'll test the
patches later and post to the ML ;-)
Regards,
Anthony Liguori
Markus Armbrusterarm...@redhat.com writes:
Compile-tested only, buyer beware.
Markus
Hey,
Here's one for the calendar - a 2 day track at FOSDEM devoted to Open
Source Virtualization and Cloud.
Hope to see you there! :)
Cheers,
Mark.
Forwarded Message
From: Thierry Carrez thie...@openstack.org
To: openst...@lists.launchpad.net openst...@lists.launchpad.net
Hello,
In the driver for the SMSC LAN9118 device (hw/lan9118.c), I modify the code to
update the PM_CTRL register (switch PM_MODE bits to D0 and set (1b) READY bit )
when writing to the BYTE_TEST register.
Writing to PM_CTRL was not permitted before this modification = raise an
harware error
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even with proper clustered storage. I think doing a block level flush
cache interface and letting block devices decide
Am 10.11.2011 17:01, schrieb Paolo Bonzini:
Add more commands and their names, and remove SEEK(6) which is obsolete.
Instead, use SET_POSITION which is still in SSC.
SET CAPACITY you mean?
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi-bus.c | 25
On 11/11/2011 03:38 AM, Kevin Wolf wrote:
Am 11.11.2011 01:11, schrieb Anthony Liguori:
I did a brain dump of my understanding of the various storage requirements for
live migration. I think it's accurate but I may have misunderstand some details
so I would appreciate review.
I think given
On 11/11/2011 03:55 AM, Daniel P. Berrange wrote:
On Fri, Nov 11, 2011 at 10:38:20AM +0100, Kevin Wolf wrote:
Am 11.11.2011 01:11, schrieb Anthony Liguori:
I did a brain dump of my understanding of the various storage requirements for
live migration. I think it's accurate but I may have
Hi,
Am 11.11.2011 14:44, schrieb Cachet Bertrand:
Patch is contained in the following commit :
https://bitbucket.org/bca/qemu-linaro/changeset/0aa1f76e5141
I have sent this patch to qemu-linaro but Peter Maydell (pm215 on #qemu
IRC channel) told me to send it here because it is against
On 11/11/2011 05:58 AM, Gertjan Halkes wrote:
This patch allows the hostfwd option to override the restrict=y setting in
the user network stack, as explicitly stated in the documentation on the
restrict option:
restrict=on|off
If this option is enabled, the guest will be
Am 11.11.2011 15:03, schrieb Anthony Liguori:
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to
work
right now even with proper clustered storage. I think doing a block level
On 11/11/2011 06:44 AM, Daniel P. Berrange wrote:
From: Daniel P. Berrangeberra...@redhat.com
When doing migration to an FD, a NULL 'mon' parameter
is being accessed, resulting in SEGV
* migration.c: Always set 's-mon'
Signed-off-by: Daniel P. Berrangeberra...@redhat.com
NB, I've no idea if
On 11/11/2011 08:29 AM, Kevin Wolf wrote:
Am 11.11.2011 15:03, schrieb Anthony Liguori:
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going to work
right now even with proper clustered
Am 11.11.2011 15:35, schrieb Anthony Liguori:
On 11/11/2011 08:29 AM, Kevin Wolf wrote:
Am 11.11.2011 15:03, schrieb Anthony Liguori:
On 11/11/2011 04:15 AM, Kevin Wolf wrote:
Am 10.11.2011 22:30, schrieb Anthony Liguori:
Live migration with qcow2 or any other image format is just not going
Hi,
Am 10.11.2011 23:10, schrieb Anthony Liguori:
[...] I thought it would be a fun part of the 1.0 release to have a
logo competition to create an official image of Q.
So break out Gimp, Inkscape, or your favorite image editor and submit an
icon for consideration! If we get enough
Hi,
The READ TOC/PMA/ATIP at the end of burning gives (reformatted):
43 02 02 00 00 00 00 00 51 00
From drive: 81b
00 4f 01 01
01 14 00 a0 00 00 00 00 01 00 00
01 14 00 a1 00 00 00 00 01 00 00
01 14 00 a2 00 00 00 00 18 39 32
01 14 00 01 00 00 00 00 00 02 00
I was not aware you did your
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove libqemu target from Makefile.target. I have ran the following test:
- process mode: linux-user-test-0.3
- system mode:
- arm-test-0.2.tar.gz
- minix204.tar.bz2
- linux-0.2.img.bz2
Signed-off-by: Chen Wei-Ren
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove statement about libqemu.a from LICENSE.
Signed-off-by: Chen Wei-Ren che...@iis.sinica.edu.tw
---
LICENSE |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/LICENSE b/LICENSE
index cbd92c0..acae9a3 100644
--- a/LICENSE
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove libqemu example since libqemu.a is not available anymore.
Signed-off-by: Chen Wei-Ren che...@iis.sinica.edu.tw
---
tests/qruncom.c | 284 ---
1 files changed, 0 insertions(+), 284
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove libqemu_common.a from the comment.
v1 - v2: Reverse the deletion of common-obj-y. Only remove libqemu_common.a
from the comment.
Signed-off-by: Chen Wei-Ren che...@iis.sinica.edu.tw
---
Makefile.objs |7 +++
1 files
From: Chen Wei-Ren che...@iis.sinica.edu.tw
According to [1], libqemu is not available anymore. Remove libqemu
related stuff from QEMU source tree.
[1] http://www.mail-archive.com/address@hidden/msg49809.html
Chen Wei-Ren (6):
tests/qruncom.c: Remove libqemu.a example
tests/Makefile:
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove qruncom target from the Makefile file since we have
removed libqemu example (qruncom.c).
Signed-off-by: Chen Wei-Ren che...@iis.sinica.edu.tw
---
tests/Makefile |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove libqemu related stuff from the document since libqemu.a is not
supported
anymore.
v1 - v2: Remove entry qruncom.c from 3 Regression Tests.
Signed-off-by: Chen Wei-Ren che...@iis.sinica.edu.tw
---
qemu-tech.texi | 10 --
1
On Fri, Nov 11, 2011 at 14:27, Cao,Bing Bu m...@linux.vnet.ibm.com wrote:
Hi,
I have post a HOWTO document about windows guest debugging on:
http://www.linux-kvm.org/page/WindowsGuestDrivers/UpdatedGuestDebugging
It include more details as a complement of
On 11 November 2011 14:53, Chen Wei-Ren (陳韋任) che...@iis.sinica.edu.tw wrote:
Remove libqemu target from Makefile.target.
diff --git a/Makefile.target b/Makefile.target
index a111521..d1f7993 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -92,14 +92,6 @@ tci-dis.o: QEMU_CFLAGS +=
On 11 November 2011 14:53, Chen Wei-Ren (陳韋任) che...@iis.sinica.edu.tw wrote:
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove qruncom target from the Makefile file since we have
removed libqemu example (qruncom.c).
This should be done before the patch removing qruncom.c, not after.
Or do
On 11/11/2011 07:24 AM, 陳韋任 wrote:
You might use Inkscape for M$ from http://inkscape.org/download/
and the highest resolution image from Wikipedia
(http://upload.wikimedia.org/wikipedia/commons/7/7d/Emu_%28PSF%29.png).
I have tried my best. :-)
On Fri, 11 Nov 2011 08:24:04 -0600, Anthony Liguori anth...@codemonkey.ws
wrote:
Please submit against qemu.git master with a Signed-off-by.
Ok, here goes:
This patch allows the hostfwd option to override the restrict=y setting in
the user network stack, as explicitly stated in the
On Fri, Nov 11, 2011 at 03:02:16PM +, Peter Maydell wrote:
On 11 November 2011 14:53, Chen Wei-Ren (陳韋任) che...@iis.sinica.edu.tw
wrote:
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove qruncom target from the Makefile file since we have
removed libqemu example (qruncom.c).
Hi,
Paolo Bonzini wrote:
case MODE_PAGE_R_W_ERROR: /* error recovery */
[...]
-buf[15] = 0x00;
Kevin Wolf wrote:
Why did you drop this? It still seems to be part of the buffer.
Paolo Bonzini wrote:
Actually, I think it's best if these patches wait until Thomas
This commit isn't doing what the commit message claims it does.
What you're actually removing is a set of manually inserted
dependencies of some object files on their source files and
on cpu.h. There is already no libqemu target in this makefile.
What you maybe wanted to remove is just the
On 11 November 2011 15:07, 陳韋任 che...@iis.sinica.edu.tw wrote:
On Fri, Nov 11, 2011 at 03:02:16PM +, Peter Maydell wrote:
On 11 November 2011 14:53, Chen Wei-Ren (陳韋任) che...@iis.sinica.edu.tw
wrote:
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove qruncom target from the Makefile
Am 11.11.2011 16:07, schrieb 陳韋任:
On Fri, Nov 11, 2011 at 03:02:16PM +, Peter Maydell wrote:
On 11 November 2011 14:53, Chen Wei-Ren (陳韋任) che...@iis.sinica.edu.tw
wrote:
From: Chen Wei-Ren che...@iis.sinica.edu.tw
Remove qruncom target from the Makefile file since we have
removed
** Changed in: qemu
Assignee: (unassigned) = pradeep (psuriset)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/888016
Title:
RHEL 6.1 guest fails to boot with vhost
Status in QEMU:
New
Bug
On 11/10/2011 03:19 AM, Peter Maydell wrote:
On 10 November 2011 01:45, Alexander Grafag...@suse.de wrote:
On 10.11.2011, at 02:36, Peter Maydell wrote:
This looks a bit fishy -- cpu_physical_memory_map() takes a
target_phys_addr_t but you're passing it a ram_addr_t.
Meh. Always those types
On 11 November 2011 15:59, Alexander Graf ag...@suse.de wrote:
This is the machine init function. The s390 virtio machine's ram layout is
defined to be exactly as I posted in the previous post. So there won't be
any ram starts at != 0 or multiple mappings :).
That's the layout of the RAM in
Am 11.11.2011 16:02, schrieb Michael Roth:
On 11/11/2011 07:24 AM, 陳韋任 wrote:
You might use Inkscape for M$ from http://inkscape.org/download/
and the highest resolution image from Wikipedia
(http://upload.wikimedia.org/wikipedia/commons/7/7d/Emu_%28PSF%29.png).
I have tried my best. :-)
This is awesome! I'm worried how well it will scale down though. If you
do the emu part on the right side, vertically, between the bottom of
its head and top of its foot, you can shrink the Q part a bit to make
the emu's body more proportional and leave more space for the emu text
on the
On 11/11/2011 05:11 PM, Peter Maydell wrote:
On 11 November 2011 15:59, Alexander Grafag...@suse.de wrote:
This is the machine init function. The s390 virtio machine's ram layout is
defined to be exactly as I posted in the previous post. So there won't be
any ram starts at != 0 or multiple
On Thu, 10 Nov 2011, Konrad Rzeszutek Wilk wrote:
On Fri, Oct 28, 2011 at 04:07:33PM +0100, Anthony PERARD wrote:
From: Allen Kay allen.m@intel.com
This is going to be a bit lame review..
[...]
+return;
+}
+
+/* find register group entry */
+
Hi Blue,
This is my current patch queue for ppc on QEMU 1.0. Please pull.
Alex
The following changes since commit 0e3b800e71cb7759d099eabbd8ad4c4fe848e381:
Peter Maydell (1):
hw/lan9118.c: Add missing 'break' to fix buffer overrun
are available in the git repository at:
From: David Gibson da...@gibson.dropbear.id.au
Since we added PCI support to the pseries machine, we include a qlist of
PCI host bridges in the sPAPREnvironment structure. However this list
was never properly initialized it. Somehow we got away with this until
some other recent change broke it,
From: David Gibson da...@gibson.dropbear.id.au
tcg/ppc64/tcg-target.c has a couple of places where variables are set
unconditionally, but otherwise used only for softmmu builds, not
userspace only builds. This causes compiler warnings (which are fatal
by default) when compiling for a ppc64 host
From: Sebastian Bauer m...@sebastianbauer.info
When using gdb to single step a ppc interrupt routine, the execution
flow passes the rfi instruction without actually returning from the
interrupt.
The patch fixes this by avoiding to update the nip when the debug
exception is raised and a previous
On 11 November 2011 16:24, Alexander Graf ag...@suse.de wrote:
On 11/11/2011 05:11 PM, Peter Maydell wrote:
Yes, so that's option (2) and you need to be using a target_phys_addr_t.
But ram_size is ram_addr_t and is the ram size that I have available to use,
so it's exactly the address that I
On 11/11/2011 05:44 PM, Peter Maydell wrote:
On 11 November 2011 16:24, Alexander Grafag...@suse.de wrote:
On 11/11/2011 05:11 PM, Peter Maydell wrote:
Yes, so that's option (2) and you need to be using a target_phys_addr_t.
But ram_size is ram_addr_t and is the ram size that I have
The bdrv_qed_is_allocated() function is a synchronous wrapper around
qed_find_cluster(), which performs the cluster lookup. In order to
convert the synchronous function to a coroutine function we yield
instead of using qemu_aio_wait(). Note that QED's cache is already safe
for parallel requests
The bdrv_is_allocated() interface is not suitable for use while the VM is
running. It is a synchronous interface so it may block the running VM for
arbitrary amounts of time. It also assumes it is the only block driver
operation and there is a risk that internal state could be corrupted if
For some reason vvfat.c invokes BlockDriver functions directly and does
not go through block.h functions. Change all direct calls except for
the .bdrv_make_empty() call for which there is no public interface.
This change makes the conversion to .bdrv_co_is_allocated() possible.
Signed-off-by:
The qcow2, qcow, and vmdk block drivers are based on coroutines. They have a
coroutine mutex which protects internal state. We can convert the
.bdrv_is_allocated() function to .bdrv_co_is_allocated() by holding the mutex
around the cluster lookup operation.
Signed-off-by: Stefan Hajnoczi
There is no need for bdrv_commit() to use the BlockDriver
.bdrv_is_allocated() interface directly. Converting to the public
interface gives us the freedom to drop .bdrv_is_allocated() entirely in
favor of a new .bdrv_co_is_allocated() in the future.
Signed-off-by: Stefan Hajnoczi
Am 11.11.2011 17:47, schrieb Stefan Hajnoczi:
For some reason vvfat.c invokes BlockDriver functions directly and does
not go through block.h functions. Change all direct calls except for
the .bdrv_make_empty() call for which there is no public interface.
This change makes the conversion to
This patch introduce the public bdrv_co_is_allocated() interface which
can be used to query image allocation status while the VM is running.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block.c | 37 -
block.h |2 ++
2 files changed, 26
The cow block driver does not keep internal state for cluster lookups.
This means it is safe to perform cluster lookups in coroutine context
without risk of race conditions that corrupt internal state.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block/cow.c |8
1
On 11/11/2011 10:20 AM, Kevin Wolf wrote:
Am 11.11.2011 16:02, schrieb Michael Roth:
On 11/11/2011 07:24 AM, 陳韋任 wrote:
You might use Inkscape for M$ from http://inkscape.org/download/
and the highest resolution image from Wikipedia
It is trivial to switch from the synchronous .bdrv_is_allocated()
interface to .bdrv_co_is_allocated() since vdi_is_allocated() does not
block.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block/vdi.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git
Now that all block drivers have been converted to
.bdrv_co_is_allocated() we can drop .bdrv_is_allocated().
Note that the public bdrv_is_allocated() interface is still available
but is in fact a synchronous wrapper around .bdrv_co_is_allocated().
Signed-off-by: Stefan Hajnoczi
It is trivial to switch from the synchronous .bdrv_is_allocated()
interface to .bdrv_co_is_allocated() since vvfat_is_allocated() does not
block.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block/vvfat.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On 11/11/2011 10:18 AM, 陳韋任 wrote:
This is awesome! I'm worried how well it will scale down though. If you
do the emu part on the right side, vertically, between the bottom of
its head and top of its foot, you can shrink the Q part a bit to make
the emu's body more proportional and leave more
This patch adds the .bdrv_co_is_allocated() interface which is identical
to .bdrv_is_allocated() but runs in coroutine context. Running in
coroutine context implies that other coroutines might be performing I/O
at the same time. Therefore it must be safe to run while the following
BlockDriver
The following changes since commit 0e3b800e71cb7759d099eabbd8ad4c4fe848e381:
hw/lan9118.c: Add missing 'break' to fix buffer overrun (2011-11-10 12:29:50
+)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git block-stable
Charles Arnold (1):
block: Fix vpc
vvfat used to directly call into the qcow2 block driver instead of using the
block.c wrappers. With the coroutine conversion, this stopped working.
Signed-off-by: Kevin Wolf kw...@redhat.com
Reviewed-by: Paolo Bonzini pbonz...@redhat.com
---
block/vvfat.c | 44
From: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/ide/atapi.c | 11 ---
hw/ide/core.c | 13 +
2 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/hw/ide/atapi.c
From: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Kevin Wolf kw...@redhat.com
---
hw/scsi-disk.c | 24 +---
1 files changed, 21 insertions(+), 3 deletions(-)
diff --git a/hw/scsi-disk.c b/hw/scsi-disk.c
index
1 - 100 of 190 matches
Mail list logo
