search for: doorbells

Given the need for 4K doorbell such that QEMU can easily map, ect, and assuming that I have a HW device which exposes 2 VQ's, with a notification area off of BAR3, offset=whatever, notifier_multiplier=4, we don't need to have 2 x 4K pages mapped into the VM for both doorbells do we? The guest driver would ring DB0 at BAR4+offset, and DB1 at BAR4+offset+(4*1). The 4K per DB is useful how? This allows for QEMU trapping of individual DBs, that can then be used to do what, just forward the DBs via some other scheme - this makes sense for non-HW related Virtio devices I gue...

On 2020/5/29 ??5:16, Mika Penttil? wrote: > Hi, > > On 29.5.2020 11.03, Jason Wang wrote: >> Currently the doorbell is relayed via eventfd which may have >> significant overhead because of the cost of vmexits or syscall. This >> patch introduces mmap() based doorbell mapping which can eliminate the >> overhead caused by vmexit or syscall. > > Just wondering.

...idxListItem; + uint32_t privFlags; + bool runDelayed; + vmci_callback notifyCB; + void *clientData; + wait_queue_head_t destroyEvent; + atomic_t active; /* Only used by guest personality */ +}; + +/* The VMCI index table keeps track of currently registered doorbells. */ +static struct dbell_index_table { + spinlock_t lock; /* Index table lock */ + struct list_head entries[VMCI_DOORBELL_INDEX_TABLE_SIZE]; +} vmciDoorbellIT; + +/* + * The maxNotifyIdx is one larger than the currently known bitmap index in + * use, and is used to determine how much of...

...idxListItem; + uint32_t privFlags; + bool runDelayed; + vmci_callback notifyCB; + void *clientData; + wait_queue_head_t destroyEvent; + atomic_t active; /* Only used by guest personality */ +}; + +/* The VMCI index table keeps track of currently registered doorbells. */ +static struct dbell_index_table { + spinlock_t lock; /* Index table lock */ + struct list_head entries[VMCI_DOORBELL_INDEX_TABLE_SIZE]; +} vmciDoorbellIT; + +/* + * The maxNotifyIdx is one larger than the currently known bitmap index in + * use, and is used to determine how much of...

Hi, I am trying to connect a doorbell to a Xorcom device. And the setup is quite simple. But when I push the doorbell all I see on the asterisk cli is: -- Starting simple switch on 'Zap/11-1' [Apr 2 13:00:40] DEBUG[8771]: chan_dahdi.c:6180 ss_thread: not enough digits (and no ambiguous match)... -- Hungup 'Zap/11-1' I defined the extension s,h,i,t,T etc... in my context. Any

Currently the doorbell is relayed via eventfd which may have significant overhead because of the cost of vmexits or syscall. This patch introduces mmap() based doorbell mapping which can eliminate the overhead caused by vmexit or syscall. To ease the userspace modeling of the doorbell layout (usually virtio-pci), this patch starts from a doorbell per page model. Vhost-vdpa only support the

> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com] > Sent: Wednesday, February 14, 2018 10:54 PM > > The virtio IOMMU is a para-virtualized device, allowing to send IOMMU > requests such as map/unmap over virtio-mmio transport without > emulating > page tables. This implementation handles ATTACH, DETACH, MAP and > UNMAP > requests. > > The

> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com] > Sent: Wednesday, February 14, 2018 10:54 PM > > The virtio IOMMU is a para-virtualized device, allowing to send IOMMU > requests such as map/unmap over virtio-mmio transport without > emulating > page tables. This implementation handles ATTACH, DETACH, MAP and > UNMAP > requests. > > The

Hi, Does anybody know of a VoIP compatible doorbell or door intercom unit? I've contemplated buying a cheap SIP phone, ripping it apart, and putting it inside an IP66 sealed unit... It would need: - At least one speed-dial key, or some way to make every button dial the same extension number - PoE (power over ethernet), so I can power it off the central switch - cheap enough to rip apart

> From: Tian, Kevin > Sent: Thursday, March 22, 2018 6:06 PM > > > From: Robin Murphy [mailto:robin.murphy at arm.com] > > Sent: Wednesday, March 21, 2018 10:24 PM > > > > On 21/03/18 13:14, Jean-Philippe Brucker wrote: > > > On 21/03/18 06:43, Tian, Kevin wrote: > > > [...] > > >>> + > > >>> +#include

...vironments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An interrupt handler for shutting down the partition upon receiving the shutdown doorbell from a manager partition 4. A kernel interface for receiving callbacks when a managed partition shuts down. Signed-off-by: Timur Tabi <timur at freescale.com> --- Documentation/ioctl/ioctl-n...

...vironments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An interrupt handler for shutting down the partition upon receiving the shutdown doorbell from a manager partition 4. A kernel interface for receiving callbacks when a managed partition shuts down. Signed-off-by: Timur Tabi <timur at freescale.com> --- Documentation/ioctl/ioctl-n...

...vironments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An interrupt handler for shutting down the partition upon receiving the shutdown doorbell from a manager partition 4. A kernel interface for receiving callbacks when a managed partition shuts down. Signed-off-by: Timur Tabi <timur at freescale.com> --- drivers/Kconfig...

...vironments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An interrupt handler for shutting down the partition upon receiving the shutdown doorbell from a manager partition 4. A kernel interface for receiving callbacks when a managed partition shuts down. Signed-off-by: Timur Tabi <timur at freescale.com> --- drivers/Kconfig...

Hi Kevin, Thanks for the comments On 19/03/18 10:03, Tian, Kevin wrote: > BYPASS feature bit is not covered in "2.3.1/2.3.2/2.3.3"". Is it > intended? In my opinion BYPASS is a bit different from the other features: while the others are needed for correctness, this one is optional and even if the guest supports BYPASS, it should be allowed not to accept it. For security

Hi Kevin, Thanks for the comments On 19/03/18 10:03, Tian, Kevin wrote: > BYPASS feature bit is not covered in "2.3.1/2.3.2/2.3.3"". Is it > intended? In my opinion BYPASS is a bit different from the other features: while the others are needed for correctness, this one is optional and even if the guest supports BYPASS, it should be allowed not to accept it. For security

...overhead. A new vdpa_config_ops was introduced to report the location of the doorbell, vhost_vdpa may then choose to map the doorbell when: - The doorbell register is localted at page boundary - The doorbell register does not share page with non doorbell registers. With these two requriements, doorbells layout could be modelled more easily from guest (e.g Qemu's page-per-vq model) and it would be more safe to avoid exposing other registers to userspace directly. IFCVF was reported to support this feature but unfortuantely the one I used does not meet those requirements. So a new virtio-pci dr...

...overhead. A new vdpa_config_ops was introduced to report the location of the doorbell, vhost_vdpa may then choose to map the doorbell when: - The doorbell register is localted at page boundary - The doorbell register does not share page with non doorbell registers. With these two requriements, doorbells layout could be modelled more easily from guest (e.g Qemu's page-per-vq model) and it would be more safe to avoid exposing other registers to userspace directly. IFCVF was reported to support this feature but unfortuantely the one I used does not meet those requirements. So a new virtio-pci dr...

Hi, has anyone already set up a configuration between the doorbell Siedle DCA 612 and an Asterisk Server? I have used a Grandstream HT 286 to connect the doorbell and the asterisk. When I press the button, the phone ring and when I pick up the call I hear a beeping. At the door I hear nothing. According to the wiki, this doorbell should work with Asterisk, but I haven't found a dialplan

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser support is built into the xen0 kernel. I have similar setup with ext3 file systems working just fine, so I don''t think it is a setup problem. I have tried booting with and without and initrd file, booting with the original Linux distro initrd file, etc, but nothing seems to work. I recall seeing a thread about ReiserFS