search for: v13

Hi everyone, I am attempting to use the apply() function to obtain the mode and class of each column in a data frame, however, I am encountering unexpected results. I have the following example data: v13<-1:6 v14<-c(1,2,3,3,NA,1) v15<-c("Good","Bad",NA,"Good","Bad","Bad") f4<-factor(rep(c("Blue","Red","Green"),2)) v16<-c(F,T,F,F,T,F) data6<-data.frame(v13,v14,v15,f4,v16) data6 Here is my function def...

Hi I am brand new to Linux and Wine and so far have found getting everything working has been very easy. My only problem has been with my favourite 3D program - Cybermotion v13. I see from the apps database that version 12 worked okay but I am having problems getting the latest version to run. When run the splash screen appears but problems occur when the main display loads. Everything looks like it might work but everything soon stops with a 'float-invalid operation...

..., main=titles[n]) axis(1) axis(2) lines(1:5, pred.mat[k+1,], lty=1) lines(1:5, pred.mat[k+2,], lty=3) legend("topright", c("avg. player", "5th %-tile player", "95th %-tile player"), lty=1:3, bty="n") n<-n+1 } } plotProb(q8.pred.mat.v13, c(193, 196, 199, 205, 217,241,289), c(3,3), q8.titles3, "identification") [1] "debug" [1] 193 [1] 1 [1] 1920 Error in print(pred.mat[k, ]) : error in evaluating the argument 'x' in selecting a method for function 'print': Error: subscript out of bounds &gt...

Hi list, on asterisk 13 I use same => n,Set(__myCpt=$[${myCpt} + 1]) which is working well. On an Asterisk 16 I get, for this same command [2019-10-01 16:15:01] WARNING[28197][C-00000008]: ast_expr2.fl:470 ast_yyerror: ast_yyerror(): syntax error: syntax error, unexpected '+', expecting $end; Input: + 1 ^ What changes in 16 version creates this behavior and how to

On 08/03/2017 06:44 PM, Michal Hocko wrote: > On Thu 03-08-17 18:42:15, Wei Wang wrote: >> On 08/03/2017 05:11 PM, Michal Hocko wrote: >>> On Thu 03-08-17 14:38:18, Wei Wang wrote: > [...] >>>> +static int report_free_page_block(struct zone *zone, unsigned int order, >>>> + unsigned int migratetype, struct page **page) >>> This is just too

On 08/03/2017 04:13 PM, Pankaj Gupta wrote: >> >> + /* Allocate space for find_vqs parameters */ >> + vqs = kcalloc(nvqs, sizeof(*vqs), GFP_KERNEL); >> + if (!vqs) >> + goto err_vq; >> + callbacks = kmalloc_array(nvqs, sizeof(*callbacks), GFP_KERNEL); >> + if (!callbacks) >> + goto

> > On 08/03/2017 04:13 PM, Pankaj Gupta wrote: > >> > >> + /* Allocate space for find_vqs parameters */ > >> + vqs = kcalloc(nvqs, sizeof(*vqs), GFP_KERNEL); > >> + if (!vqs) > >> + goto err_vq; > >> + callbacks = kmalloc_array(nvqs, sizeof(*callbacks), GFP_KERNEL); > >> + if

