public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Andrew Morton <akpm@osdl.org>, Dan Hecht <dhecht@vmware.com>,
	Dan Arai <arai@vmware.com>, Anne Holler <anne@vmware.com>,
	Pratap Subrahmanyam <pratap@vmware.com>,
	Christopher Li <chrisl@vmware.com>,
	Joshua LeVasseur <jtl@ira.uka.de>, Rik Van Riel <riel@redhat.com>,
	Jyothy Reddy <jreddy@vmware.com>, Jack Lo <jlo@vmware.com>,
	Kip Macy <kmacy@fsmware.com>, Jan Beulich <jbeulich@novell.com>,
	Ky Srinivasan <ksrinivasan@novell.com>,
	Wim Coekaerts <wim.coekaerts@oracle.com>,
	Leendert van Doorn <leendert@watson.ibm.com>,
	Gerd Hoffmann <kraxel@suse.de>
Subject: Re: [RFC, PATCH 7/24] i386 Vmi memory hole
Date: Tue, 14 Mar 2006 14:35:59 -0800	[thread overview]
Message-ID: <4417454F.2080908@vmware.com> (raw)
In-Reply-To: <20060314215616.GM12807@sorel.sous-sol.org>

Chris Wright wrote:
> * Zachary Amsden (zach@vmware.com) wrote:
>   
>> Allow creation of an compile time hole at the top of linear address space.
>>
>> Extended to allow a dynamic hole in linear address space, 7/2005.  This
>> required some serious hacking to get everything perfect, but the end result
>> appears to function quite nicely.  Everyone can now share the appreciation
>> of pseudo-undocumented ELF OS fields, which means core dumps, debuggers
>> and even broken or obsolete linkers may continue to work.
>>     
>
> Thanks.  Gerd did something similar (although I believe it's simpler,
> don't recall the relocation magic) for Xen.  Either way, it's useful
> from Xen perspective.
>   

I believe Xen disables sysenter.  The complications in my patch come 
from the fact that the vsyscall page has to be relocated dynamically, 
requiring, basically run time linking on the page and some tweaks to get 
sysenter to work.  If you don't use vsyscall (say, non-TLS glibc), then 
you don't need that complexity.  But I think it might be needed now, 
even for Xen.

Zach

  reply	other threads:[~2006-03-14 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 18:04 [RFC, PATCH 7/24] i386 Vmi memory hole Zachary Amsden
2006-03-14  6:41 ` Chris Wright
2006-03-14  7:14   ` Zachary Amsden
2006-03-14 21:56     ` Chris Wright
2006-03-14 22:35       ` Zachary Amsden [this message]
2006-03-15  4:31         ` Chris Wright
2006-03-15  8:27           ` Gerd Hoffmann
2006-03-15  8:36             ` Zachary Amsden
2006-03-15  9:09               ` Chris Wright
2006-03-15  9:18                 ` Zachary Amsden
2006-03-15  9:41                   ` Chris Wright
2006-03-15  9:27               ` Gerd Hoffmann
2006-03-15  9:37                 ` Zachary Amsden

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=4417454F.2080908@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@osdl.org \
    --cc=anne@vmware.com \
    --cc=arai@vmware.com \
    --cc=chrisl@vmware.com \
    --cc=chrisw@sous-sol.org \
    --cc=dhecht@vmware.com \
    --cc=jbeulich@novell.com \
    --cc=jlo@vmware.com \
    --cc=jreddy@vmware.com \
    --cc=jtl@ira.uka.de \
    --cc=kmacy@fsmware.com \
    --cc=kraxel@suse.de \
    --cc=ksrinivasan@novell.com \
    --cc=leendert@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap@vmware.com \
    --cc=riel@redhat.com \
    --cc=torvalds@osdl.org \
    --cc=virtualization@lists.osdl.org \
    --cc=wim.coekaerts@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox