Re: [Qemu-devel] qemu-cvs-2007-5-2 compile error

[Sunil Amitkumar Janki]

Hwang YunSong(황윤성) wrote:
> make[1]: Entering directory `/home/hys545/qemu/arm-softmmu'
> gcc33 -Wall -O2 -g -fno-strict-aliasing -I. -I.. 
> -I/usr/src/Haansoft/BUILD/qemu/target-arm -I/usr/src/Haansoft/BUILD/qemu 
> -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -I/usr/src/Haansoft/BUILD/qemu/fpu -DHAS_AUDIO -DHIGH_LATENCY 
> -I/usr/src/Haansoft/BUILD/qemu/slirp-c -o alsaaudio.o 
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c: In function `alsa_open':
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: 
> `DEFAULT_BUFFER_SIZE' undeclared (first use in this function)
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: (Each undeclared 
> identifier is reported only once
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: for each function 
> it appears in.)
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:360: error: 
> `DEFAULT_PERIOD_SIZE' undeclared (first use in this function)
> make[1]: *** [alsaaudio.o] 오류 1
> make[1]: Leaving directory `/home/hys545/qemu/arm-softmmu'
>   
I had the same error 3 days ago but I don't know what it is caused by.
I also looked for DEFAULT_BUFFER_SIZE and DEFAULT_PERIOD_SIZE
in /usr/include but couldn't find them. Maybe someone knows what this error
message is about, e.g. newer ALSA headers necessary.

[Qemu-devel] Saving state on a context switch

[eady]

Can anyone think of a way to save and restore an additional cpu state 
variable during a context switch without modifying the target operating 
system? Basically I would like to add a variable to the CPUState 
structure that is saved and restored with the registers.


Any ideas?

Thanks,
Nuri

Re: [Qemu-devel] Saving state on a context switch

[Paul Brook]

On Wednesday 02 May 2007, eady wrote:
> Can anyone think of a way to save and restore an additional cpu state
> variable during a context switch without modifying the target operating
> system? Basically I would like to add a variable to the CPUState
> structure that is saved and restored with the registers.

The short answer is that in general you can't.

Processes and contexts are managed by the host OS, and it is responsible for 
switching state appropriately. Some hardware has features to assist this 
process, but often not enough to reliably identify a particular process.

To do what you want generally requires intimite knowledge of the appropriate 
parts of your OS. Some debuggers are capable of doing this.
There are patches to add scripting support to GDB for this purpose. I don't 
have a URL handy, check the gdb mailing lists.

Paul

[Qemu-devel] QEMU Various Vulnerabilities

[Kirill A. Shutemov]

http://secunia.com/advisories/25073/

Any comments ?

-- 
Regards,  Kirill A. Shutemov
 + Belarus, Minsk
 + Velesys LLC, http://www.velesys.com/
 + ALT Linux Team, http://www.altlinux.com/


signature.asc
Description: Digital signature

Re: [Qemu-devel] QEMU Various Vulnerabilities

[malc]

On Wed, 2 May 2007, Kirill A. Shutemov wrote:


http://secunia.com/advisories/25073/

Any comments ?


AAM - http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00650.html
SB16/DMA - in attachment

--
valeIndex: hw/dma.c
===
RCS file: /cvsroot/qemu/qemu/hw/dma.c,v
retrieving revision 1.14
diff -u -r1.14 dma.c
--- hw/dma.c21 Nov 2005 23:29:55 -  1.14
+++ hw/dma.c2 May 2007 14:23:19 -
@@ -438,6 +438,13 @@
 write_cont (d, (0x0d << d->dshift), 0);
 }
 
+static int dma_phony_handler (void *opaque, int nchan, int dma_pos, int 
dma_len)
+{
+dolog ("unregistered DMA channel used nchan=%d dma_pos=%d dma_len=%d\n",
+   nchan, dma_pos, dma_len);
+return dma_pos;
+}
+
 /* dshift = 0: 8 bit DMA, 1 = 16 bit DMA */
 static void dma_init2(struct dma_cont *d, int base, int dshift,
   int page_base, int pageh_base)
@@ -470,6 +477,9 @@
 }
 qemu_register_reset(dma_reset, d);
 dma_reset(d);
+for (i = 0; i < LENOFA (d->regs); ++i) {
+d->regs[i].transfer_handler = dma_phony_handler;
+}
 }
 
 static void dma_save (QEMUFile *f, void *opaque)
Index: hw/sb16.c
===
RCS file: /cvsroot/qemu/qemu/hw/sb16.c,v
retrieving revision 1.23
diff -u -r1.23 sb16.c
--- hw/sb16.c   7 Apr 2007 18:14:41 -   1.23
+++ hw/sb16.c   2 May 2007 14:23:19 -
@@ -1189,6 +1189,12 @@
 SB16State *s = opaque;
 int till, copy, written, free;
 
+if (s->block_size <= 0) {
+dolog ("invalid block size=%d nchan=%d dma_pos=%d dma_len=%d\n",
+   s->block_size, nchan, dma_pos, dma_len);
+return dma_pos;
+}
+
 if (s->left_till_irq < 0) {
 s->left_till_irq = s->block_size;
 }

[Qemu-devel] what type of serial does qemu support ?

[tang peilei]

i hope to use qemu's serial, the qemu is qemu-system-arm, and the os 
is linux.
but i found i can not get a serial console, i think the problem may be in 
the serial's driver code of linux, so who knows what type of serial in qemu 
?? 8250 ?? or who knows what kernel config is need to support qemu's serial 
in linux2.6.


_
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com  

Re: [Qemu-devel] what type of serial does qemu support ?

[Paul Brook]

On Wednesday 02 May 2007, tang peilei wrote:
>  i hope to use qemu's serial, the qemu is qemu-system-arm, and the os
> is linux.
> but i found i can not get a serial console, i think the problem may be in
> the serial's driver code of linux, so who knows what type of serial in qemu
> ?? 8250 ?? or who knows what kernel config is need to support qemu's serial
> in linux2.6.

As the qemu documentation clearly states, the arm 
integrator/versatile/realview boards have PL011 serial ports.
Use console=ttyAMA0. The arm-test image on the qemu website includes a kernel 
config.

Paul

[Qemu-devel] easiest way to share data between host and guest?

[Maxime Tierrie]

Hi,
I'm a newbie with Qemu and linux for arm. The arm-test-0.2.tar.gz file 
in the download page seems to be very interesting for me. I didn't 
manage to share data between arm-linux guest and my linux host by using 
tftp. I think it's because the provided tftp client in the arm-linux 
supports only "octet" mode.
So the question is : what is the easiest way to share data between the 
host and the guest?

thanks in advance.

[Qemu-devel] qemu/target-sparc op.c

[Blue Swirl]

CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl   07/05/02 16:37:44

Modified files:
target-sparc   : op.c 

Log message:
Handle division by zero case in Sparc64 udivx and sdivx ops

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/op.c?cvsroot=qemu&r1=1.31&r2=1.32

Re: [Qemu-devel] [PATCH] Getting 32-bit Vista on KVM

[andrzej zaborowski]

Hi,

On 02/05/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:

Now I realized that I needed to use 32-bit Linux to build the bios.bin
(i.e. BIOS-bochs-latest) in bochs. As long as I used x86-64 Linux to
build bios.bin, the resulting binary had a problem, as I reported
previously.


A patch for this has been recently posted to Bochs-developers:
http://www.nabble.com/-PATCH--add--m32-flag-to-bios-Makefile.in-t3632406.html
(the official list archive doesn't seem to work at the moment)



With this very simple patch, I was able to install and run 32-bit Vista
on KVM (almost the latest tree) on the 64-bit host. Thanks Qing for
debuging this. I believe this should work for Qemu as well.

Jun
---
Intel Open Source Technology Center

Signed-off-by: Qing He <[EMAIL PROTECTED]>
Signed-off-by: Jun Nakajima <[EMAIL PROTECTED]>

Index: rombios32.c
===
RCS file: /cvsroot/bochs/bochs/bios/rombios32.c,v
retrieving revision 1.9
diff -u -w -r1.9 rombios32.c
--- rombios32.c 20 Feb 2007 09:36:55 -  1.9
+++ rombios32.c 2 May 2007 06:07:31 -
@@ -1191,7 +1191,7 @@
 {
 memcpy(h->signature, sig, 4);
 h->length = cpu_to_le32(len);
-h->revision = 0;
+h->revision = 1;
 #ifdef BX_QEMU
 memcpy(h->oem_id, "QEMU  ", 6);
 memcpy(h->oem_table_id, "QEMU", 4);

Re: [Qemu-devel] qemu-cvs-2007-5-2 compile error

[andrzej zaborowski]

Hi,

On 02/05/07, Sunil Amitkumar Janki <[EMAIL PROTECTED]> wrote:

Hwang YunSong(황윤성) wrote:
> make[1]: Entering directory `/home/hys545/qemu/arm-softmmu'
> gcc33 -Wall -O2 -g -fno-strict-aliasing -I. -I.. 
-I/usr/src/Haansoft/BUILD/qemu/target-arm -I/usr/src/Haansoft/BUILD/qemu 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-I/usr/src/Haansoft/BUILD/qemu/fpu -DHAS_AUDIO -DHIGH_LATENCY 
-I/usr/src/Haansoft/BUILD/qemu/slirp-c -o alsaaudio.o 
/usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c: In function `alsa_open':
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: 
`DEFAULT_BUFFER_SIZE' undeclared (first use in this function)
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: (Each undeclared 
identifier is reported only once
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:359: error: for each function 
it appears in.)
> /usr/src/Haansoft/BUILD/qemu/audio/alsaaudio.c:360: error: 
`DEFAULT_PERIOD_SIZE' undeclared (first use in this function)
> make[1]: *** [alsaaudio.o] 오류 1
> make[1]: Leaving directory `/home/hys545/qemu/arm-softmmu'
>
I had the same error 3 days ago but I don't know what it is caused by.
I also looked for DEFAULT_BUFFER_SIZE and DEFAULT_PERIOD_SIZE
in /usr/include but couldn't find them. Maybe someone knows what this error
message is about, e.g. newer ALSA headers necessary.


