Why disable vdso by default with CONFIG_PARAVIRT?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Why disable vdso by default with CONFIG_PARAVIRT?
From: jeremy at goop.org (Jeremy Fitzhardinge)
Date: Mon, 11 Dec 2006 17:49:34 -0800
In-reply-to: <457E0A03.3020704@xxxxxxxxxx>

Zachary Amsden wrote:
> It's not for us or Xen.  Perhaps it came from lhype?  

(I suspect it came from Andi's fevered brain.)  If lhype can't deal with
vdso, it can turn it off for itself - but I don't think its a problem
for lhype.

    J

References:
- Why disable vdso by default with CONFIG_PARAVIRT?
  - From: Jeremy Fitzhardinge
- Why disable vdso by default with CONFIG_PARAVIRT?
  - From: Zachary Amsden
- Why disable vdso by default with CONFIG_PARAVIRT?
  - From: Jeremy Fitzhardinge
- Why disable vdso by default with CONFIG_PARAVIRT?
  - From: Zachary Amsden

Prev by Date: Why disable vdso by default with CONFIG_PARAVIRT?
Next by Date: Why disable vdso by default with CONFIG_PARAVIRT?
Previous by thread: Why disable vdso by default with CONFIG_PARAVIRT?
Next by thread: Why disable vdso by default with CONFIG_PARAVIRT?
Index(es):
- Date
- Thread

[Index of Archives] [KVM Development] [Libvirt Development] [Libvirt Users] [CentOS Virtualization] [Netdev] [Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]

Powered by Linux