All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Mark Hurenkamp <Mark.Hurenkamp@xs4all.nl>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: 2.4.26-xen0 unresolved symbol _mmx_memcpy in USB modules
Date: Wed, 25 Aug 2004 01:17:11 -0700	[thread overview]
Message-ID: <412C4B07.9090403@vmware.com> (raw)
In-Reply-To: <35595.161.85.127.139.1093351536.squirrel@hoth.xs4all.nl>

In general, modules for different processors or subarchitectures are not 
cross compatible.  Modules compiled for Athlon will use MMX instructions 
to do fast memcopy, but a kernel compiled for Pentium II does not export 
the _mmx_memcpy symbol for modules to use - not because it's not 
supported, but because it's just not as fast on Pentium II.  You should 
be able to use modules which are a strict ancestor of the current kernel 
architecture without problems - i.e. a 386 module in a Pentium II kernel 
should not cause grief.  YMMV.  I highly recommend using modules 
compiled for the same kernel configuration, however.

Cheers,
Zach

Mark Hurenkamp wrote:

>Hi,
>
>I've been playing with the 2.4.26 and 2.4.27 xen0 kernels, and at some
>point I noticed that I was unable to load the USB modules anymore because
>of an unresolved _mmx_memcpy symbol...A bit of fiddling with my settings showed that when I build all my USB
>modules in the kernel, the problem goes away, or alternately, if I switch
>back from Athlon to Pentium II cpu (which was my original setting).
>So for now I'm using the Pentium II as my CPU selection, but I was just
>wondering if this is a known problem, or if I stumbled across something
>new :-) ?
>Warm regards,
>Mark.
>
>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
>100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
>Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
>http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>  
>



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  parent reply	other threads:[~2004-08-25  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 12:45 2.4.26-xen0 unresolved symbol _mmx_memcpy in USB modules Mark Hurenkamp
2004-08-25  8:16 ` Ian Pratt
2004-08-25  8:17 ` Zachary Amsden [this message]
2004-08-25  8:47 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=412C4B07.9090403@vmware.com \
    --to=zach@vmware.com \
    --cc=Mark.Hurenkamp@xs4all.nl \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.