All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why disable vdso by default with CONFIG_PARAVIRT?
Date: Mon, 11 Dec 2006 17:42:22 -0800	[thread overview]
Message-ID: <457E08FE.6050600@vmware.com> (raw)
In-Reply-To: <457E0460.4030107@goop.org>

Jeremy Fitzhardinge wrote:
> Hi Andi,
>
> What problem do they cause together?  There's certainly no problem with
> Xen+vdso (in fact, its actually very useful so that it picks up the
> right libc with Xen-friendly TLS).
>   

Methinks the compat VDSO support got broken in the config?  Paravirt + 
COMPAT_VDSO are incompatible.

  reply	other threads:[~2006-12-12  1:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  1:22 Why disable vdso by default with CONFIG_PARAVIRT? Jeremy Fitzhardinge
2006-12-12  1:42 ` Zachary Amsden [this message]
2006-12-12  1:44   ` Jeremy Fitzhardinge
2006-12-12  1:46     ` Zachary Amsden
2006-12-12  1:49       ` Jeremy Fitzhardinge
2006-12-12  3:02 ` Andi Kleen
2006-12-12  6:28   ` Zachary Amsden
2006-12-12  6:50   ` Jeremy Fitzhardinge
2006-12-12  7:27     ` Andi Kleen
2006-12-12 10:23       ` Jeremy Fitzhardinge
2006-12-12 12:01         ` Andi Kleen
2006-12-12 20:11           ` Jeremy Fitzhardinge
2006-12-12 21:15             ` Andi Kleen
2006-12-13  2:04               ` Rusty Russell
2006-12-13  4:36               ` Rusty Russell
2006-12-13  5:25                 ` Rusty Russell
2006-12-12 23:22   ` Rusty Russell

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=457E08FE.6050600@vmware.com \
    --to=zach@vmware.com \
    --cc=ak@suse.de \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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.