search for: unprepar

...ish string values, suitable for storage in a xenstore directory. vdi This host''s intent to access a specific target. Non-persistent, created on request by toolstack, enumerable. Possible states: inactive/active. Abstract operations: prepare, activate, deactivate, unprepare. (We call the "create" operation for this object "prepare" to avoid confusion with other kinds of "create".) The toolstack promises that no two vdis for the same target will simultaneously be active, even if the two vdis are on different hos...

...anywhere. Again nothing useful in them either. So if this was a hardware failure (harddrive), then any kernel panic statements probably would not make it to the harddrive. So it would be hard to tell. My question is, what if i got hacked? Would there be anyway to find out despite me being totally unprepared for this? That question really messes with my head. Any pointer and/or clue stick treatments would be greatly appreciated. thanx mario;> --------------------- Do you schmut!? http://www.schmut.com For a real web site try: House Of Sites http://www.HouseOfSites.net Email: mario@HouseOfSite...

The virtio balloon driver has a VIRTIO_BALLOON_F_MUST_TELL_HOST feature bit. Whenever the bit is set, we must always tell the host before we free pages back to the allocator. Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don&...

The virtio balloon driver has a VIRTIO_BALLOON_F_MUST_TELL_HOST feature bit. Whenever the bit is set, we must always tell the host before we free pages back to the allocator. Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don&...

...s the playback thread. If I make the necessary changes to make the OSS_OpenDevice() failure not blast OSS_OpenFD, the playing thread eventually does finish. All the while, the other thread keeps tring the open again and again.... Ultimately, though the playing thread never goes through the Reset/Unprepare/Close sequence, so no sound after that point. My questions: Am I looking at too low a level in the code to properly diagnose this? Are there higher level functions that should be ensuring complete playback (including close)? What other debug traces should I turn on? Or does this look like a bu...

...has a VIRTIO_BALLOON_F_MUST_TELL_HOST > feature bit. Whenever the bit is set, the guest kernel must > always tell the host before we free pages back to the allocator. > Without this feature, we might free a page (and have another > user touch it) while the hypervisor is unprepared for it. > > But, if the bit is _not_ set, we are under no obligation to > reverse the order; we're under no obligation to do _anything_. > As of now, qemu-kvm defines the bit, but doesn't set it. Well this is not what the spec says in the end. To continue that co...

...has a VIRTIO_BALLOON_F_MUST_TELL_HOST > feature bit. Whenever the bit is set, the guest kernel must > always tell the host before we free pages back to the allocator. > Without this feature, we might free a page (and have another > user touch it) while the hypervisor is unprepared for it. > > But, if the bit is _not_ set, we are under no obligation to > reverse the order; we're under no obligation to do _anything_. > As of now, qemu-kvm defines the bit, but doesn't set it. Well this is not what the spec says in the end. To continue that co...

