Re: [Qemu-devel] [PATCH] add info ioapic monitor command

2010-01-01 Thread Gleb Natapov
On Thu, Dec 31, 2009 at 12:57:44PM -0600, Anthony Liguori wrote: On 12/31/2009 09:33 AM, Gleb Natapov wrote: On Thu, Dec 31, 2009 at 08:15:29AM -0600, Anthony Liguori wrote: On 12/30/2009 06:16 PM, Gleb Natapov wrote: It helps debug problems and it is not intrusive. Since 0.12 will be used

Re: [Qemu-devel] [PATCHv2] add info ioapic monitor command

2010-01-01 Thread Gleb Natapov
On Thu, Dec 31, 2009 at 01:05:18PM -0600, Anthony Liguori wrote: On 12/31/2009 09:42 AM, Gleb Natapov wrote: On Thu, Dec 31, 2009 at 08:20:06AM -0600, Anthony Liguori wrote: On 12/30/2009 06:20 PM, Gleb Natapov wrote: I included only the state I need for debugging. I don't what to see

Re: [Qemu-devel] [PATCH] add info ioapic monitor command

2010-01-01 Thread Gleb Natapov
On Thu, Dec 31, 2009 at 01:01:50PM -0600, Anthony Liguori wrote: On 12/31/2009 09:39 AM, Gleb Natapov wrote: The common case is where you just want to see the state of the device. We support hundreds of devices. We can have one code path that displays 95% of them with a couple devices that

[Qemu-devel] LatticeMico32/Milkymist support

2010-01-01 Thread Sébastien Bourdeauducq
Hi, Would anyone be interested in adding the support of the LatticeMico32 [1] microprocessor and the Milkymist System-on-Chip [2] to QEMU? This would help the open source hardware movement by easing software development on free platforms. Currently, QEMU only supports proprietary systems.

[Qemu-devel] [PATCH] PPC: Add wrapper for target long DCR operations

2010-01-01 Thread Alexander Graf
The recent transition to always have the DCR helper functions take 32 bit values broke the PPC64 target, as tlong became 64 bits there. This patch moves all translate.c callers to a _tl function that simply calls the uint32_t functions. That way we don't need to mess with TCG trying to pass

Re: [Qemu-devel] [PATCH 14/14] Add -fstack-protector-all to CFLAGS

2010-01-01 Thread Kirill A. Shutemov
On Thu, Dec 31, 2009 at 12:58 PM, Arnaud Patard arnaud.pat...@rtp-net.org wrote: Kirill A. Shutemov kir...@shutemov.name writes: Hi, -fstack-protector-all emit extra code to check for buffer overflows, such as stack smashing attacks.  This is done by adding a guard variable to functions with

Re: [Qemu-devel] [PATCH 12/14] linux-user/mmap.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
On Thu, Dec 31, 2009 at 12:50 PM, Arnaud Patard arnaud.pat...@rtp-net.org wrote: Kirill A. Shutemov kir...@shutemov.name writes: Hi,   CC    i386-linux-user/mmap.o cc1: warnings being treated as errors /usr/src/RPM/BUILD/qemu-0.11.92/linux-user/mmap.c: In function 'mmap_frag':

Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9)

2010-01-01 Thread H. Peter Anvin
On 12/30/2009 08:49 AM, Kevin O'Connor wrote: On Tue, Dec 29, 2009 at 01:51:36PM -0800, H. Peter Anvin wrote: Add generic support for debugging consoles (simple I/O ports which when written to cause debugging output to be written to a target.) The current implementation matches Bochs' port

Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9)

2010-01-01 Thread H. Peter Anvin
On 12/30/2009 08:49 AM, Kevin O'Connor wrote: Hi, SeaBIOS writes debugging info to port 0x0402. Unfortunately, qemu has to be recompiled in order to display this info. Will your patch enable one to get at the 0x0402 data without recompiling? -Kevin Incidentally, it's somewhat

[Qemu-devel] [PATCH 01/15] Introduce qemu_write_full()

2010-01-01 Thread Kirill A. Shutemov
A variant of write(2) which handles partial write. Signed-off-by: Kirill A. Shutemov kir...@shutemov.name --- osdep.c | 27 +++ qemu-common.h |2 ++ 2 files changed, 29 insertions(+), 0 deletions(-) diff --git a/osdep.c b/osdep.c index e4836e7..8ae48fe 100644

[Qemu-devel] [PATCH 02/15] posix-aio-compat.c: fix warning with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCposix-aio-compat.o cc1: warnings being treated as errors posix-aio-compat.c: In function 'aio_signal_handler': posix-aio-compat.c:505: error: ignoring return value of 'write', declared with attribute warn_unused_result make: *** [posix-aio-compat.o] Error 1 Signed-off-by: Kirill A.

[Qemu-devel] [PATCH 03/15] block/cow.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCblock/cow.o cc1: warnings being treated as errors block/cow.c: In function 'cow_create': block/cow.c:251: error: ignoring return value of 'write', declared with attribute warn_unused_result block/cow.c:253: error: ignoring return value of 'ftruncate', declared with attribute

