[Qemu-devel] Re: Qemu-devel Digest, Vol 34, Issue 8

["Josè Gerardo Gonzàlez Jimènez" <libereco@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 17860 bytes --]

Hi, i'm new on this list... bus i have a   suggestion, is not ease read
mails with 100 lines of code... why don't put it in a webpage/blog, and only
paste an URL to see it?? that may make more clean to read this mails...

friendly

2006/1/4, qemu-devel-request@nongnu.org <qemu-devel-request@nongnu.org>:
>
> Send Qemu-devel mailing list submissions to
>         qemu-devel@nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.nongnu.org/mailman/listinfo/qemu-devel
> or, via email, send a message with subject or body 'help' to
>         qemu-devel-request@nongnu.org
>
> You can reach the person managing the list at
>         qemu-devel-owner@nongnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Qemu-devel digest..."
>
>
> Today's Topics:
>
>    1. [PATCH 1/3] ide id updates (Jens Axboe)
>    2. qemu-smp guest on monoCPU host: big slowdown (octane indice)
>    3. Problems bringing up network in qemu-system-arm
>       (Wolfgang Schildbach)
>    4. CL-GD5446 technical reference manual, anyone?
>       (engel@mathematik.uni-marburg.de)
>    5. Pharmaceutical revolution (Emphysema U. Contrasts)
>    6. Re: qemu and configuration file? (Mike Kronenberg)
>    7. Re: Problems bringing up network in qemu-system-arm
>       (Daniel Jacobowitz)
>    8. Re: CL-GD5446 technical reference manual, anyone? (Paul Brook)
>    9. [PATCH] Mention --enable-cocoa in --help (Pavel Jan?k )
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Jan 2006 13:12:57 +0100
> From: Jens Axboe <qemu@kernel.dk>
> Subject: [Qemu-devel] [PATCH 1/3] ide id updates
> To: qemu-devel@nongnu.org
> Message-ID: <20060104121256.GB3389@suse.de>
> Content-Type: text/plain; charset=us-ascii
>
> Hi,
>
> Subject: [PATCH] ide id updates
> From: Jens Axboe <axboe@suse.de>
> Date: 1136375788 +0100
>
> Some changes to the ata/atapi identify code and default values:
>
> - Store the drive id in the IDEState, so we can reliably set and query
>   new values. Right now doing things like:
>
> doesn't work, as the IDENTIFY command will re-fill default values
> everytime.
>
> - Fill in IORDY, dma timings, and mdma modes.
>
> - Don't set both 1 << 14 and 0x4000 for word 93, it's the same thing.
>
> - Fill in supported/set ata specs
>
> - Implement real setting of transfer mode (sub feature 0x03 of
>   WIN_SETFEATURES) so we can reflect the transfer mode requested by the
>   OS.
>
> With this patch, Linux correctly identifies and sets DMA mode in the
> drive by default.
>
> ---
>
> hw/ide.c |   61
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
> 1 files changed, 54 insertions(+), 7 deletions(-)
>
> eaa17552cf9891cbc8fc46b826fde10a4d5e07c7
> diff --git a/hw/ide.c b/hw/ide.c
> index 28ed5ab..8196ace 100644
> --- a/hw/ide.c
> +++ b/hw/ide.c
> @@ -296,6 +296,8 @@ typedef struct IDEState {
>      int cylinders, heads, sectors;
>      int64_t nb_sectors;
>      int mult_sectors;
> +    int identify_set;
> +    uint16_t identify_data[256];
>      SetIRQFunc *set_irq;
>      void *irq_opaque;
>      int irq;
> @@ -414,6 +416,11 @@ static void ide_identify(IDEState *s)
>      unsigned int oldsize;
>      char buf[20];
>
> +    if (s->identify_set) {
> +       memcpy(s->io_buffer, s->identify_data, sizeof(s->identify_data));
> +       return;
> +    }
> +
>      memset(s->io_buffer, 0, 512);
>      p = (uint16_t *)s->io_buffer;
>      put_le16(p + 0, 0x0040);
> @@ -433,10 +440,10 @@ static void ide_identify(IDEState *s)
>      put_le16(p + 47, 0x8000 | MAX_MULT_SECTORS);
> #endif
>      put_le16(p + 48, 1); /* dword I/O */
> -    put_le16(p + 49, 1 << 9 | 1 << 8); /* DMA and LBA supported */
> +    put_le16(p + 49, (1 << 11) | (1 << 9) | (1 << 8)); /* DMA and LBA
> supported */
>      put_le16(p + 51, 0x200); /* PIO transfer cycle */
>      put_le16(p + 52, 0x200); /* DMA transfer cycle */
> -    put_le16(p + 53, 1 | 1 << 2); /* words 54-58,88 are valid */
> +    put_le16(p + 53, 1 | 1 << 1 | 1 << 2); /* words 54-58,64-70,88 are
> valid */
>      put_le16(p + 54, s->cylinders);
>      put_le16(p + 55, s->heads);
>      put_le16(p + 56, s->sectors);
> @@ -447,15 +454,24 @@ static void ide_identify(IDEState *s)
>          put_le16(p + 59, 0x100 | s->mult_sectors);
>      put_le16(p + 60, s->nb_sectors);
>      put_le16(p + 61, s->nb_sectors >> 16);
> -    put_le16(p + 80, (1 << 1) | (1 << 2));
> +    put_le16(p + 63, 0x07); /* mdma0-2 supported */
> +    put_le16(p + 65, 120);
> +    put_le16(p + 66, 120);
> +    put_le16(p + 67, 120);
> +    put_le16(p + 68, 120);
> +    put_le16(p + 80, 0xf0); /* ata3 -> ata6 supported */
> +    put_le16(p + 81, 0x16); /* conforms to ata5 */
>      put_le16(p + 82, (1 << 14));
>      put_le16(p + 83, (1 << 14));
>      put_le16(p + 84, (1 << 14));
>      put_le16(p + 85, (1 << 14));
>      put_le16(p + 86, 0);
>      put_le16(p + 87, (1 << 14));
> -    put_le16(p + 88, 0x1f | (1 << 13));
> -    put_le16(p + 93, 1 | (1 << 14) | 0x2000 | 0x4000);
> +    put_le16(p + 88, 0x3f | (1 << 13)); /* udma5 set and supported */
> +    put_le16(p + 93, 1 | (1 << 14) | 0x2000);
> +
> +    memcpy(s->identify_data, p, sizeof(s->identify_data));
> +    s->identify_set = 1;
> }
>
> static void ide_atapi_identify(IDEState *s)
> @@ -463,6 +479,11 @@ static void ide_atapi_identify(IDEState
>      uint16_t *p;
>      char buf[20];
>
> +    if (s->identify_set) {
> +       memcpy(s->io_buffer, s->identify_data, sizeof(s->identify_data));
> +       return;
> +    }
> +
>      memset(s->io_buffer, 0, 512);
>      p = (uint16_t *)s->io_buffer;
>      /* Removable CDROM, 50us response, 12 byte packets */
> @@ -483,11 +504,14 @@ static void ide_atapi_identify(IDEState
>      put_le16(p + 66, 0xb4); /* recommended DMA multiword tx cycle time */
>      put_le16(p + 67, 0x12c); /* minimum PIO cycle time without flow
> control */
>      put_le16(p + 68, 0xb4); /* minimum PIO cycle time with IORDY flow
> control */
> -
> +
>      put_le16(p + 71, 30); /* in ns */
>      put_le16(p + 72, 30); /* in ns */
>
>      put_le16(p + 80, 0x1e); /* support up to ATA/ATAPI-4 */
> +
> +    memcpy(s->identify_data, p, sizeof(s->identify_data));
> +    s->identify_set = 1;
> }
>
> static void ide_set_signature(IDEState *s)
> @@ -1601,13 +1625,36 @@ static void ide_ioport_write(void *opaqu
>              /* XXX: valid for CDROM ? */
>              switch(s->feature) {
>              case 0x02: /* write cache enable */
> -            case 0x03: /* set transfer mode */
>              case 0x82: /* write cache disable */
>              case 0xaa: /* read look-ahead enable */
>              case 0x55: /* read look-ahead disable */
>                  s->status = READY_STAT | SEEK_STAT;
>                  ide_set_irq(s);
>                  break;
> +            case 0x03: { /* set transfer mode */
> +               uint8_t val = s->nsector & 0x07;
> +
> +               switch (s->nsector >> 3) {
> +                   case 0x00: /* pio default */
> +                   case 0x01: /* pio mode */
> +                       put_le16(s->identify_data + 63,0x07);
> +                       put_le16(s->identify_data + 88,0x3f);
> +                       break;
> +                   case 0x04: /* mdma mode */
> +                       put_le16(s->identify_data + 63,0x07 | (1 << (val +
> 8)));
> +                       put_le16(s->identify_data + 88,0x3f);
> +                       break;
> +                   case 0x08: /* udma mode */
> +                       put_le16(s->identify_data + 63,0x07);
> +                       put_le16(s->identify_data + 88,0x3f | (1 << (val +
> 8)));
> +                       break;
> +                   default:
> +                       goto abort_cmd;
> +               }
> +                s->status = READY_STAT | SEEK_STAT;
> +                ide_set_irq(s);
> +                break;
> +           }
>              default:
>                  goto abort_cmd;
>              }
> --
> 1.0.GIT
>
> --
> Jens Axboe
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 04 Jan 2006 13:26:41 +0100
> From: octane indice <octane@alinto.com>
> Subject: [Qemu-devel] qemu-smp guest on monoCPU host: big slowdown
> To: qemu-devel@nongnu.org
> Message-ID: <1136377601.43bbbf0178301@webmail.alinto.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello
>
> I'm trying to use the new -smp option.
> host: win2k
> guest: linux 2.6.13-SMP
>
> The first sight is a really big slowdown.
> with -smp 2, the guest seems to go approximatively to 1/4 speed of a
> monoCPU guest.
>
> I tried to boot with -smp 8, but it was so slow that I abandoned.
>
> Am I doing something wrong?
> Is it unavoidable? Some options to use to compile qemu, or to
> compile the SMP kernel?
>
> Thanks for all informations
>
> ---------------------------------------------
> Alinto vous souhaite une très bonne année 2006 http://www.alinto.com
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 4 Jan 2006 16:56:13 +0100
> From: Wolfgang Schildbach <wolfgang.schildbach@codingtechnologies.com>
> Subject: [Qemu-devel] Problems bringing up network in qemu-system-arm
> To: qemu-devel@nongnu.org
> Message-ID:
>         <
> OF2F26C906.4744374A-ONC12570EC.00578112-C12570EC.00578B87@codingtechnologies.com
> >
>
> Content-Type: text/plain; charset="US-ASCII"
>
> Hi everyone,
>
> I am using the current CVS (HEAD) version of qemu running on x86 linux,
> and am using it to emulate an ARM on the integrator board, running
> arm-linux, using arm-test-0.1.tar.gz.
>
> >From what I've read in this list (
> http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00137.html), it
> should be possible to set up a network, user-mode or TUN/TAP. However, I
> fail to see the light as to how to bring the correct interface up on the
> guest system (arm-linux). ifconfig shows two devices, lo and dummy0, but
> nothing that would point to a smc91 being detected or used. This is
> independent from whether I try -net tap or -net user.
>
> 1) Is the network/smc91x support finished enough to be useable?
> 2) If so, what is the magic bullet? Any boot options that I need to give
> to the kernel? (BTW, I am calling the emulation as
>
> qemu-system-arm -kernel integratorcp.zImage -initrd arm_root.imfg
> -nographic -net user )
>
> Thanks much for any help,
> Wolfgang
> --
> Wolfgang Schildbach, Senior Research Engineer
> Coding Technologies GmbH
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 4 Jan 2006 18:41:54 +0100 (CET)
> From: engel@mathematik.uni-marburg.de
> Subject: [Qemu-devel] CL-GD5446 technical reference manual, anyone?
> To: qemu-devel@nongnu.org
> Message-ID:
>         <
> 60490.80.226.245.57.1136396514.squirrel@www.mathematik.uni-marburg.de>
>
> Content-Type: text/plain;charset=iso-8859-1
>
>
> Hi,
>
> does anyone have a copy of the Cirrus Logic GD5446
> technical reference manual (gd5446trm.pdf)?
>
> All copies that were available online seem to have vanished...
>
> Michael
>
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 04 Jan 2006 18:36:38 -0600
> From: "Emphysema U. Contrasts" <wdg@goldsgymsydney.com>
> Subject: [Qemu-devel] Pharmaceutical revolution
> To: Qemu <qemu-devel@nongnu.org>
> Message-ID: <7760043259.20060104183638@goldsgymsydney.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Get Cipnro, Avanrdia, Prodzac and more ONLINE!
>
> Vlagjra - $3.3
> Leyvitra - $3.3
> Cialils - $3.7
> Imzitrex - $16.4
> Flzomax - $2.2
> Ulntram - $0.78
> Viioxx - $4.75
> Amqbien - $2.2
> VaIiupm - $0.97
> Sboma - $3
> Xanzax - $1.09
> Mheridia - $2.2
> If you compare the cost and services of our competitors, you will see that
> we give you much more… for less. Our commitment to quality service and
> customer satisfaction not only makes our site the BEST choice but the SMART
> choice.
>
> *we guarantee 100% top-quality of all products
> * we offer a money-back guarantee in case the product doesn't work for you
> or you may be somehow dissatisfied by its performance
> * we've efficiently streamlined our service, letting you buy from us in a
> very discreet, non-embarrassing and hassle-free manner
>
> Visit our website
> http://greatval.com
>
> dpkllmbvn QFdeQRhVV0VRWXFcXFpSX0cdW0dW
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.gnu.org/pipermail/qemu-devel/attachments/20060104/9fff5f13/attachment.html
>
> ------------------------------
>
> Message: 6
> Date: Wed, 4 Jan 2006 19:44:44 +0100
> From: Mike Kronenberg <mike.kronenberg@kberg.ch>
> Subject: Re: [Qemu-devel] qemu and configuration file?
> To: qemu-devel@nongnu.org
> Message-ID: <CE7F3B09-1285-4FC5-AAC8-518924CF0681@kberg.ch>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> I made a proposal some month ago based on xml:
> http://lists.gnu.org/archive/html/qemu-devel/2005-08/msg00034.html
>
> I use this style of xml property lists for the configuration of the
> vm of Q (slightly alter by now).
> Q is a OS X port of QEMU http://www.kberg.ch/q
>
> I ran recently into some troubles with arguments that can appear
> multiple times, like -net and -redir.
> I'm now about to changes my configuration files. Having a well
> defined style of configuration files would help making simple guest
> packages, that could be used on multiple systems...
>
> Mike
>
> On 04.01.2006, at 06:50, martin wrote:
>
> >  If we'd go for a config file at all with such a complicated
> > structure, i see no reasons why to choose anything else than xml
> > for it. We have tons of xml libs that can be used for gui's (think
> > perl, tk, python etc...). Certainly better every dude writing it's
> > own XuPeRpArSeR that will be broken and compatible after a major
> > change in qemu ...
> >  Another choice would be the pure rc (just 'item = value' lines)
> > without any supersmart blocks.
> >
> > xml style or rc style, please no hack in betweeen :)
> >
> > martin
> >
>
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 4 Jan 2006 13:54:11 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Subject: Re: [Qemu-devel] Problems bringing up network in
>         qemu-system-arm
> To: qemu-devel@nongnu.org
> Message-ID: <20060104185411.GA9361@nevyn.them.org>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, Jan 04, 2006 at 04:56:13PM +0100, Wolfgang Schildbach wrote:
> > Hi everyone,
> >
> > I am using the current CVS (HEAD) version of qemu running on x86 linux,
> > and am using it to emulate an ARM on the integrator board, running
> > arm-linux, using arm-test-0.1.tar.gz.
> >
> > >From what I've read in this list (
> > http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00137.html), it
> > should be possible to set up a network, user-mode or TUN/TAP. However, I
> > fail to see the light as to how to bring the correct interface up on the
> > guest system (arm-linux). ifconfig shows two devices, lo and dummy0, but
> > nothing that would point to a smc91 being detected or used. This is
> > independent from whether I try -net tap or -net user.
> >
> > 1) Is the network/smc91x support finished enough to be useable?
>
> Yes.
>
> > 2) If so, what is the magic bullet? Any boot options that I need to give
> > to the kernel? (BTW, I am calling the emulation as
> >
> > qemu-system-arm -kernel integratorcp.zImage -initrd arm_root.imfg
> > -nographic -net user )
>
> -net nic -net user, or no -net option at all.  You need a network card
> on the VLAN, and also a connection ("user") to the outside.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 4 Jan 2006 18:57:20 +0000
> From: Paul Brook <paul@codesourcery.com>
> Subject: Re: [Qemu-devel] CL-GD5446 technical reference manual,
>         anyone?
> To: qemu-devel@nongnu.org
> Cc: engel@mathematik.uni-marburg.de
> Message-ID: <200601041857.21032.paul@codesourcery.com>
> Content-Type: text/plain;  charset="iso-8859-1"
>
> On Wednesday 04 January 2006 17:41, engel@mathematik.uni-marburg.de wrote:
> > Hi,
> >
> > does anyone have a copy of the Cirrus Logic GD5446
> > technical reference manual (gd5446trm.pdf)?
> >
> > All copies that were available online seem to have vanished...
>
> www.datasheetarchive.com has a copy.
>
> Paul
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 04 Jan 2006 20:19:49 +0100
> From: Pavel@Janik.cz (Pavel Jan?k )
> Subject: [Qemu-devel] [PATCH] Mention --enable-cocoa in --help
> To: qemu-devel@nongnu.org
> Message-ID: <87fyo3ztpm.fsf@Janik.cz>
> Content-Type: text/plain; charset=iso-8859-2
>
> Hi,
>
> --enable-cocoa is not mentioned in configure--help output. Please apply.
>
> --- configure   19 Dec 2005 19:54:10 +0100      1.79
> +++ configure   04 Jan 2006 20:08:47 +0100
> @@ -375,6 +375,7 @@
> echo "  --host-cc=CC             use C compiler CC [$host_cc] for dyngen
> etc."
> echo "  --make=MAKE              use specified make [$make]"
> echo "  --static                 enable static build [$static]"
> +echo "  --enable-cocoa           enable COCOA (Mac OS X only)"
> echo "  --enable-mingw32         enable Win32 cross compilation with
> mingw32"
> echo "  --enable-adlib           enable Adlib emulation"
> echo "  --enable-coreaudio       enable Coreaudio audio driver"
> --
> Pavel Janík
>
> Use self-identifying input.  Allow defaults.  Echo both on output.
>                   -- The Elements of Programming Style (Kernighan &
> Plaugher)
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
> End of Qemu-devel Digest, Vol 34, Issue 8
> *****************************************
>



--
Saludos
José Gerardo González Jiménez

[-- Attachment #2: Type: text/html, Size: 27496 bytes --]