...(&engine->queue_lock, flags); > - if (engine->cur_req == &req->base) > - finalize_cur_req = true; > - spin_unlock_irqrestore(&engine->queue_lock, flags); > - > - if (finalize_cur_req) { > - if (engine->cur_req_prepared && > - engine->unprepare_cipher_request) { > - ret = engine->unprepare_cipher_request(engine, req); > - if (ret) > - dev_err(engine->dev, "failed to unprepare request\n"); > - } > - spin_lock_irqsave(&engine->queue_lock, flags); > - engine->cur_req = NULL; > - engi...

...(&engine->queue_lock, flags); > - if (engine->cur_req == &req->base) > - finalize_cur_req = true; > - spin_unlock_irqrestore(&engine->queue_lock, flags); > - > - if (finalize_cur_req) { > - if (engine->cur_req_prepared && > - engine->unprepare_cipher_request) { > - ret = engine->unprepare_cipher_request(engine, req); > - if (ret) > - dev_err(engine->dev, "failed to unprepare request\n"); > - } > - spin_lock_irqsave(&engine->queue_lock, flags); > - engine->cur_req = NULL; > - engi...

...fset2= add i64, %j, %offset1 %1 = getelementptr double, double* %A, inrange i64 %offset2 %2 = llvm.multidim.access.pdouble.pdouble.i64.i64.i64.i64(double* %A, i64 %n, i64 %m, i64 %i, i64 %j) %cmp = icmp eq %1, %2 call void @llvm.assume(i1 %cmp) The main motivation is to avoid that unprepared analyses such as BasicAA have to give up when encountering the new intrinsic. 2. and 3. only add things around as they were before such multidimensional accesses. Subjectively, I don't think that having to give up is such a big problem. In the beginning, there will be no frontend that genera...

.../" (the current directory) is referring. Do you have any clues on how to solve that problem? BTW: Also sharing /Shares/CAD is not a solution I'm after :) Thanks a lot, Alexander Skwar -- If there were a school for, say, sheet metal workers, that after three years left its graduates as unprepared for their careers as does law school, it would be closed down in a minute, and no doubt by lawyers. -- Michael Levin, "The Socratic Method -------------------------------------------------------------------------

...&engine->queue_lock, flags); + if (engine->cur_req == req) + finalize_cur_req = true; + spin_unlock_irqrestore(&engine->queue_lock, flags); + + if (finalize_cur_req) { + enginectx = crypto_tfm_ctx(req->tfm); + if (engine->cur_req_prepared && + enginectx->op.unprepare_request) { + ret = enginectx->op.unprepare_request(engine, req); + if (ret) + dev_err(engine->dev, "failed to unprepare request\n"); + } + spin_lock_irqsave(&engine->queue_lock, flags); + engine->cur_req = NULL; + engine->cur_req_prepared = false; + spin_un...

...; > > - if (engine->cur_req == &req->base) > > - finalize_cur_req = true; > > - spin_unlock_irqrestore(&engine->queue_lock, flags); > > - > > - if (finalize_cur_req) { > > - if (engine->cur_req_prepared && > > - engine->unprepare_cipher_request) { > > - ret = engine->unprepare_cipher_request(engine, req); > > - if (ret) > > - dev_err(engine->dev, "failed to unprepare request\n"); > > - } > > - spin_lock_irqsave(&engine->queue_lock, flags); > > - engine-&g...

...e; - int ret; - - spin_lock_irqsave(&engine->queue_lock, flags); - if (engine->cur_req == &req->base) - finalize_cur_req = true; - spin_unlock_irqrestore(&engine->queue_lock, flags); - - if (finalize_cur_req) { - if (engine->cur_req_prepared && - engine->unprepare_cipher_request) { - ret = engine->unprepare_cipher_request(engine, req); - if (ret) - dev_err(engine->dev, "failed to unprepare request\n"); - } - spin_lock_irqsave(&engine->queue_lock, flags); - engine->cur_req = NULL; - engine->cur_req_prepared = false; -...

...; + if (engine->cur_req == req) > finalize_cur_req = true; > spin_unlock_irqrestore(&engine->queue_lock, flags); > > if (finalize_cur_req) { > + enginectx = crypto_tfm_ctx(req->tfm); > if (engine->cur_req_prepared && > - engine->unprepare_cipher_request) { > - ret = engine->unprepare_cipher_request(engine, req); > + enginectx->op.unprepare_request) { > + ret = enginectx->op.unprepare_request(engine, req); > if (ret) > dev_err(engine->dev, "failed to unprepare request\n"); &gt...

Any quick tips? I''ve been getting the SQL Server adapter up to passing for 3.2 and I wanted to test our explain printer. It will be very much like mysql2''s printer. But I think my brain is mush and my meta-fu weak at the moment and I need some help. I tried stubbing ActiveRecord::Base.logger.warn but to no avail. Any thoughts? - Ken -- You received this message because you

...LOON_F_MUST_TELL_HOST >> feature bit. Whenever the bit is set, the guest kernel must >> always tell the host before we free pages back to the allocator. >> Without this feature, we might free a page (and have another >> user touch it) while the hypervisor is unprepared for it. >> >> But, if the bit is _not_ set, we are under no obligation to >> reverse the order; we're under no obligation to do _anything_. >> As of now, qemu-kvm defines the bit, but doesn't set it. > > Well this is not what the spec says in the...

...n far more from this list than we will be able to contribute (at least in the near term) owe it to those who will likely contribute far more than they will actually gain to do our homework before asking the list. The risk of enduring a withering (and public) "Ripley" for being apparently unprepared (whether valid or not), is probably a small price to pay for the number of "how do I use R to compute the mean" questions that are likely filtered out as a consequence. On the other hand, big contributors are surely entitled (but not, I suppose, obliged) to say what they like. Enjoyin...

...onf, as well as the os level=65 line Danger!!! If you set the options as above, then your Samba box will become a domain master browser for its domain. I'll register the NetBIOS name for that domain, and your NT PDC will lose the election. PDC's don;t expect this to happen, and are caught unprepared by it. From the Samba docs:- Note that you should NOT set Samba to be the domain master for a workgroup that has the same name as an NT Domain: on each wide area network, you must only ever have one domain master browser per workgroup, regardless of whether it is NT, Samba or any other type of d...

...(engine->cur_req == &req->base) + if (engine->cur_req == req) finalize_cur_req = true; spin_unlock_irqrestore(&engine->queue_lock, flags); if (finalize_cur_req) { + enginectx = crypto_tfm_ctx(req->tfm); if (engine->cur_req_prepared && - engine->unprepare_cipher_request) { - ret = engine->unprepare_cipher_request(engine, req); + enginectx->op.unprepare_request) { + ret = enginectx->op.unprepare_request(engine, req); if (ret) dev_err(engine->dev, "failed to unprepare request\n"); } @@ -285,46 +267,64 @@ voi...