search for: oustand

...PN 0x21000024ff376b98 isp0: max tagged openings: 4096, max dev openings: 4096 isp0: max_ccbs: 20488, ccb_count: 79 isp0: ccb_freeq is NOT empty isp0: alloc_queue.entries 0, alloc_openings 4096 isp0: qfrozen_cnt:0:0:0:0:0 (ctl2:isp0:0:0:0): 0 requests total waiting for CCBs (ctl2:isp0:0:0:0): 0 CCBs oustanding (17788811 allocated, 17788811 freed) (ctl2:isp0:0:0:0): 0 CTIOs outstanding (17788811 sent, 17788811 returned (ctl4:isp0:0:0:1): 0 requests total waiting for CCBs (ctl4:isp0:0:0:1): 0 CCBs oustanding (16708305 allocated, 16708305 freed) (ctl4:isp0:0:0:1): 0 CTIOs outstanding (16708305 sent, 1670...

...n Wed, Jul 23, 2014 at 11:39 AM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote: >> The scheduler needs to keep track of a lot of fences, so I think we'll >> have to register callbacks, not a simple wait function. We must keep >> track of all the non-i915 fences for all oustanding batches. Also, the >> scheduler doesn't eliminate the hw queue, only keep it much slower so >> that we can sneak in higher priority things. >> >> Really, scheduler or not is orthogonal. > Also see my other comment about interactions between wait_fence and > the...

...? > > Cause that sounds like reducing the necessary fence interface to just a > fence->wait function. The scheduler needs to keep track of a lot of fences, so I think we'll have to register callbacks, not a simple wait function. We must keep track of all the non-i915 fences for all oustanding batches. Also, the scheduler doesn't eliminate the hw queue, only keep it much slower so that we can sneak in higher priority things. Really, scheduler or not is orthogonal. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch

I am seeing a problem with the Xen emulated serial console. When running a Linux 2.6.20 HVM guest that has CONFIG_HOTPLUG_CPU=n, the guest blocks on output to the console until it receives input keypresses from `xm console`. This prevents the guest from booting up without banging on some keys, and makes interactive use of the console difficult. By bisecting Linux kernel commits, I found that

...ing. Our dedication to delivering quality medicines in innovative ways and our commitment to bringing out the best in our people are just some of the reasons why we're ranked among Fortune magazine's "100 Best Companies to Work for in America." We offer a competitive salary, an oustanding benefits package, and a professional work environment with a company known for scientific excellence. To apply, please forward your CV or resume and cover letter to ATTENTION: Open Position Vladimir Svetnik, Ph.D. Biometrics Research Dept. Merck Research Laboratories, RY33-300 126 E. Lincoln A...

...red. Our dedication to delivering quality medicines in innovative ways and our commitment to bringing out the best in our people are just some of the reasons why we're ranked among Fortune magazine's "100 Best Companies to Work for in America." We offer a competitive salary, an oustanding benefits package, and a professional work environment with a company known for scientific excellence. To apply, please forward your CV or resume and cover letter to ATTENTION: Open Positions Vladimir Svetnik, Ph.D. Biometrics Research Dept. Merck Research Laboratories, RY33-300 126 E. Lincoln...

On Wed, Jul 23, 2014 at 11:39 AM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote: > The scheduler needs to keep track of a lot of fences, so I think we'll > have to register callbacks, not a simple wait function. We must keep > track of all the non-i915 fences for all oustanding batches. Also, the > scheduler doesn't eliminate the hw queue, only keep it much slower so > that we can sneak in higher priority things. > > Really, scheduler or not is orthogonal. Also see my other comment about interactions between wait_fence and the i915 reset logic. We can&...

...3, 2014 at 11:39 AM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote: >>> The scheduler needs to keep track of a lot of fences, so I think we'll >>> have to register callbacks, not a simple wait function. We must keep >>> track of all the non-i915 fences for all oustanding batches. Also, the >>> scheduler doesn't eliminate the hw queue, only keep it much slower so >>> that we can sneak in higher priority things. >>> >>> Really, scheduler or not is orthogonal. >> Also see my other comment about interactions between wait...

On Wed, Jul 23, 2014 at 11:27 AM, Christian K?nig <christian.koenig at amd.com> wrote: > You submit a job to the hardware and then block the job to wait for radeon > to be finished? Well than this would indeed require a hardware reset, but > wouldn't that make the whole problem even worse? > > I mean currently we block one userspace process to wait for other hardware >

...1:39 AM, Daniel Vetter <daniel.vetter at ffwll.ch> wrote: >>>> The scheduler needs to keep track of a lot of fences, so I think we'll >>>> have to register callbacks, not a simple wait function. We must keep >>>> track of all the non-i915 fences for all oustanding batches. Also, the >>>> scheduler doesn't eliminate the hw queue, only keep it much slower so >>>> that we can sneak in higher priority things. >>>> >>>> Really, scheduler or not is orthogonal. >>> Also see my other comment about inter...

Hi, How can I figure why some domain is still in zombie state, like these ones: master-xen root /vm/ttylinux# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 574 1 r----- 90.5 Zombie-small-11 28 0 1 ---s-d 0.9 Zombie-small-17 34 0 1 ---s-d

...difference between the top of the current range and the input value, minus one. In the encoder: the low end of the current range.*/ - ec_uint32 val; + celt_uint32 val; /*In the decoder: the saved normalization factor from ec_decode(). In the encoder: the number of oustanding carry propagating symbols.*/ - ec_uint32 ext; + celt_uint32 ext; /*A buffered input/output symbol, awaiting carry propagation.*/ int rem; /*Nonzero if an error occurred.*/ @@ -97,7 +95,7 @@ static inline void ec_reset(ec_ctx *_this){ _this->offs=_this-&gt...

> On Nov 17, 2016, at 2:55 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > Hi Gerolf, > > This is really cool! > I’m very excited about this initiative and I hope we’ll be able to get to a stage where compile time regression are handled like other regression: if they are not expected / justified by the commit author promptly, the commit should be reverted in the