similar to: call-limit in 1.2 HEAD

Hello all, I've installed AAH 1.1 on my VIA C3 powered mini PC. I've made the necessary changes to the * makefile, so the compilation went well. The first thing I did was configuring two extensions from AMP, namely 200 and 201. Then I installed X-lite on two PC's and configured them with one of the extensions: System settings - SIP proxy - Default: Username: 200 Authorisation user:

vhost checked the counter within the refcnt before decrementing. It really wanted to know that it is the one that has the last reference, as a way to batch freeing resources a bit more efficiently. Note: we only let refcount go to 0 on device release. This works well but we now access the ref counter twice so there's a race: all users might see a high count and decide to defer freeing

vhost checked the counter within the refcnt before decrementing. It really wanted to know that it is the one that has the last reference, as a way to batch freeing resources a bit more efficiently. Note: we only let refcount go to 0 on device release. This works well but we now access the ref counter twice so there's a race: all users might see a high count and decide to defer freeing

On 3/14/06, Chris Lattner <sabre at nondot.org> wrote: > > > How exactly does this indicate X is no longer live? Is this internal > > code-generator logic/magic? > > No, this just prevents the GC from accidentally thinking that *X is live > through that pointer. The collector cannot distinguish between > pointers that are out of scope from those that aren't,

Hello, To do some testing with Asterisk installed the latest Asterisk @ Home in a Vmware system. All worked fine, I can access the web interface (AMP). I have setup the extention and X-Lite softphone according to the description in the Wike (http://www.voip-info.org/wiki-Asterisk+phone+xten+xlite). I can dial 200 (the softphone extention) and 1234 and they connect (the softphone shows this, as

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

Hello, I'm using Asterisk@Home. I'm still new to Asterisk, and trying to grasp it all. I'm wanting to do a simple setup of One SIP provider (Broadvoice) and 3 SIP Software Phones. I'm able to call the VoIP provided line fine and get dropped to the digital receptionist (or mailbox). However, when I try to send outbound calls I get "Error 503 Service Unavailable" and

I'm trying to call from XLite phone to PSTN (I've tried this from internet and from local network the same) The Xlite doesn't write that it is connected but receives excelent audio. At the other end comes only noise. Some times only for a second you can here the caller voice , but this was only one time :) I saw with ethereal that UDP packets are coming and going to the asterisk

Hi all, I've been running Asterisk with a TDM400P for about 6months, no problems. 2 in/outgoing analog lines, one analog phone. Recently I was messing with the XTEN client, got to finagling with things, and not knowing what was wrong I upgraded from 1.0.7 to 1.0.9 (both asterisk + zaptel). I was testing various things, and found everything worked except outgoing calls. So I checked

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

On Thu, Mar 12, 2015 at 11:54:10AM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On device hot-unplug, 9p/virtio currently will kfree channel while > > it might still be in use. > > > > Of course, it might stay used forever, so it's an extremely ugly hack, > > but it seems better than use-after-free that we

On Thu, Mar 12, 2015 at 11:54:10AM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On device hot-unplug, 9p/virtio currently will kfree channel while > > it might still be in use. > > > > Of course, it might stay used forever, so it's an extremely ugly hack, > > but it seems better than use-after-free that we

Hello, I have a TDM400P with 2x2 configuration of FXOs and FXSs. I set a test extension of '444' to dial out a specific zap trunk and call a local #. First time I call out to '444' everything works fine. If I hang up the call, and within 10 seconds dial the same number again, I get a fast busy. Seems it isn't letting go of the trunk or something, and I don't have a

"Michael S. Tsirkin" <mst at redhat.com> writes: > On device hot-unplug, 9p/virtio currently will kfree channel while > it might still be in use. > > Of course, it might stay used forever, so it's an extremely ugly hack, > but it seems better than use-after-free that we have now. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> I'll

"Michael S. Tsirkin" <mst at redhat.com> writes: > On device hot-unplug, 9p/virtio currently will kfree channel while > it might still be in use. > > Of course, it might stay used forever, so it's an extremely ugly hack, > but it seems better than use-after-free that we have now. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> I'll

It is sometimes useful to get the value of the reference count after decrement. For example, vhost wants to execute some periodic cleanup operations once number of references drops below a specific value, before it reaches zero (for efficiency). Add an API to do this atomically and efficiently using atomic_sub_return. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Greg, could

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

On Thu, Feb 16, 2023 at 03:09:02PM +0100, Laszlo Ersek wrote: > On 2/14/23 19:51, Richard W.M. Jones wrote: > > In the case that building the parameters to the Python event callback > > fails, args was returned as NULL. We immediately tried to call > > Py_INCREF on this which crashed. Returning NULL means the Python > > function threw an exception, so print the

On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things

I've written a reference-counting garbage collector for LLVM, but I'm still unclear on a few things. The following piece of code that appears on http://llvm.cs.uiuc.edu/docs/GarbageCollection.html is unclear: ;; As the pointer goes out of scope, store a null value into ;; it, to indicate that the value is no longer live. store %Object* null, %Object** %X ... How exactly does