MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Roland McGrath <roland@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Various x86 syscall mechanisms
In-Reply-To: Jeremy Fitzhardinge's message of  Friday, 27 June 2008 14:45:16 -0700 <48655F6C.7000409@goop.org>
References: <485C2875.2050204@goop.org>
	<20080627204954.166D0154077@magilla.localdomain>
	<48655F6C.7000409@goop.org>
Message-Id: <20080627215248.6E9C6154058@magilla.localdomain>
Date: Fri, 27 Jun 2008 14:52:48 -0700 (PDT)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 888
Lines: 24

> > [...] "int $0x80" for 32-bit
> > syscalls made from 64-bit tasks on CONFIG_IA32_EMULATION kernels (intended
> > for valgrind).
> 
> Hm, I think that's a post-facto rationalization.  

It was my recollection of something Andi had said about why it was there.
My recollections are not a reliable source of accurate information.

> Thanks for the clarifying overview.  I've been piecing my understanding 
> together as I've been getting 64-bit pvops Xen working, and trying to 
> fit what it has to do to implement all these instructions and mode 
> combinations, and it looks like I'm about right.

I'm always glad to help.


Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/