All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Paul Wagland <paul@wagland.net>
Cc: Hugo Mills <hugo-lkml@carfax.org.uk>,
	"J. Ryan Earl" <heretic@clanhk.org>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@muc.de>
Subject: Re: amd64 questions
Date: Sun, 11 Apr 2004 12:45:57 +0100	[thread overview]
Message-ID: <20040411114557.GB22258@selene> (raw)
In-Reply-To: <A716F1DA-8BAC-11D8-A41D-000A95CD704C@wagland.net>

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

On Sun, Apr 11, 2004 at 01:37:46PM +0200, Paul Wagland wrote:
> 
> On Apr 10, 2004, at 21:02, Hugo Mills wrote:
> 
> >On Sat, Apr 10, 2004 at 08:49:04PM +0200, Andi Kleen wrote:
> >>>line either?  Or we can if we use AMD64 [DM] libraries with a AMD64
> >>>kernel?  DM = Device Mapper right?
> >>
> >>You can't use Device Mapper with 32bit user tools on a 64bit kernel
> >>right now.
> >
> >   Well, you can, because that's what I'm doing on this machine. Joe
> >Thornber posted a patch[1] here a few weeks ago which fixes the
> >problem in a "sealing-wax-and-string" kind of way. It Works For
> >Me(tm), which is about all you can say about it -- it's not the
> >prettiest piece of code, even to my non-kernel eyes. :)
> 
> Ah, yes, but you missed the bit slightly later in the thread where Andi 
> requested that this not be added to the kernel since it would then 
> break all currently existing 64bit DM user tools. Newly compiled ones 
> would, of course, work, but you introduce a DM user tool versioning 
> problem, where the old 64 bit utils need to be used with old kernels, 
> and the new tools need to be used with the new kernels. As far as I 
> understood, this is the "official" line for the mainstream kernel. It 
> is my hope that the disties all decide to use Thornbers patch when they 
> do release, but only time will tell...

   Sorry, I probably wasn't making myself clear.

   I'm well aware of the issues surrounding this patch, and the fact
that it's never going to get into mainline kernels. However, it _does_
allow you to use DM with 32-bit user-space + 64-bit kernel, which was
my only point.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
   --- The English language has the mot juste for every occasion. ---    

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-11 11:48 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
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 [this message]
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=20040411114557.GB22258@selene \
    --to=hugo-lkml@carfax.org.uk \
    --cc=ak@muc.de \
    --cc=heretic@clanhk.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@wagland.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.