07 May, 2011

1 commit

  • - Documentation/kvm/ to Documentation/virtual/kvm
    - Documentation/uml/ to Documentation/virtual/uml
    - Documentation/lguest/ to Documentation/virtual/lguest
    throughout the kernel source tree.

    Signed-off-by: Rob Landley
    Signed-off-by: Randy Dunlap

    Rob Landley
     

12 Jun, 2009

2 commits

  • Currently, when a Guest wants to perform I/O it calls LHCALL_NOTIFY with
    an address: the main Launcher process returns with this address, and figures
    out what device to run.

    A far nicer model is to let processes bind an eventfd to an address: if we
    find one, we simply signal the eventfd.

    Signed-off-by: Rusty Russell
    Cc: Davide Libenzi

    Rusty Russell
     
  • This version requires that host and guest have the same PAE status.
    NX cap is not offered to the guest, yet.

    Signed-off-by: Matias Zabaljauregui
    Signed-off-by: Rusty Russell

    Matias Zabaljauregui
     

23 Feb, 2009

1 commit

  • Impact: remove unused/broken code

    The Voyager subarch last built successfully on the v2.6.26 kernel
    and has been stale since then and does not build on the v2.6.27,
    v2.6.28 and v2.6.29-rc5 kernels.

    No actual users beyond the maintainer reported this breakage.
    Patches were sent and most of the fixes were accepted but the
    discussion around how to do a few remaining issues cleanly
    fizzled out with no resolution and the code remained broken.

    In the v2.6.30 x86 tree development cycle 32-bit subarch support
    has been reworked and removed - and the Voyager code, beyond the
    build problems already known, needs serious and significant
    changes and probably a rewrite to support it.

    CONFIG_X86_VOYAGER has been marked BROKEN then. The maintainer has
    been notified but no patches have been sent so far to fix it.

    While all other subarchs have been converted to the new scheme,
    voyager is still broken. We'd prefer to receive patches which
    clean up the current situation in a constructive way, but even in
    case of removal there is no obstacle to add that support back
    after the issues have been sorted out in a mutually acceptable
    fashion.

    So remove this inactive code for now.

    Signed-off-by: Ingo Molnar

    Ingo Molnar
     

11 Jul, 2008

1 commit


20 Jan, 2008

1 commit


19 Jan, 2008

1 commit

  • There's currently no way to turn on Lguest guest support; the planned
    Kconfig virtualization reorg didn't get into 2.6.25.

    This was unnoticed because if you already had CONFIG_LGUEST_GUEST=y in
    your config, it worked. Too bad about new users...

    Also, the Kconfig help was wrong now the virtio drivers are merged.

    Signed-off-by: Rusty Russell
    Signed-off-by: Linus Torvalds

    Rusty Russell
     

23 Oct, 2007

3 commits


24 Aug, 2007

1 commit


07 Aug, 2007

1 commit

  • Lguest drivers need to default to "Y" otherwise they're never selected
    for new builds. (We don't bother prompting, because they're less than
    4k combined, and implied by selecting lguest support).

    Signed-off-by: Rusty Russell
    Signed-off-by: Linus Torvalds

    Rusty Russell
     

30 Jul, 2007

1 commit


20 Jul, 2007

1 commit