search for: kind

Turing introduced a new simplified page kind scheme, reducing the number of possible page kinds from 256 to 16. It also is the first NVIDIA GPU in which the highest possible page kind value is not reserved as an "invalid" page kind. To address this, the invalid page kind is made an explicit property of the MMU HAL, and a new table...

Hi all, I?m fitting GLM?s and I can?t interprete the coefficients when I run a model with interaction terms. When I run the simpliest model there is no problem: Model1<-glm (Fishes ~ Year + I(Year^2) + Kind.Geographic + Kind.Fishers + Zone.2 + Hours + Fishers + Month, family = poisson(log)) # Fishes, Year, Hours, and Fishers are numeric, Kind.Geographic, Kind.Fishers, Zone.2 and Month are factors with 4, 3, 5 and 12 levels respectively. Model1$coefficients (whith Helmert contrasts): (Int...

...is included below along with a test (which works in Solaris with R and Splus 3.3). The approach is somewhat different from the usual problems on this list as I am trying to get the same results from Splus as I get from R. However, there are a couple of R issues: - There is a small change to RNGkind to allow "default" (currently Wichmann-Hill but could change from time to time). -The strategy for specifying the transformation to get rnorm results should be examined, as I think it should be put into R and extended for other random number transformations. Paul Gilbert ________ # F...

On Wed, Dec 11, 2019 at 4:04 PM James Jones <jajones at nvidia.com> wrote: > > Allow setting the block layout of a nouveau FB > object using DRM format modifiers. When > specified, the format modifier block layout and > kind overrides the GEM buffer's implicit layout > and kind. The specified format modifier is > validated against he list of modifiers supported > by the target display hardware. > > Signed-off-by: James Jones <jajones at nvidia.com> > --- > drivers/gpu/drm/nouveau/dispnv...

