From: "J. Ryan Earl" <heretic@clanhk.org>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd64 questions
Date: Sat, 10 Apr 2004 11:54:55 -0500 [thread overview]
Message-ID: <407826DF.9030506@clanhk.org> (raw)
In-Reply-To: <m3isgb69xx.fsf@averell.firstfloor.org>
Andi Kleen wrote:
>It is a subsystem bug really. These subsystems were all designed to
>not require emulation, but the designers weren't aware of all the
>requirements for this and broke it for AMD64/IA64. Unfortunately the
>interfaces were done in a way that it would be very complicated and a
>lot of work to write an emulation layer, because they're extremly
>emulation unfriendly. Maybe it would be still possible to write an
>emulation layer, but easier is it to just use static 64bit executables
>or hacked 32bit executables.
>
>I don't have any plans to write emulation layers for such hopeless
>cases on my own, but just declared these subsystems as broken.
>
>
So let me get this straight, we can't use LVM with AMD64 under the 2.6
line either? Or we can if we use AMD64 [DM] libraries with a AMD64
kernel? DM = Device Mapper right?
-ryan
next prev parent reply other threads:[~2004-04-10 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1Ijzw-4ff-5@gated-at.bofh.it>
[not found] ` <1Ijzv-4ff-3@gated-at.bofh.it>
[not found] ` <1IntE-7wn-39@gated-at.bofh.it>
2004-04-07 16:15 ` amd64 questions Andi Kleen
2004-04-07 16:49 ` Chris Friesen
2004-04-07 18:08 ` Andi Kleen
2004-04-10 16:54 ` J. Ryan Earl [this message]
2004-04-10 18:49 ` Andi Kleen
2004-04-10 19:02 ` Hugo Mills
2004-04-11 11:37 ` Paul Wagland
2004-04-11 11:45 ` Hugo Mills
2004-04-10 20:01 ` J. Ryan Earl
[not found] <1I8up-46J-3@gated-at.bofh.it>
2004-04-07 11:29 ` Andi Kleen
2004-04-07 15:24 ` Paul Wagland
2004-04-07 17:36 ` Bryan Koschmann - GKT
2004-04-06 23:37 Bryan Koschmann - GKT
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=407826DF.9030506@clanhk.org \
--to=heretic@clanhk.org \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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.