On Thursday, August 3, 2017 10:23 PM, Michael S. Tsirkin wrote: > On Thu, Aug 03, 2017 at 02:38:17PM +0800, Wei Wang wrote: > > +static void send_one_sg(struct virtio_balloon *vb, struct virtqueue *vq, > > + void *addr, uint32_t size) > > +{ > > + struct scatterlist sg; > > + unsigned int len; > > + > > + sg_init_one(&sg, addr, size); > > +

On Thursday, August 3, 2017 9:51 PM, Michal Hocko: > As I've said earlier. Start simple optimize incrementally with some numbers to > justify a more subtle code. > -- OK. Let's start with the simple implementation as you suggested. Best, Wei

On Fri 04-08-17 00:02:01, Michael S. Tsirkin wrote: > On Thu, Aug 03, 2017 at 03:20:09PM +0000, Wang, Wei W wrote: > > On Thursday, August 3, 2017 9:51 PM, Michal Hocko: > > > As I've said earlier. Start simple optimize incrementally with some numbers to > > > justify a more subtle code. > > > -- > > > > OK. Let's start with the simple

On Fri 04-08-17 16:15:24, Wei Wang wrote: > On 08/04/2017 03:53 PM, Michal Hocko wrote: > >On Fri 04-08-17 00:02:01, Michael S. Tsirkin wrote: > >>On Thu, Aug 03, 2017 at 03:20:09PM +0000, Wang, Wei W wrote: > >>>On Thursday, August 3, 2017 9:51 PM, Michal Hocko: > >>>>As I've said earlier. Start simple optimize incrementally with some numbers to

On 08/03/2017 05:11 PM, Michal Hocko wrote: > On Thu 03-08-17 14:38:18, Wei Wang wrote: > This is just too ugly and wrong actually. Never provide struct page > pointers outside of the zone->lock. What I've had in mind was to simply > walk free lists of the suitable order and call the callback for each one. > Something as simple as > > for (i = 0; i < MAX_NR_ZONES;

On Tue 08-08-17 14:34:25, Wei Wang wrote: > On 08/08/2017 02:12 PM, Wei Wang wrote: > >On 08/03/2017 05:11 PM, Michal Hocko wrote: > >>On Thu 03-08-17 14:38:18, Wei Wang wrote: > >>This is just too ugly and wrong actually. Never provide struct page > >>pointers outside of the zone->lock. What I've had in mind was to simply > >>walk free lists of

I pushed this now, thanks. I made a few fixes: - Trailing whitespace in a few places. - The "--keep-index" option was documented but does not appear to exist in the tool itself. test-docs.sh caught this. - index_parser_tests.ml did not build. - Updated website.html.in. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my

> > On 08/03/2017 04:13 PM, Pankaj Gupta wrote: > >> > >> + /* Allocate space for find_vqs parameters */ > >> + vqs = kcalloc(nvqs, sizeof(*vqs), GFP_KERNEL); > >> + if (!vqs) > >> + goto err_vq; > >> + callbacks = kmalloc_array(nvqs, sizeof(*callbacks), GFP_KERNEL); > >> + if

Am 25.03.23 um 15:58 schrieb Dmitry Osipenko: > On 3/15/23 16:46, Dmitry Osipenko wrote: >> On 3/14/23 05:26, Dmitry Osipenko wrote: >>> @@ -633,7 +605,10 @@ int drm_gem_shmem_mmap(struct drm_gem_shmem_object *shmem, struct vm_area_struct >>> return ret; >>> } >>> >>> + dma_resv_lock(shmem->base.resv, NULL); >>> ret =

On Mon, Aug 26, 2013 at 02:18:32PM +0530, Raghavendra K T wrote: > > This series forms the kvm host part of paravirtual spinlock > based against kvm tree. > > Please refer to https://lkml.org/lkml/2013/8/9/265 for > kvm guest and Xen, x86 part merged to -tip spinlocks. > > Please note that: > kvm uapi: Add KICK_CPU and PV_UNHALT definition to uapi is a common

KVM_HC_KICK_CPU hypercall added to wakeup halted vcpu in paravirtual spinlock enabled guest. KVM_FEATURE_PV_UNHALT enables guest to check whether pv spinlock can be enabled in guest. Thanks Vatsa for rewriting KVM_HC_KICK_CPU Cc: Rob Landley <rob at landley.net> Signed-off-by: Srivatsa Vaddagiri <vatsa at linux.vnet.ibm.com> Signed-off-by: Raghavendra K T <raghavendra.kt at

On 08/03/2017 07:28 PM, Michal Hocko wrote: > On Thu 03-08-17 19:27:19, Wei Wang wrote: >> On 08/03/2017 06:44 PM, Michal Hocko wrote: >>> On Thu 03-08-17 18:42:15, Wei Wang wrote: >>>> On 08/03/2017 05:11 PM, Michal Hocko wrote: >>>>> On Thu 03-08-17 14:38:18, Wei Wang wrote: >>> [...] >>>>>> +static int

On Wed, 12 Jun 2019 18:15:22 +0530 Pankaj Gupta <pagupta at redhat.com> wrote: > This patch adds virtio-pmem driver for KVM guest. > > Guest reads the persistent memory range information from > Qemu over VIRTIO and registers it on nvdimm_bus. It also > creates a nd_region object with the persistent memory > range information so that existing 'nvdimm/pmem' driver