...onvert -f yaml -symbolize -instr_map=./fdr-mode xray-log.fdr-mode.Xubrrm --- header: version: 2 type: 1 constant-tsc: true nonstop-tsc: true cycle-frequency: 3400000000 records: - { type: 0, func-id: 3, function: 'fA()', cpu: 2, thread: 31756, kind: function-enter, tsc: 4955892956329578 } - { type: 0, func-id: 2, function: 'fB()', cpu: 2, thread: 31756, kind: function-enter, tsc: 4955892956357542 } - { type: 0, func-id: 1, function: 'fC()', cpu: 2, thread: 31756, kind: function-enter, tsc: 4955892956358238 } - { type:...

.../joel de vahl Example code: template <typename T> class Test { T test; }; struct S { }; Test<int> test_int; Test<S> test_struct; Tree dump script: def DeepPrintType(node, depth = 0): tabs = " " * depth print tabs + "type" print tabs + " kind", node.kind def DeepPrint(node, depth = 0): tabs = " " * depth print tabs + "cursor", node.spelling print tabs + " location", node.location node_type_res = node.type.get_result() print tabs + " result", node_type_res.kind print...

Justin, thanks for the reply. I would like to point out that value_kind is actually not really stored in the raw profile data (nor do we intend to do so), other than the minimal information about per value kind NumOfSites info in per-function profile header. Basically the data is organized per value kind instead of stored intermixed. That is about it. More replies be...

My suggestion: 1. Keep the value kind enum, but remove the reserved kinds 2. In compiler-rt code, assert the kind to be icalltarget and remove the loop 3. Keep the indexed format (as is now) 4. Add assertion in profile use that icalltarget is the only expected kind. Justin, does this sound reasonable? David On Jul 2, 2015 1:10 PM, &q...

> Xinliang David Li <davidxl at google.com> writes: >> Justin, thanks for the reply. >> I would like to point out that value_kind is actually not really stored in the raw profile data (nor do we intend to do so), other than the minimal information about per value kind NumOfSites info in per-function profile header. Basically the data is organized per value kind instead of stored intermixed. That is about it. >> More re...

Justin, do you have more concerns on keeping value_kind? If there is still disagreement, can we agree to move on with it for now ? After the initial version of the patches checked in, we can do more serious testings with large apps and revisit this if there are problems discovered. thanks, David On Mon, Jun 15, 2015 at 10:47 PM, Xinliang David Li...

Allow setting the block layout of a nouveau FB object using DRM format modifiers. When specified, the format modifier block layout and kind overrides the GEM buffer's implicit layout and kind. The specified format modifier is validated against he list of modifiers supported by the target display hardware. Signed-off-by: James Jones <jajones at nvidia.com> --- drivers/gpu/drm/nouveau/dispnv50/wndw.c | 8 +-- drivers/gpu/...

...1/19 1:13 PM, Ilia Mirkin wrote: > On Wed, Dec 11, 2019 at 4:04 PM James Jones <jajones at nvidia.com> wrote: >> >> Allow setting the block layout of a nouveau FB >> object using DRM format modifiers. When >> specified, the format modifier block layout and >> kind overrides the GEM buffer's implicit layout >> and kind. The specified format modifier is >> validated against he list of modifiers supported >> by the target display hardware. >> >> Signed-off-by: James Jones <jajones at nvidia.com> >> --- >> d...

Xinliang David Li <davidxl at google.com> writes: > On Mon, Jun 15, 2015 at 5:35 PM, Justin Bogner <mail at justinbogner.com> wrote: >> "Betul Buyukkurt" <betulb at codeaurora.org> writes: >>>> - We don't need to store the value profiling kind in the data at all. >>>> The frontend knows which invocations of the intrinsic are for each kind >>>> implicitly, much like it knows the difference between a counter for an >>>> "if" and a "for" apart implicitly. Just store one set of pr...

...reds = %"168.i", %"161.i" call void bitcast (void (...)* @_gfortran_cpu_time_4 to void (float*)*)(float* %finish.i) nounwind br i1 %37, label %"172.i", label %"171.i" GIMPLE: ======= _gfortran_cpu_time_4 (&start); { integer(kind=4) D.1699; D.1699 = ns; k = 1; if (k <= D.1699) goto <D.2262>; else goto <D.2263>; <D.2262>: <D.2264>: { logical(kind=4) D.1710; { integer(kind=4) D.1702; D....

...RNG(old.rng)) } ... } and know that I have all the information for reproducibility. Below is a version of this that I have been using for a few years. Its main shortcoming is that it only considers the uniform generator and normal transformation. Paul Gilbert ______ set.RNG <- function(kind=NULL, seed=NULL, normal.kind=NULL) {# with a null argument this also serves as get.RNG #The next line means that set.RNG with null args does not truly # return the state of the RNG in the case when it has not been # initialize. It first initializes it and then retur...

Hi Daniel, thanks for the quick reply we did try to override SMBIOS host_uuid_source = "machine-id" and it didn't work even that nodes have different [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker root@kind-1:/# cat /etc/machine-id [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane root@kind-1:/# cat /etc/machine-id 71ebb3fc051a48b2b45345b67bb1002b Thanks On Thu, Mar 26, 2020 at 5:05 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Thu,...

This series modifies the NV5x+ nouveau display backends to advertise appropriate format modifiers on their display planes in atomic mode setting blobs. Corresponding modifications to Mesa/userspace are available here: https://gitlab.freedesktop.org/cubanismo/mesa/tree/nouveau_work But those need a bit of cleanup before they're ready to submit. I've tested this on Tesla, Kepler, Pascal,

...ited, deemed safe, and left as-is for consistency with existing code. v3: -Rebased on nouveau linux-5.6 @ 137c4ba7163ad9d5696b9fde78b1c0898a9c115b -Noted corresponding Mesa patches are production-worthy now -Better validate bo tile_mode when checking framebuffer size. v4: Do not cache kind, tile_mode in nouveau_framebuffer v5: Resolved against nouveau_framebuffer cleanup James Jones (3): drm/nouveau: Add format mod prop to base/ovly/nvdisp drm/nouveau: Check framebuffer size against bo drm/nouveau: Support NVIDIA format modifiers drivers/gpu/drm/nouveau/dispnv50/base507c.c...

...ited, deemed safe, and left as-is for consistency with existing code. v3: -Rebased on nouveau linux-5.6 @ 137c4ba7163ad9d5696b9fde78b1c0898a9c115b -Noted corresponding Mesa patches are production-worthy now -Better validate bo tile_mode when checking framebuffer size. v4: Do not cache kind, tile_mode in nouveau_framebuffer James Jones (3): drm/nouveau: Add format mod prop to base/ovly/nvdisp drm/nouveau: Check framebuffer size against bo drm/nouveau: Support NVIDIA format modifiers drivers/gpu/drm/nouveau/dispnv50/base507c.c | 7 +- drivers/gpu/drm/nouveau/dispnv50/disp.c...

Make use of the struct_size() helper instead of an open-coded version in order to avoid any potential type mistakes, in particular in the context in which this code is being used. So, replace the following form: sizeof(*kind) + sizeof(*kind->data) * mmu->kind_nr; with: struct_size(kind, data, mmu->kind_nr) This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva <gustavo at embeddedor.com> --- drivers/gpu/drm/nouveau/nvif/mmu.c | 2 +- 1 file changed, 1 insertion(+), 1...