search for: hmat

I can't comment on frailtypack issues, but would like to mention that coxme will handle nested models, contrary to the statement below that "frailtypack is perhaps the only .... for nested survival data". To reprise the original post's model cgd.nfm <- coxme(Surv(Tstart, Tstop, Status) ~ Treatment + (1 | Center/ID), data=cgd.ag) And a note to the poster-- you should

...:97] 0.545 0.606 0.485 0.415 0.636 ... .. ..@ rmat : num [1:102, 1:5] -0.00096 -0.000778 -0.000286 0.000102 -0.000688 ... .. ..@ offdiag : num 0 .. ..@ Dim : int [1:2] 102 102 .. ..@ Dimnames :List of 2 .. .. ..$ : NULL .. .. ..$ : NULL $ df : num [1:2] 6 49.3 $ hmat :Formal class 'gchol.bdsmatrix' [package "bdsmatrix"] with 6 slots .. ..@ blocksize: int [1:97] 1 1 1 1 1 1 1 1 1 1 ... .. ..@ blocks : num [1:97] 1.87 1.68 2.12 2.47 1.61 ... .. ..@ rmat : num [1:102, 1:5] -0.1885 0.0659 -0.2205 -0.0816 -0.1502 ... .. ..@...

Hi, I am just wondering if there is a test available for testing if a linear fit of an independent variable in a Cox regression is enough? Thanks for any suggestions. John Zhang ____________________________________________________________________________________ [[elided Yahoo spam]]

...o best be used with huge pages in the guest). But we could also > simply start only with RAM. I think it's up to the hypervisor to manage whether the guest is getting huge pages or not and the guest need not know. As for communicating differentiated memory media performance we have the ACPI HMAT (Heterogeneous Memory Attributes Table) for that. > 2. Adding also a guest -> host command queue. > > That can be used to request/notify the host about something. As written > in the original proposal, for ordinary RAM this could be used to request > more/less memory out of the g...

...o best be used with huge pages in the guest). But we could also > simply start only with RAM. I think it's up to the hypervisor to manage whether the guest is getting huge pages or not and the guest need not know. As for communicating differentiated memory media performance we have the ACPI HMAT (Heterogeneous Memory Attributes Table) for that. > 2. Adding also a guest -> host command queue. > > That can be used to request/notify the host about something. As written > in the original proposal, for ordinary RAM this could be used to request > more/less memory out of the g...

...s in the guest). But we could also >> simply start only with RAM. > > I think it's up to the hypervisor to manage whether the guest is > getting huge pages or not and the guest need not know. As for > communicating differentiated memory media performance we have the ACPI > HMAT (Heterogeneous Memory Attributes Table) for that. Yes, in the world of ACPI I agree. > >> 2. Adding also a guest -> host command queue. >> >> That can be used to request/notify the host about something. As written >> in the original proposal, for ordinary RAM this c...

Hi, this is an idea that is based on Andrea Arcangeli's original idea to host enforce guest access to memory given up using virtio-balloon using userfaultfd in the hypervisor. While looking into the details, I realized that host-enforcing virtio-balloon would result in way too many problems (mainly backwards compatibility) and would also have some conceptual restrictions that I want to avoid.

Hi, this is an idea that is based on Andrea Arcangeli's original idea to host enforce guest access to memory given up using virtio-balloon using userfaultfd in the hypervisor. While looking into the details, I realized that host-enforcing virtio-balloon would result in way too many problems (mainly backwards compatibility) and would also have some conceptual restrictions that I want to avoid.