search for: cfunc

Hello, This is a question that probably reveals my lack of understanding. In a C function (call it cfunc), i created a SEXP, called S, and then called R_PreserveObject on S. I returned the SEXP to the calling R function (call it rfunc). Note, I didn't call R_ReleaseObject on S. v <- .Call("cfunc") So, are the following statements correct 1. S is 'doubly' protected from t...

Hi, I am getting this error when i execute rake db:create:all /opt/gitorious/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:569: [BUG] unknown type 0x22 (0xc given) any clues ? -Manish -- Posted via http://www.ruby-forum.com/.

Apologies, I am resending this because my emails seem to go in HTML form. Hello, This is a question that probably reveals my lack of understanding. In a C function (call it cfunc), i created a SEXP, called S, and then called R_PreserveObject on S. I returned the SEXP to the calling R function (call it rfunc). Note, I didn't call R_ReleaseObject on S. v <- .Call("cfunc") So, are the following statements correct 1. S is 'doubly' protected from t...

Apologies, I am resending this because my emails seem to go in HTML form. (I haven't as yet figured gmail web interface) Hello, This is a question that probably reveals my lack of understanding. In a C function (call it cfunc), i created a SEXP, called S, and then called R_PreserveObject on S. I returned the SEXP to the calling R function (call it rfunc). Note, I didn't call R_ReleaseObject on S. v <- .Call("cfunc") So, are the following statements correct 1. S is 'doubly' protected from t...

.../* pt_regs->ss */ pushq PER_CPU_VAR(cpu_tss_rw + TSS_sp2) /* pt_regs->sp */ @@ -446,6 +448,82 @@ _ASM_NOKPROBE(\asmsym) SYM_CODE_END(\asmsym) .endm +/** + * idtentry_vc - Macro to generate entry stub for #VC + * @vector: Vector number + * @asmsym: ASM symbol for the entry point + * @cfunc: C function to be called + * + * The macro emits code to set up the kernel context for #VC. The #VC handler + * runs on an IST stack and needs to be able to cause nested #VC exceptions. + * + * To make this work the #VC entry code tries its best to pretend it doesn't use + * an IST stack by sw...

.../lib/ruby1.9/lib/ruby/gems/1.9.0/gems/wxruby-1.9.7-x86-linux/lib/wxruby2.so: [BUG] unknown type 0x22 (0x12 given) ruby 1.9.0 (2007-12-25 revision 14709) [i686-linux] -- control frame ---------- c:0008 p:-34008570 s:0021 b:0021 l:000020 d:000020 TOP c:0007 p:---- s:0019 b:0019 l:000018 d:000018 CFUNC :require c:0006 p:0009 s:0015 b:0015 l:000014 d:000014 TOP /usr/lib/ruby1.9/lib/ruby/gems/1.9.0/gems/wxruby-1.9.7-x86-linux/lib/wx.rb:12 c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH :class_eval c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :require c:0003 p:0020 s:0006 b:0006 l:0...

.../Applications/Ruby/lib/ruby/gems/1.9.1/gems/wxruby-2.0.1-x86-mswin32-60/lib/wxruby2.so: [BUG] Segmentation fault ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mswin32] -- control frame ---------- c:0008 p:-9088168 s:0021 b:0021 l:000020 d:000020 TOP c:0007 p:---- s:0019 b:0019 l:000018 d:000018 CFUNC :require c:0006 p:0011 s:0015 b:0015 l:000014 d:000014 TOP C:/Program Files/Applications/Ruby/lib/ruby/gems/1.9.1/gems/wxruby-2.0.1-x86-mswin32-60/lib/wx.rb:12 c:0005 p:---- s:0012 b:0012 l:000011 d:000011 FINISH c:0004 p:---- s:0010 b:0010 l:000009 d:000009 CFUNC :require c:0003 p:0038 s:0006...

...p180 (2011-02-18 revision 30909) [x86_64-linux] *** [err :: myserver] *** [err :: myserver] -- control frame ---------- *** [err :: myserver] c:0120 *** [err :: myserver] p:---- *** [err :: myserver] s:0469 b:0469 *** [err :: myserver] l:000468 *** [err :: myserver] d:000468 *** [err :: myserver] CFUNC *** [err :: myserver] :New *** [err :: myserver] . . . . . . *** [err :: myserver] /var/www/apps/app-name/shared/bundle/ruby/1.9.1/gems/therubyracer-0.9.4/lib/v8/portal.rb:50:in `v8'' *** [err :: myserver] /var/www/apps/app-name/shared/bundle/ruby/1.9.1/gems/therubyracer-0.9.4/lib/v8/po...

..., Joerg Roedel wrote: > @@ -446,6 +448,82 @@ _ASM_NOKPROBE(\asmsym) > SYM_CODE_END(\asmsym) > .endm > ifdeffery pls... > +/** > + * idtentry_vc - Macro to generate entry stub for #VC > + * @vector: Vector number > + * @asmsym: ASM symbol for the entry point > + * @cfunc: C function to be called > + * > + * The macro emits code to set up the kernel context for #VC. The #VC handler > + * runs on an IST stack and needs to be able to cause nested #VC exceptions. > + * > + * To make this work the #VC entry code tries its best to pretend it doesn't u...

Jeff Brown wrote: > > Hi, > > I'm trying to learn to use .C, which lets one invoke compiled C code from > within R. To do that, one has to first get the C code into R as a shared > object, which (I think) means first compiling it (with COMPILE or SHLIB) > and then loading it (with dyn.load()). > I would suggest taking it a step further and building an R package

From: Joerg Roedel <jroedel at suse.de> Hi, here is the new version of the SEV-ES client enabling patch-set. It is based on the latest tip/master branch and contains the necessary changes. In particular those ar: - Enabling CR4.FSGSBASE early on supported processors so that early #VC exceptions on APs can be handled. - Add another patch (patch 1) to fix a KVM frame-size build

From: Joerg Roedel <jroedel at suse.de> Hi, here is a rebased version of the latest SEV-ES patches. They are now based on latest tip/master instead of upstream Linux and include the necessary changes. Changes to v4 are in particular: - Moved early IDT setup code to idt.c, because the idt_descr and the idt_table are now static - This required to make stack protector work early (or

From: Joerg Roedel <jroedel at suse.de> Hi, here is the fourth version of the SEV-ES Guest Support patches. I addressed the review comments sent to me for the previous version and rebased the code v5.8-rc5. The biggest change in this version is the IST handling code for the #VC handler. I adapted the entry code for the #VC handler to the big pile of entry code changes merged into

From: Joerg Roedel <jroedel at suse.de> Hi, here is the fourth version of the SEV-ES Guest Support patches. I addressed the review comments sent to me for the previous version and rebased the code v5.8-rc5. The biggest change in this version is the IST handling code for the #VC handler. I adapted the entry code for the #VC handler to the big pile of entry code changes merged into

From: Joerg Roedel <jroedel at suse.de> Hi, here is a new version of the SEV-ES Guest Support patches for x86. The previous versions can be found as a linked list starting here: https://lore.kernel.org/lkml/20200824085511.7553-1-joro at 8bytes.org/ I updated the patch-set based on ther review comments I got and the discussions around it. Another important change is that the early IDT

From: Joerg Roedel <jroedel at suse.de> Hi, here is a new version of the SEV-ES Guest Support patches for x86. The previous versions can be found as a linked list starting here: https://lore.kernel.org/lkml/20200824085511.7553-1-joro at 8bytes.org/ I updated the patch-set based on ther review comments I got and the discussions around it. Another important change is that the early IDT