similar to: How is Win/Dos syscalls implemented in Wine?

Hello again, (FYI, I took the liberty to change the topic since I started the former thread "How is Win/Dos syscalls implemented in Wine?" which I feel has gone a little bit off-topic) I had some more thoughts on the issue... I believe most wine users trust wine not to touch anything outside of its configured drive space. Malicious Linux/Unix syscalls could be embedded in windows

Hello * users I've problems with sound quality on zaphfc Asterisk works fine good sound quality. If I do "make load" in the bristuf.xx zaphfc dir then sound quality drops directly. Even if I don't load the chan_zap in the modules.conf I use this config on more (even old 400Mhz machines) and works correctly. Looks like an hardware problem but I can't find it. I don't

Hi, I was trying to determine how Wine captures syscalls, and I found this thread: http://www.winehq.org/pipermail/wine-users/2002-October/009077.html The answer was that Wine *doesn't* deal with syscalls, and relies on the application never directly making a syscall, but instead calling into the standard system libraries (Win32). Is this still true today? I'm surprised that Wine can

klibc fails to build on ia64 because it has neither fork nor the ppoll syscalls. This patch marks the former in SYSCALLS.def, and puts a guard wrapper around the ppoll definition in ppoll.c Should these calls return ENOSYS rather than simply not existing on some systems? If yes, please apply this and I'll follow up with a patch shortly that does ENOSYS for this and pselect at least.

There were a few unchecked syscalls in fish.c >From ba8b8b0684a03b6e6fbb939ed7e1cbf5e1000092 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Wed, 19 Aug 2009 10:01:07 +0200 Subject: [PATCH libguestfs] guestfish: detect a few more failed syscalls * fish/fish.c (issue_command): Detect/diagnose more failed syscalls. --- fish/fish.c | 26

Currently shutdown is nop for virtio devices, but the core code could remove things behind us such as MSI-X handler etc. For example in the case of virtio-scsi-pci, the device may still try to send interupts, which will be on IRQ lines seeing MSI-X disabled. Those interrupts will be unhandled, and may cause flood. Remove the device in "shutdown" callback to allow device drivers clean up

Currently shutdown is nop for virtio devices, but the core code could remove things behind us such as MSI-X handler etc. For example in the case of virtio-scsi-pci, the device may still try to send interupts, which will be on IRQ lines seeing MSI-X disabled. Those interrupts will be unhandled, and may cause flood. Remove the device in "shutdown" callback to allow device drivers clean up

Hi all I installed a tdm400p into a old p2 machine. I'm not able to see it under /proc/interupts or using lspci.. we removed all other cards. changed slots, forced irq to that slot.. etc etc. what is the min specs needed to get one of these cards running? thanks L --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term'

This patchset allow syscalls (flock, ipc, getuid, geteuid and ioctl), so openssl engines, e.g. OpenSSL-ibmca and OpenSSL-ibmpkcs11, can work and communicate with the crypto cards during ssh login. 1. The flock and ipc are allowed only for s390 architecture. They are needed for openCryptoki project (PKCS#11 implementation), as the ibmpkcs11 engine makes use of openCryptoki. For more information,

Hi, I have a v2000 compaq laptop. The realtek network and USB on this machine was not working. After adding to grub.conf "acpi=off apci=off noacpi noapic" the v2000 realtek started working and the USB worked fine... Fantastic! So I thought I would try those same options on my r4000 laptop. they had no effect.... This AMD turion 64 4000+ rating laptop is still running SLOWWW...

On Fri, 16 Aug 2013, Nicholas A. Bellinger wrote: > + spinlock_t lock; Remove the spinlock. > + unsigned nr_free; > + unsigned freelist[]; > +}; > + > +static inline void move_tags(unsigned *dst, unsigned *dst_nr, > + unsigned *src, unsigned *src_nr, > + unsigned nr) > +{ > + *src_nr -= nr; > + memcpy(dst + *dst_nr, src + *src_nr,

On Fri, 16 Aug 2013, Nicholas A. Bellinger wrote: > + spinlock_t lock; Remove the spinlock. > + unsigned nr_free; > + unsigned freelist[]; > +}; > + > +static inline void move_tags(unsigned *dst, unsigned *dst_nr, > + unsigned *src, unsigned *src_nr, > + unsigned nr) > +{ > + *src_nr -= nr; > + memcpy(dst + *dst_nr, src + *src_nr,

Sorry to reply to myself, but I wanted to expand this to -stable and add some more info... See the original post at the bottom of this msg. I just took the Smart 2/P and put it in slot1 (one of the shared Eisa/PCI slots.) Now the Dmesg output shows the "SMP: AP CPU" lines in a different order... They were: SMP: AP CPU# 3 Launched! SMP: AP CPU# 1 Launched! SMP: AP CPU# 2 Launched! now

On Wed, 03/11 10:06, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote: > > Currently shutdown is nop for virtio devices, but the core code could > > remove things behind us such as MSI-X handler etc. For example in the > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X

On Wed, 03/11 10:06, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote: > > Currently shutdown is nop for virtio devices, but the core code could > > remove things behind us such as MSI-X handler etc. For example in the > > case of virtio-scsi-pci, the device may still try to send interupts, > > which will be on IRQ lines seeing MSI-X

Hi, I am interested in the thoughts of the people who know the architecture of Asterisk quite well.. What I am interested in is the performace difference of Celeron vs P4 vs Xeon.. I know Intel marketing says that servers should be Xeon, Workstations should be P4 and desktops should be Celeron and they are priced to the specific target market.. I am on a tight budget and so I am looking for the

Hi all, Is there some documentation or some example on how to interpret the arg0 .. arg<n> for the aioread, aiowrite, aiowait syscalls? The system call name for all three seems to be "kaio". Michael === Michael Mueller ================== Tel. + 49 8171 63600 Fax. + 49 8171 63615 Web: http://www.michael-mueller-it.de ======================================

Dear R-gurus, I would like to zoom in a plot, e.g. I select a region on the x-axis and then I would like the ranges on the y-axis to change accordingly. Is it possible to do this with existing functions, or do I have to invent some data selection before plotting? See below a short example, where I select ylim with trial and error, which I want to avoid. Cheers, Henrik Andersson

Hello to all When my SNOM (300 or 320) loses Internet connectivity, it loses its Asterisk registration (ok, thats normal). But when the phone is back online, he doesn't try to register in Asterisk. I believe this happens to avoid flooding the private LANs when the Internet link is lost.... but the problem is that the phones don't try to re-register in the future.... Sometimes it stays

On Thu, 03/12 17:22, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2015 at 06:11:35PM +0800, Fam Zheng wrote: > > On Wed, 03/11 10:06, Michael S. Tsirkin wrote: > > > On Wed, Mar 11, 2015 at 04:09:17PM +0800, Fam Zheng wrote: > > > > Currently shutdown is nop for virtio devices, but the core code could > > > > remove things behind us such as MSI-X handler