Sorry, this was caused by adding audio in qemu-system-arm and adding
-DHIGH_LATENCY (which in turn triggered a problem in alsaaudio.c). Now
I removed the HIGH_LATENCY definition, but also changed alsaaudio.c to
compile with HIGH_LATENCY.

Andrzej

Re: [Qemu-devel] what type of serial does qemu support ?

[tang peilei]

thank you very much, you are right.




From: Paul Brook <[EMAIL PROTECTED]>
Reply-To: qemu-devel@nongnu.org
To: qemu-devel@nongnu.org
CC: tang peilei <[EMAIL PROTECTED]>
Subject: Re: [Qemu-devel] what type of serial does qemu support ?
Date: Wed, 2 May 2007 15:53:15 +0100

On Wednesday 02 May 2007, tang peilei wrote:
>  i hope to use qemu's serial, the qemu is qemu-system-arm, and the 

os

> is linux.
> but i found i can not get a serial console, i think the problem may be 

in
> the serial's driver code of linux, so who knows what type of serial in 

qemu
> ?? 8250 ?? or who knows what kernel config is need to support qemu's 

serial

> in linux2.6.

As the qemu documentation clearly states, the arm
integrator/versatile/realview boards have PL011 serial ports.
Use console=ttyAMA0. The arm-test image on the qemu website includes a 

