similar to: How to dereference a pointer to a pointer

Displaying 20 results from an estimated 500 matches similar to: "How to dereference a pointer to a pointer"

2018 Dec 17
1
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
?On 12/17/18, 2:55 PM, "Michael S. Tsirkin" <mst at redhat.com> wrote: On Thu, Dec 13, 2018 at 11:24:28PM +0000, Steven Luong (sluong) via Virtualization wrote: > Folks, > > > > We came across a memory race condition between VPP vhost driver and the kernel > vhost. VPP is running a tap interface over vhost backend. In this case,
2018 Dec 13
2
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
Folks, We came across a memory race condition between VPP vhost driver and the kernel vhost. VPP is running a tap interface over vhost backend. In this case, VPP is acting as the vhost driver mode and the kernel vhost is acting as the vhost device mode. In the kernel vhost?s TX traffic direction which is VPP?s RX traffic direction, kernel vhost is the producer and VPP is the consumer. Kernel
2018 Dec 13
2
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
Folks, We came across a memory race condition between VPP vhost driver and the kernel vhost. VPP is running a tap interface over vhost backend. In this case, VPP is acting as the vhost driver mode and the kernel vhost is acting as the vhost device mode. In the kernel vhost?s TX traffic direction which is VPP?s RX traffic direction, kernel vhost is the producer and VPP is the consumer. Kernel
2012 Jul 19
1
kernel panic caused by zfs/sa.c
Hello, I'm experiencing a kernel panic that appears to be caused by zfs. No errors are making it into /var/log/messages, but here is the error message that appears on my screen after panic (transcribed): panic solaris assert BSWAP_32(sa_hdr_phys->sa_magic) == SA_MAGIC, file: /src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c, line 1262 I can reproduce this by
2008 Mar 04
1
grid.layout?
platform x86_64-unknown-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu status major 2 minor 6.2 year 2008 month 02 day
2008 Feb 24
2
Can DTrace display non-instrumented function argument counts and types?
Is it possible to use DTrace to display the number of arguments and their types for userland or kernel functions that are not explicitly instrumented or documented by their authors? We''re talking about functions provided by Veritas VxVM/VxFS and the like, and for example, we might want to try tracing I/Os from App => VxFS => VxVM => ssd driver to see where I/Os get aggregated or
2007 May 09
5
Refactor zfs_zget()
Hi, Since almost all operations in the FUSE low-level API identify files by inode number, I''ve been using zfs_zget() to get the corresponding znode/vnode in order to call the corresponding VFS function in zfs_vnops.c. However, there are some cases when zfs_zget() behaves slightly different than I need: 1) If zp->z_unlinked != 0 then zfs_zget() returns ENOENT. I need it to return
2001 Dec 19
1
rsync-2.5.0 getaddrinfo in AIX4.3?
Anyone have problems with getaddrinfo under AIX4.3? I have built 2.5.0 under linux, HP and VPP without too much in the way of problems. However, AIX4.3 version builds OK but doesn't execute getaddrinfo correctly. Any ideas? Terry Raggett ------------- -- +-------------------+----------------------------------+---------------------+ | Terry Raggett | |
2010 Jan 18
1
[PATCH 1/2] nv30-nv40: Rewrite primitive splitting and emission
The current code for primitive splitting and emission on pre-nv50 is severely broken. In particular: 1. Quads and lines are totally broken because "&= 3" should be "&= ~3" and similar for lines 2. Triangle fans and polygons are broken because the first vertex must be repeated for each split chunk 3. Line loops are broken because the must be converted to a line strip,
2018 Dec 17
0
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
On Thu, Dec 13, 2018 at 11:24:28PM +0000, Steven Luong (sluong) via Virtualization wrote: > Folks, > > > > We came across a memory race condition between VPP vhost driver and the kernel > vhost. VPP is running a tap interface over vhost backend. In this case, VPP is > acting as the vhost driver mode and the kernel vhost is acting as the vhost > device mode. > >
2006 Jul 07
2
Probe ID changes
OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311
2002 Feb 20
6
using GUI
A few days ago I loaded R version 1.4.1 to run on Windows 98 and haven't been able to find information on the GUI approach in the FAQs, R Reference Index, or Search Engine . Edit has an item that allows changing GUI preferences, and the Target path in the icon ends in Rgui.exe, so it appears that R for Windows does include using the GUI approach. In S-Plus I wrote a application with
2008 Jan 16
1
Non linear regression with 2 explanatory variables
Hello! I want to do a non-linear regression with 2 explanatory variables (something like : length ~ a * time * exp( b* temperature)), having a data set (length, time, temperature). Which function could I use (I tried nls but I think it doesn't work) Thanks a lot! Janice
2004 Dec 06
1
Gam() function in R
Unfortunately that's not really an R question. I recommend that you read up on the statistical methods underneath. One that I'd wholeheartedly recommend is Prof. Harrell's `Regression Modeling Strategies'. [BTW, there are now two implementations of gam() in R: one in `mgcv', which is fairly different from that in `gam'. I'm guessing you're referring to the one
2007 Aug 29
6
How do I look up syscall name
I''m using a fbt probe where I get a system call id as an argument, how do I look up the name of it? At the moment I''m post-processing the output using /etc/name/to_sysnum but that doesn''t feel right :) cheers, /Martin -- This message posted from opensolaris.org
2011 Apr 06
2
Limiting dtrace depth
If I use a simple dtrace script such as this: fbt::somefunc:entry{self->trace=1;} fbt::somefunc:return{self->trace=0;} fbt:::entry{} fbt:::return{printf("%lx", arg1);} then it will descend to whatever depth is necessary If I want to limit it to say 3 functions deep, how can I do that? The quick answer I want to use is to do "self->depth++" on each entry and then
2006 Jun 30
2
Qs. on fbt::copystr: probe
Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf
2018 Nov 01
2
CentOS 7.6 and Xen 4.6
Hey all, In order to make sure SIG content is "fresh", whenever a new version of CentOS comes out, content is discarded automatically unless SIG chairs specifically request it to be moved over. At the moment, Xen has three repos that are under consideration to be moved up: virt/x86_64/xen-46 virt/x86_64/xen-48 virt/x86_64/xen-410 I'll request xen-48 and xen-410 to be updated for
2007 Dec 25
6
what is differenct between syscall::write:entry fbt::write:entry
what is differenct between syscall::write:entry fbt::write:entry are the two probe fires at the same place. -- This message posted from opensolaris.org
2007 Jul 11
5
Error trying to count return points in functions.
Whilst trying out some D to get an insight into what is the most common reason for a given function to return, I have bumped into an error I don''t understand. The first take on what I was trying to do was: # dtrace -n ''fbt:ip:ip_input:return{@home[arg0] = count();}'' and all was well. The next step was: # dtrace -n