Re: Why disable vdso by default with CONFIG_PARAVIRT?

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Why disable vdso by default with CONFIG_PARAVIRT?
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Why disable vdso by default with CONFIG_PARAVIRT?
    • From: Zachary Amsden <[email protected]>
  • Re: Why disable vdso by default with CONFIG_PARAVIRT?
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Why disable vdso by default with CONFIG_PARAVIRT?
    • From: Zachary Amsden <[email protected]>

• Prev by Date: Re: Why disable vdso by default with CONFIG_PARAVIRT?
• Next by Date: Re: [PATCH] connector: Some fixes for ia64 unaligned access errors
• Previous by thread: Re: Why disable vdso by default with CONFIG_PARAVIRT?
• Next by thread: [PATCH][SCSI]: Save some bytes in struct scsi_target
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]