kernel

config.

Paul




_
免费下载 MSN Explorer:   http://explorer.msn.com/lccn/  

[Qemu-devel] OT: funny google ads you get when you subscribe to the qemu list

[Jonathan Kalbfeld]

Apparently the rest of the world think we have something to do with plastic
surgery or home mortgages here...

Do European gmail users get bombarded with adjustible rate mortgages or is
that a North American phenomenon?
I especially like the liposuction ad, which is probably because the
GoogleBorg knows I live in Los Angeles...

Enjoy:

Arm Liposuction
$3400
Permanently smaller arms in 1 hour. Drive yourself home.View our prices
www.dralanbittner.com
100% option 
ARM
100% financing stated on option ARM 100% investment property to 1Mil
www.ezhomeloan.com
1% Pay Option Arm
Loans
1% pay option arm loans, 50 states 40 year loans, free quote, 100%
www.247negamloans.com
ARM Single Board
Computer
ARM 920T based development platform running Linux, Windows CE
www.littlechips.com More about...


--
--
Jonathan Kalbfeld
+1 323 620 6682

RE: [kvm-devel] [Qemu-devel] [PATCH] Getting 32-bit Vista on KVM

[Nakajima, Jun]

andrzej zaborowski wrote:
> Hi,
> 
> On 02/05/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:
>> Now I realized that I needed to use 32-bit Linux to build the
>> bios.bin (i.e. BIOS-bochs-latest) in bochs. As long as I used x86-64
>> Linux to build bios.bin, the resulting binary had a problem, as I
>> reported previously.
> 
> A patch for this has been recently posted to Bochs-developers:
>
http://www.nabble.com/-PATCH--add--m32-flag-to-bios-Makefile.in-t3632406
.html
> (the official list archive doesn't seem to work at the moment)
> 
Thanks!

Jun
---
Intel Open Source Technology Center

Re: [Qemu-devel] Patch for SDL framebuffer console problem

[Rob Landley]

On Tuesday 24 April 2007 2:23 am, Kitambi Leo wrote:
> I've been using qemu using the Linux framebuffer console, on a machine
> that's a bit too slow to support X.  There have been more than a few snags,
> but perhaps the most irritating one was that if qemu crashed (and received a
> SIGSEGV), it would leave the console in an unusable state.  This would
> require me to log into the machine via ssh and reboot it remotely.

Type "reset" and hit enter when this happens.

Rob

[Qemu-devel] Re: [PATCH] Getting 32-bit Vista on KVM

[consul]

With this patch I am little farther installing Vista, however install still 
crashes with BSOD
PAGE_FAULT_IN_NONPAGED_AREA


"Nakajima, Jun" <[EMAIL PROTECTED]> wrote 
in message 
news:[EMAIL PROTECTED]
> Now I realized that I needed to use 32-bit Linux to build the bios.bin
> (i.e. BIOS-bochs-latest) in bochs. As long as I used x86-64 Linux to
> build bios.bin, the resulting binary had a problem, as I reported
> previously.
>
> With this very simple patch, I was able to install and run 32-bit Vista
> on KVM (almost the latest tree) on the 64-bit host. Thanks Qing for
> debuging this. I believe this should work for Qemu as well.
>
> Jun
> ---
> Intel Open Source Technology Center
>
> Signed-off-by: Qing He <[EMAIL PROTECTED]>
> Signed-off-by: Jun Nakajima 
> <[EMAIL PROTECTED]>
>
> Index: rombios32.c
> ===
> RCS file: /cvsroot/bochs/bochs/bios/rombios32.c,v
> retrieving revision 1.9
> diff -u -w -r1.9 rombios32.c
> --- rombios32.c 20 Feb 2007 09:36:55 -  1.9
> +++ rombios32.c 2 May 2007 06:07:31 -
> @@ -1191,7 +1191,7 @@
> {
> memcpy(h->signature, sig, 4);
> h->length = cpu_to_le32(len);
> -h->revision = 0;
> +h->revision = 1;
> #ifdef BX_QEMU
> memcpy(h->oem_id, "QEMU  ", 6);
> memcpy(h->oem_table_id, "QEMU", 4);
>
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/