similar to: [ANNOUNCE] Lguest64 - fatter puppies!

Displaying 20 results from an estimated 1000 matches similar to: "[ANNOUNCE] Lguest64 - fatter puppies!"

2007 Dec 20
5
[PATCH 0/16] lguest: introduce vcpu structure
this patch makes room for the vcpu structure in lguest, already used in this very same way at lguest64. It's the first part of our plan to have lguest and lguest64 unified too. When two dogs hang out, you don't have new puppies right in the other day. Some time has to be elapsed. They have to grow first. In this same spirit, having these patches _do not_ mean smp guests can be launched
2007 Dec 20
5
[PATCH 0/16] lguest: introduce vcpu structure
this patch makes room for the vcpu structure in lguest, already used in this very same way at lguest64. It's the first part of our plan to have lguest and lguest64 unified too. When two dogs hang out, you don't have new puppies right in the other day. Some time has to be elapsed. They have to grow first. In this same spirit, having these patches _do not_ mean smp guests can be launched
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 06/13] lguest64 Kconfig
plain text document attachment (lguest64-kconfig.patch) Put the kconfig options for lguest64 in. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index: work-pv/arch/x86_64/Kconfig =================================================================== ---
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 06/13] lguest64 Kconfig
plain text document attachment (lguest64-kconfig.patch) Put the kconfig options for lguest64 in. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index: work-pv/arch/x86_64/Kconfig =================================================================== ---
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 08/13] lguest64 user header.
plain text document attachment (lguest64-user.patch) This patch adds the header used by the lguest64 loader. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index: work-pv/include/asm-x86_64/lguest_user.h ===================================================================
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 08/13] lguest64 user header.
plain text document attachment (lguest64-user.patch) This patch adds the header used by the lguest64 loader. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index: work-pv/include/asm-x86_64/lguest_user.h ===================================================================
2008 May 23
1
kvm-lite, lguest64: status?
Hi, Just a quick question: What is the status of the two projects in $subject? Havn't heared anything for a while for both ... cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/
2008 May 23
1
kvm-lite, lguest64: status?
Hi, Just a quick question: What is the status of the two projects in $subject? Havn't heared anything for a while for both ... cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 00/13] Lguest for the x86_64
Hi all! Lately, Glauber and I have been working on getting both paravirt_ops and lguest running on the x86_64. I already pushed the x86_64 patches and as promised, I'm pushing now the lguest64 patches. This patches are greatly influenced by Rusty Russell, and we tried to stay somewhat consistent with his work on the i386. But there are some major differences that we had to over come.
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 00/13] Lguest for the x86_64
Hi all! Lately, Glauber and I have been working on getting both paravirt_ops and lguest running on the x86_64. I already pushed the x86_64 patches and as promised, I'm pushing now the lguest64 patches. This patches are greatly influenced by Rusty Russell, and we tried to stay somewhat consistent with his work on the i386. But there are some major differences that we had to over come.
2007 Apr 18
1
[RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64
Hi all, Glauber and I have been playing around with getting paravirt ops working on the x86_64. We have our own version of lguest running there too. We have lguest64 running up to console_init, and then it takes an interrupt storm. I'll be posting those patches tomorrow. Glauber and I have been sharing a git repo that isn't open to the public. (we don't want people to see how
2007 Apr 18
1
[RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64
Hi all, Glauber and I have been playing around with getting paravirt ops working on the x86_64. We have our own version of lguest running there too. We have lguest64 running up to console_init, and then it takes an interrupt storm. I'll be posting those patches tomorrow. Glauber and I have been sharing a git repo that isn't open to the public. (we don't want people to see how
2007 Apr 18
1
[PATCH] Lguest32 print hex on bad reads and writes
Currently the lguest32 error messages from bad reads and writes prints a decimal integer for addresses. This is pretty annoying. So this patch changes those to be hex outputs. This is applied on top of my debug patch. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Index: linux-2.6.21-rc5-mm2/drivers/lguest/core.c =================================================================== ---
2007 Apr 18
1
[PATCH] Lguest32 print hex on bad reads and writes
Currently the lguest32 error messages from bad reads and writes prints a decimal integer for addresses. This is pretty annoying. So this patch changes those to be hex outputs. This is applied on top of my debug patch. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Index: linux-2.6.21-rc5-mm2/drivers/lguest/core.c =================================================================== ---
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]
2007 Apr 18
1
[PATCH] lguest32 kallsyms backtrace of guest.
This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 09/13] lguest64 devices
plain text document attachment (lguest64-device.patch) We started working a little bit on the devices for lguest64. This is still very much a work-in-progress and needs much more work. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index:
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 09/13] lguest64 devices
plain text document attachment (lguest64-device.patch) We started working a little bit on the devices for lguest64. This is still very much a work-in-progress and needs much more work. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Glauber de Oliveira Costa <glommer@gmail.com> Cc: Chris Wright <chrisw@sous-sol.org> Index:
2007 May 09
2
[patch 5/9] lguest: the Makefile and Kconfig
From: Rusty Russell <rusty@rustcorp.com.au> This is the Kconfig and Makefile to allow lguest to actually be compiled. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/Kconfig | 2 ++ drivers/Makefile | 1 + drivers/lguest/Kconfig | 20
2009 Mar 12
1
Cross-validation -> lift curve
Hi all, I'd like to do cross-validation on lm and get the resulting lift curve/table (or, alternatively, the estimates on 100% of my data with which I can get lift). If such a thing doesn't exist, could it be derived using cv.lm, or would we need to start from scratch? Thanks! -- Eric Siegel, Ph.D. President Prediction Impact, Inc. Predictive Analytics World Conference More info: