search for: lstar

...############################# # COMPUTING THE LOGLIKELIHOOD # USING NUMERICAL INTEGRALS ############################# LLK <- function(alpha, y) { n <- length(y) lglik <- numeric(n) # TO BE SUMMED LATER TO GET THE LOGLIKELIHOOD lambda <- numeric(n-1) # GENERATING *lstar* for (i in 1:(n-1)) { # TO USE IN THE lambda[i] <- y[i+1]/y[i] # RE-PARAMETRIZATION BELOW } lstar <- (min(lambda)-0.01) # NOTE RE-PARAMETRIZATION # THESE RESTRICTIONS EMERGE FROM THE MODEL muep <- alpha[1]...

Hi, I''m trying to use the SYSCALL/SYSRET opcodes with a minios kernel without much success. Going by the manuals (and linux sources) I first have to setup the STAR and LSTAR registers to define the segment and instruction pointer to be used for SYSCALL: /* * LSTAR and STAR live in a bit strange symbiosis. * They both write to the same internal register. STAR allows to set * CS/DS but only a 32bit target. LSTAR sets the 64bit rip....

Hi, I implemented my own Hypercall in xen. Now I wish my application under dom0 could talk to Xen via my hypercall. Currently, I make a stub in dom0''s kernel, which works as a proxy to forward the request. So, my application first makes a system call to dom0, which then makes hypercall to xen. Is this design necessary? May I call hypercalls from user application under dom0 directly?

...nt_arch arch; + } + +On x86 the structure looks like this:: + + struct kvmi_event_arch { + __u8 mode; + __u8 padding[7]; + struct kvm_regs regs; + struct kvm_sregs sregs; + struct { + __u64 sysenter_cs; + __u64 sysenter_esp; + __u64 sysenter_eip; + __u64 efer; + __u64 star; + __u64 lstar; + __u64 cstar; + __u64 pat; + __u64 shadow_gs; + } msrs; + }; + +It contains information about the vCPU state at the time of the event. + +The reply to events have the *KVMI_EVENT_REPLY* message id and begins +with two common structures:: + + struct kvmi_vcpu_hdr; + struct kvmi_event_reply...

...(u64)pda); mb(); pda->cpunumber = cpu; @@ -152,7 +152,7 @@ char boot_exception_stacks[(N_EXCEPTION_ __attribute__((section(".bss.page_aligned"))); /* May not be marked __init: used by software suspend */ -void syscall_init(void) +void x86_64_syscall_init(void) { /* * LSTAR and STAR live in a bit strange symbiosis. @@ -160,7 +160,7 @@ void syscall_init(void) * but only a 32bit target. LSTAR sets the 64bit rip. */ wrmsrl(MSR_STAR, ((u64)__USER32_CS)<<48 | ((u64)__KERNEL_CS)<<32); - wrmsrl(MSR_LSTAR, system_call); + wrmsrl(MSR_LSTAR, (u64)sys...

...(u64)pda); mb(); pda->cpunumber = cpu; @@ -152,7 +152,7 @@ char boot_exception_stacks[(N_EXCEPTION_ __attribute__((section(".bss.page_aligned"))); /* May not be marked __init: used by software suspend */ -void syscall_init(void) +void x86_64_syscall_init(void) { /* * LSTAR and STAR live in a bit strange symbiosis. @@ -160,7 +160,7 @@ void syscall_init(void) * but only a 32bit target. LSTAR sets the 64bit rip. */ wrmsrl(MSR_STAR, ((u64)__USER32_CS)<<48 | ((u64)__KERNEL_CS)<<32); - wrmsrl(MSR_LSTAR, system_call); + wrmsrl(MSR_LSTAR, (u64)sys...

...nt_arch arch; + } + +On x86 the structure looks like this:: + + struct kvmi_event_arch { + __u8 mode; + __u8 padding[7]; + struct kvm_regs regs; + struct kvm_sregs sregs; + struct { + __u64 sysenter_cs; + __u64 sysenter_esp; + __u64 sysenter_eip; + __u64 efer; + __u64 star; + __u64 lstar; + __u64 cstar; + __u64 pat; + __u64 shadow_gs; + } msrs; + }; + +It contains information about the vCPU state at the time of the event. + +Specific data can follow these common structures. + +1. KVMI_EVENT_UNHOOK +-------------------- + +:Architecture: all +:Versions: >= 1 +:Actions: non...

...), with online help and examples (thanks to Gianluca Gazzola). tsDyn is a package for nonlinear time series modelling. At this point the package focuses on Nonlinear Autoregressive Models, often indicated as NLAR (as a major reference, see Tong (1990)). Currently available are threshold (SETAR and LSTAR), neural networks (NNET), and additive autoregressive (AAR) models. An experimental cross-platform tcltk GUI is included for model selection. Explorative and diagnostic tools are also available. A vignette is included for a clearer presentation of the package contents. Comments and suggestions app...

...), with online help and examples (thanks to Gianluca Gazzola). tsDyn is a package for nonlinear time series modelling. At this point the package focuses on Nonlinear Autoregressive Models, often indicated as NLAR (as a major reference, see Tong (1990)). Currently available are threshold (SETAR and LSTAR), neural networks (NNET), and additive autoregressive (AAR) models. An experimental cross-platform tcltk GUI is included for model selection. Explorative and diagnostic tools are also available. A vignette is included for a clearer presentation of the package contents. Comments and suggestions app...

...0.7 of package tsDyn presented at useR! 2009 is now on CRAN, extended with several new features. The package tsDyn is aimed at estimating nonlinear time series models which exhibit regime specific properties. The regime switching dynamics can either be described by smooth transition (STAR and LSTAR) or threshold effects (SETAR). The package furthermore offers nonlinear models such as neural networks (NNET), and additive autoregressive (AAR) models. The version 0.7 enhances the functionalities for the threshold autoregression models (SETAR) by extending the estimation techniques, providi...

...0.7 of package tsDyn presented at useR! 2009 is now on CRAN, extended with several new features. The package tsDyn is aimed at estimating nonlinear time series models which exhibit regime specific properties. The regime switching dynamics can either be described by smooth transition (STAR and LSTAR) or threshold effects (SETAR). The package furthermore offers nonlinear models such as neural networks (NNET), and additive autoregressive (AAR) models. The version 0.7 enhances the functionalities for the threshold autoregression models (SETAR) by extending the estimation techniques, providi...

...nt_arch arch; + } + +On x86 the structure looks like this:: + + struct kvmi_event_arch { + __u8 mode; + __u8 padding[7]; + struct kvm_regs regs; + struct kvm_sregs sregs; + struct { + __u64 sysenter_cs; + __u64 sysenter_esp; + __u64 sysenter_eip; + __u64 efer; + __u64 star; + __u64 lstar; + __u64 cstar; + __u64 pat; + __u64 shadow_gs; + } msrs; + }; + +It contains information about the vCPU state at the time of the event. + +Specific event data can follow these common structures. + +1. KVMI_EVENT_UNHOOK +-------------------- + +:Architecture: all +:Versions: >= 1 +:Action...

*Hi all, I got problems installing RSTAR, MSVAR, and MSVECM packages. * > install.packages("RSTAR")Installing package(s) into ‘C:/Program Files/R/R-2.15.1/library’ (as ‘lib’ is unspecified)Warning in install.packages : package ‘RSTAR’ is not available (for R version 2.15.1) > install.packages("MSVAR") Installing package(s) into ‘C:/Program Files/R/R-2.15.1/library’

...R_IA32_SYSENTER_ESP, &ev->msrs.sysenter_esp, + true); + __kvm_get_msr(vcpu, MSR_IA32_SYSENTER_EIP, &ev->msrs.sysenter_eip, + true); + __kvm_get_msr(vcpu, MSR_EFER, &ev->msrs.efer, true); + __kvm_get_msr(vcpu, MSR_STAR, &ev->msrs.star, true); + __kvm_get_msr(vcpu, MSR_LSTAR, &ev->msrs.lstar, true); + __kvm_get_msr(vcpu, MSR_CSTAR, &ev->msrs.cstar, true); + __kvm_get_msr(vcpu, MSR_IA32_CR_PAT, &ev->msrs.pat, true); + __kvm_get_msr(vcpu, MSR_KERNEL_GS_BASE, &ev->msrs.shadow_gs, true); +} + +void kvmi_arch_setup_event(struct kvm_vcpu *vcpu, st...

Here is an slightly updated version of the paravirt_ops patch. If your comments and criticism were welcome before, now it's even more! There are some issues that are _not_ addressed in this revision, and here are the causes: * split debugreg into multiple functions, suggested by Andi: - Me and jsfg agree that introducing more pvops (specially 14!) is not worthwhile. So, although we do

Here is an slightly updated version of the paravirt_ops patch. If your comments and criticism were welcome before, now it's even more! There are some issues that are _not_ addressed in this revision, and here are the causes: * split debugreg into multiple functions, suggested by Andi: - Me and jsfg agree that introducing more pvops (specially 14!) is not worthwhile. So, although we do

This is hopefully the last iteration of the pvops64 patch. >From the last version, we have only one change, which is include/asm-x86_64/processor.h: There were still one survivor in raw asm. Also, git screwed me up for some reason, and the 25th patch was missing the new files, paravirt.{c,h}. (although I do remember having git-add'ed it, but who knows...) Andrew, could you please push it

This is hopefully the last iteration of the pvops64 patch. >From the last version, we have only one change, which is include/asm-x86_64/processor.h: There were still one survivor in raw asm. Also, git screwed me up for some reason, and the 25th patch was missing the new files, paravirt.{c,h}. (although I do remember having git-add'ed it, but who knows...) Andrew, could you please push it

Hi folks, After some time away from it, and a big rebase as a consequence, here is the updated version of paravirt_ops for x86_64, heading to inclusion. Your criticism is of course, very welcome. Have fun -- arch/x86_64/Kconfig | 11 arch/x86_64/ia32/syscall32.c | 2 arch/x86_64/kernel/Makefile | 1 arch/x86_64/kernel/apic.c | 2

Hi folks, After some time away from it, and a big rebase as a consequence, here is the updated version of paravirt_ops for x86_64, heading to inclusion. Your criticism is of course, very welcome. Have fun -- arch/x86_64/Kconfig | 11 arch/x86_64/ia32/syscall32.c | 2 arch/x86_64/kernel/Makefile | 1 arch/x86_64/kernel/apic.c | 2