search for: mhp

...PFN_PHYS(start_pfn), PFN_PHYS(end_pfn)); + mm_to_dma_pfn(start_pfn), + mm_to_dma_pfn(end_pfn)); if (ret) return ret; } @@ -4593,58 +4585,37 @@ static int intel_iommu_memory_notifier(struct notifier_block *nb, unsigned long val, void *v) { struct memory_notify *mhp = v; - unsigned long long start, end; - unsigned long start_vpfn, last_vpfn; + unsigned long start_vpfn = mm_to_dma_pfn(mhp->start_pfn); + unsigned long last_vpfn = mm_to_dma_pfn(mhp->start_pfn + + mhp->nr_pages - 1); switch (val) { case MEM_GOING_ONLINE: - start = mhp->start_p...

...only. ----- For changing directories during a session, I use the following function, a slight modification of Andy Liaw's cd() function that also changes the titlebar: cd <- function(dir = tclvalue(tkchooseDirectory()), saveOld=NA, loadNew=TRUE) { # From Andy Liaw ... additions by MHP # Change the working directory during an R session # # First check that the tcl-tk package is available: stopifnot(require(tcltk)) # Print any error message from trying to load: if (.Platform$OS.type=="windows") flush.console() ## MHP # Warn user if saving exi...

..., data = x) ....... ........ (Dispersion parameter for binomial family taken to be 1) Null deviance: 365.00 on 266 degrees of freedom Residual deviance: 305.72 on 261 degrees of freedom AIC: 317.72 Number of Fisher Scoring iterations: 3 Correlation of Coefficients: ( dP dI dC mHP durP 1 durI 1 durC 1 moyHzPB . 1 moyHzIN , attr(,"legend") [1] 0 ` ' 0.3 `.' 0.6 `,' 0.8 `+' 0.9 `*' 0.95 `B' 1 I used binaries rpm from CRAN . The same error is obtained with R1.2 on RH6.2 and R.1.3.1-1 on RH7.0 (with the up...

...fred) <- as.integer(c(NA,5)) Error in `row.names<-.data.frame`(`*tmp*`, value = c(NA, 5)) : invalid 'row.names' length Is there any reason why the expression c(NA,5) is better here than the more natural 1:5 here? I will appreciate help from anyone with time to reply. MHP -- Mike Prager, NOAA, Beaufort, NC * Opinions expressed are personal and not represented otherwise. * Any use of tradenames does not constitute a NOAA endorsement.

...MT (2 weeks, 1 day, 23 hours and 55 minutes ago) > >Walter -- > >P.S. The advantage of using formatC over pasting the digits (1:1000) >directly is that when one uses leading zeroes, as in the formatC example >shown, the resulting filenames will sort into proper order. > >...MHP > >You can use paste() with something like > > formatC(number,digits=0,wid=3,flag="0") > >(where number is your loop index) to generate the filenames. > >on 9/22/2005 10:21 AM Leite,Walter said the following: > >>I have a question about how to save to the...

Hello, I'm hoping that there is an easier way to rename columns in a data frame other than by using the names() assignment, which requires you to type in all the column names at once for a data.frame, in the case that I simply want to rename a single column in a data frame. Also, is there an easy way to move columns in a data frame around relative to the other columns? Thanks in

@Andrew, @Mst, I suggest the whole series (including the virtio-mem change) goes via the -mm tree. Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising

For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff maintained by me. This should go via the -mm tree. --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now that the semantics are much clearer (and are documented in patch #6),

For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff maintained by me. This should go via the -mm tree. --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now that the semantics are much clearer (and are documented in patch #6),

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4,#6 have RBss or ACKs, patch #5 is virtio-mem stuff maintained by me (and MST is aware). --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4,#6 have RBss or ACKs, patch #5 is virtio-mem stuff maintained by me (and MST is aware). --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4 have RB's, patch #5 is virtio-mem stuff maintained by me, patch #6 is just a doc update. --- Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4 have RB's, patch #5 is virtio-mem stuff maintained by me, patch #6 is just a doc update. --- Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to

Hi, I have to R fairly recently from Matlab, where I have been used to organising my own custom functions into directories which are adding to the Matlab search path. This enables me to call them as I would one of Matlab's built-in functions. I have not found a way of doing the same thing in R. I have resorted to using source() on symlinks located in the current directory. Not very

Dear R-Help members, I have a question about how to save to the hard drive the one thousand datasets I generated in a simulation. The datasets are created in a "for" loop that repeatedly creates normally distributed datasets, such as the example below: Library(MASS) for (number in 1:1000) { dataset = mvrnorm(n = 400, mu = c(0,0,0), Sigma =

Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising for users (especially, if onlining suddenly fails). Let's support partially plugged memory

Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising for users (especially, if onlining suddenly fails). Let's support partially plugged memory

This patchset converts the intel iommu driver to the dma-iommu api. While converting the driver I exposed a bug in the intel i915 driver which causes a huge amount of artifacts on the screen of my laptop. You can see a picture of it here: https://github.com/pippy360/kernelPatches/blob/master/IMG_20191219_225922.jpg This issue is most likely in the i915 driver and is most likely caused by the

This patchset converts the intel iommu driver to the dma-iommu api. While converting the driver I exposed a bug in the intel i915 driver which causes a huge amount of artifacts on the screen of my laptop. You can see a picture of it here: https://github.com/pippy360/kernelPatches/blob/master/IMG_20191219_225922.jpg This issue is most likely in the i915 driver and is most likely caused by the

I'd like to develop a simple library in R in which to save my particular functions. I have read the manual on "Writing R Extensions" but it's too difficult. Someone could help me? I want only save my personal function (recorded in R-code, not in C) in "myLibrary" and I want to call it with: >library (myLibrary). After this, the functions should be available