From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Fri, 09 Feb 2007 18:20:57 +1100 [thread overview]
Message-ID: <1171005657.2718.19.camel@localhost.localdomain> (raw)
In-Reply-To: <45CC1BCA.8060003@vmware.com>
On Thu, 2007-02-08 at 22:59 -0800, Zachary Amsden wrote:
> I believe there was a patch that got applied that turned it off by
> default if CONFIG_PARAVIRT was enabled. Doing it the cpuid way is the
> right solution, IMHO.
Ah, yes, the VDSO issue. This is separate, and does need fixing.
Basically, if the user doesn't select COMPAT_VDSO, we don't have a
problem. Currently they don't get offered COMPAT_VDSO if PARAVIRT is
enabled, but we *still* disable vdso in that case (unless vdso=1 is on
cmdline).
I think the best choice is to rework COMPAT_VDSO to a general "support
old glibcs" option, which will either (1) map it fixed if !
CONFIG_PARAVIRT, or (2) disable it if CONFIG_PARAVIRT.
I'll send that soon...
Cheers,
Rusty.
next prev parent reply other threads:[~2007-02-09 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Paravirt-ops VMI / Xen / lrustyvisor merge status Zachary Amsden
2007-02-09 5:54 ` Rusty Russell
2007-02-09 6:12 ` Zachary Amsden
2007-02-09 6:24 ` Jeremy Fitzhardinge
2007-02-09 6:58 ` Zachary Amsden
2007-02-09 6:44 ` Rusty Russell
2007-02-09 6:57 ` Jeremy Fitzhardinge
2007-02-09 6:59 ` Zachary Amsden
2007-02-09 7:06 ` Jeremy Fitzhardinge
2007-02-09 7:20 ` Rusty Russell [this message]
2007-02-09 7:35 ` Andi Kleen
2007-02-09 8:46 ` Rusty Russell
2007-02-09 6:10 ` Jeremy Fitzhardinge
2007-02-09 7:21 ` Andi Kleen
2007-02-09 7:35 ` 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=1171005657.2718.19.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.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).