virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Fix VMI and COMPAT_VDSO for 2.6.21
Date: Sat, 10 Mar 2007 09:47:50 +0100	[thread overview]
Message-ID: <20070310084750.GA15647@elte.hu> (raw)
In-Reply-To: <45F257C1.4070904@vmware.com>


* Zachary Amsden <zach@vmware.com> wrote:

> Zachary Amsden wrote:
> >VMI is broken under COMPAT_VDSO, as Xen and other non hardware 
> >assisted hypervisors will be.  I have been working on a fix for this 
> >which works for older glibcs that panic when the new relocatable VDSO 
> >is used.  However, I believe at this time that the fix is going to be 
> >too radical to consider at this stage in the release of 2.6.21.  We 
> >don't expect this config option to be turned on by vendors for new 
> >distributions, so at this point we are willing to drop support for it 
> >when VMI is compiled in, and work on a patch for 2.6.22 which more 
> >fully addresses the problem.
> >
> >Please apply, thanks.

makes sense. We can do Jan's relocatable-COMPAT_VDSO thing in v2.6.22, 
but for v2.6.21 that's way too intrusive.

Acked-by: Ingo Molnar <mingo@elte.hu>

> I suppose it would be better if I attached the patch.

it certainly helps ;-)

	Ingo

  reply	other threads:[~2007-03-10  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10  7:00 PATCH: Fix VMI and COMPAT_VDSO for 2.6.21 Zachary Amsden
2007-03-10  7:01 ` Zachary Amsden
2007-03-10  8:47   ` Ingo Molnar [this message]
2007-03-10 10:32     ` 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=20070310084750.GA15647@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).