[Qemu-devel] [PATCH 04/15] block/qcow.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCblock/qcow.o cc1: warnings being treated as errors block/qcow.c: In function 'qcow_create': block/qcow.c:804: error: ignoring return value of 'write', declared with attribute warn_unused_result block/qcow.c:806: error: ignoring return value of 'write', declared with attribute

[Qemu-devel] [PATCH 05/15] block/vmdk.o: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCblock/vmdk.o cc1: warnings being treated as errors block/vmdk.c: In function 'vmdk_snapshot_create': block/vmdk.c:236: error: ignoring return value of 'ftruncate', declared with attribute warn_unused_result block/vmdk.c: In function 'vmdk_create': block/vmdk.c:775: error: ignoring return

[Qemu-devel] [PATCH 06/15] block/vvfat.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCblock/vvfat.o cc1: warnings being treated as errors block/vvfat.c: In function 'commit_one_file': block/vvfat.c:2259: error: ignoring return value of 'ftruncate', declared with attribute warn_unused_result make: *** [block/vvfat.o] Error 1 CCblock/vvfat.o In file included from

[Qemu-devel] [PATCH 07/15] block/qcow2.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCblock/qcow2.o cc1: warnings being treated as errors block/qcow2.c: In function 'qcow_create2': block/qcow2.c:829: error: ignoring return value of 'write', declared with attribute warn_unused_result block/qcow2.c:838: error: ignoring return value of 'write', declared with attribute

[Qemu-devel] [PATCH 08/15] net/slirp.c: fix warning with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCnet/slirp.o cc1: warnings being treated as errors net/slirp.c: In function 'slirp_smb_cleanup': net/slirp.c:470: error: ignoring return value of 'system', declared with attribute warn_unused_result make: *** [net/slirp.o] Error 1 Signed-off-by: Kirill A. Shutemov kir...@shutemov.name ---

[Qemu-devel] [PATCH 09/15] usb-linux.c: fix warning with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCusb-linux.o cc1: warnings being treated as errors usb-linux.c: In function 'usb_host_read_file': usb-linux.c:1204: error: ignoring return value of 'fgets', declared with attribute warn_unused_result make: *** [usb-linux.o] Error 1 Signed-off-by: Kirill A. Shutemov kir...@shutemov.name

[Qemu-devel] [PATCH 11/15] monitor.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCi386-softmmu/monitor.o cc1: warnings being treated as errors /usr/src/RPM/BUILD/qemu-0.11.92/monitor.c: In function 'do_memory_save': /usr/src/RPM/BUILD/qemu-0.11.92/monitor.c:1318: error: ignoring return value of 'fwrite', declared with attribute warn_unused_result

[Qemu-devel] [PATCH 10/15] vl.c: fix warning with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCi386-softmmu/vl.o cc1: warnings being treated as errors /usr/src/RPM/BUILD/qemu-0.11.92/vl.c: In function 'qemu_event_increment': /usr/src/RPM/BUILD/qemu-0.11.92/vl.c:3404: error: ignoring return value of 'write', declared with attribute warn_unused_result

[Qemu-devel] [PATCH 12/15] linux-user/mmap.c: fix warnings with _FORTIFY_SOURCE

2010-01-01 Thread Kirill A. Shutemov
CCi386-linux-user/mmap.o cc1: warnings being treated as errors /usr/src/RPM/BUILD/qemu-0.11.92/linux-user/mmap.c: In function 'mmap_frag': /usr/src/RPM/BUILD/qemu-0.11.92/linux-user/mmap.c:253: error: ignoring return value of 'pread', declared with attribute warn_unused_result

[Qemu-devel] [PATCH 13/15] Enable _FORTIFY_SOURCE=2

2010-01-01 Thread Kirill A. Shutemov
_FORTIFY_SOURCE is a Glibc feature which adds memory and string function protection. Signed-off-by: Kirill A. Shutemov kir...@shutemov.name --- configure |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure b/configure index 18aed43..0cdcdb3 100755 --- a/configure

[Qemu-devel] [PATCH 14/15] Add -fstack-protector-all to CFLAGS

2010-01-01 Thread Kirill A. Shutemov
-fstack-protector-all emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. Signed-off-by: Kirill A. Shutemov kir...@shutemov.name --- configure |8 1 files changed, 8

[Qemu-devel] [PATCH 15/15] linux-user: fix return value of mmap_frag()

2010-01-01 Thread Kirill A. Shutemov
mmap_frag() returns -1 on error and set errno. Signed-off-by: Kirill A. Shutemov kir...@shutemov.name --- linux-user/mmap.c |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/linux-user/mmap.c b/linux-user/mmap.c index c1c7e48..47bc339 100644 --- a/linux-user/mmap.c

[Qemu-devel] USB-UHCI skipping frames from the frame list

2010-01-01 Thread Althaf K Backer
Given below is the debug o/p from usb-uhci,strangely it seems to skip the frames after 118 it jumps to 145 .. similar is the case with frame 0 , it doesn't load frame 0 rather jumps to frame 1.The guest is minix 3.1.5 and the o/p was generated from the driver under development,i have notice the