search for: deivces

Hello all, I recently ran over following issue ( the description is out of necessity bit lengthy): I have corrupted partition with ext3 filesystem oni t, fortunately enough partition was mirrored, so that I was able to dd the the mirroed partiton to the file like this: dd bs=512 if=/dev/<where_the_mirrored_partition_is> of=some_file and write the content to the primary partition like this:

On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > This object is used both by fuse_connection as well virt device. So make > this object reference counted and that makes it easy to define life cycle > of the object. > > Now deivce can be removed while filesystem is still mounted. This will > cleanup all the virtqueues but virtio_fs object will still be around and

On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > This object is used both by fuse_connection as well virt device. So make > this object reference counted and that makes it easy to define life cycle > of the object. > > Now deivce can be removed while filesystem is still mounted. This will > cleanup all the virtqueues but virtio_fs object will still be around and

Some deivces do not free the old tx skbs immediately after it has been sent (usually in tx interrupt). One such example is virtio-net which optimizes for virt and only free the possible old tx skbs during the next packet sending. This would lead the pktgen to wait forever in the refcount of the skb if no other...

Some deivces do not free the old tx skbs immediately after it has been sent (usually in tx interrupt). One such example is virtio-net which optimizes for virt and only free the possible old tx skbs during the next packet sending. This would lead the pktgen to wait forever in the refcount of the skb if no other...

Dear Andrew Tridgell and Samba Team, You have done a wonderful job in providing an excellent piece of software. I am interested in porting smbclient to Handheld device, mostly as a hobby. Please see my website http://vieka.com/. Because some of the Handheld OSs don't have the ability to access Windows share resource, specifically, the new Pocket PC by Microsoft, I would like to add this

On Fri, Sep 06, 2019 at 01:03:09PM +0100, Stefan Hajnoczi wrote: > On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > > This object is used both by fuse_connection as well virt device. So make > > this object reference counted and that makes it easy to define life cycle > > of the object. > > > > Now deivce can be removed while filesystem is still

...uf, index, priv->cqe_size) + factor; > ``` > > It seems that although they have a completion > queue, they are still using the ring in order. I guess so (at least from the above bits). Git grep -i "out of order" in drivers/net gives some hints. Looks like there're few deivces do this. > I guess maybe storage device may want OOO. Right, some iSCSI did. But tracking them elsewhere is not only for OOO. Spec said: for element address " In a used descriptor, Element Address is unused. " for Next flag: " For example, if descriptors are used in the sa...

...uf, index, priv->cqe_size) + factor; > ``` > > It seems that although they have a completion > queue, they are still using the ring in order. I guess so (at least from the above bits). Git grep -i "out of order" in drivers/net gives some hints. Looks like there're few deivces do this. > I guess maybe storage device may want OOO. Right, some iSCSI did. But tracking them elsewhere is not only for OOO. Spec said: for element address " In a used descriptor, Element Address is unused. " for Next flag: " For example, if descriptors are used in the sa...

These data structures should go away when virtio_fs object is going away. When deivce is going away, we need to just make sure virtqueues can go away and after that none of the code accesses vq and all the requests get error. So allocate memory for virtio_fs and virtio_fs_vq normally and free it at right time. This patch still frees up memory during device remove time. A later patch will make

On Sun, Sep 08, 2019 at 07:10:03PM +0800, piaojun wrote: > > > On 2019/9/6 3:48, Vivek Goyal wrote: > > This object is used both by fuse_connection as well virt device. So make > > this object reference counted and that makes it easy to define life cycle > > of the object. > > > > Now deivce can be removed while filesystem is still mounted. This will >

Hi folks I seted up the asterisk with an active ISDN B1 AVM Card (german vendor) and it works fine, various SIP clients (IP fon snom, xlite under MacOSX) and also incoming and outgoing connectins. Ok. No problem. After that I configured a CP7940G with a MGCP IOS. It's connected to the asterisk too via switch. No NAT deivce between. And of course, I can call out to PSTN and also to one of the

Currently it is assumed PCI device BAR access < 4G memory. If there is such a device whose BAR size is larger than 4G, it must access > 4G memory address. This patch enable the 64bits big BAR support on hvmloader. v3 changes from v2: - Remain original print information v2 changes from v1 as comments by Jan. 1) Set Dynamic MMIO high memory address instead of a fixed number 640G 2) Mask

This object is used both by fuse_connection as well virt device. So make this object reference counted and that makes it easy to define life cycle of the object. Now deivce can be removed while filesystem is still mounted. This will cleanup all the virtqueues but virtio_fs object will still be around and will be cleaned when filesystem is unmounted and sb/fc drops its reference. Removing a

...> ``` >>> >>> It seems that although they have a completion >>> queue, they are still using the ring in order. >> I guess so (at least from the above bits). Git grep -i "out of order" in >> drivers/net gives some hints. Looks like there're few deivces do this. >> >>> I guess maybe storage device may want OOO. >> Right, some iSCSI did. >> >> But tracking them elsewhere is not only for OOO. >> >> Spec said: >> >> for element address >> >> " >> In a used descriptor, Ele...

...> ``` >>> >>> It seems that although they have a completion >>> queue, they are still using the ring in order. >> I guess so (at least from the above bits). Git grep -i "out of order" in >> drivers/net gives some hints. Looks like there're few deivces do this. >> >>> I guess maybe storage device may want OOO. >> Right, some iSCSI did. >> >> But tracking them elsewhere is not only for OOO. >> >> Spec said: >> >> for element address >> >> " >> In a used descriptor, Ele...

Hi folks, i have a problem to boot an Ubuntu CD in a hvm-enabled machine. I get a black screen when connecting via vnc to the virtual machine. When i change the line cdrom= to some other CD (grml Live CD, Windows CD, other ones) it runs fine. But any Ubuntu CD (kubuntu alternative, ubuntu server, ubuntu desktop) i get the mentioned error. I tried using sdl (no window opens) and with

Hi, Michael Tsirkin pointed out issues w.r.t various locking related TODO items and races w.r.t device removal. In this first round of cleanups, I have taken care of most pressing issues. These patches apply on top of following. git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#virtiofs-v4 I have tested these patches with mount/umount and device removal using qemu monitor. For

Unable to connect to my HVM # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3869 2 r----- 368.6 vm00 45 128 1 -b---- 62.3 The vm00 changes state from "r" to "b" after about a minute. (I have a fedora dvd in the drive.) #cat

...tor; > > ``` > > > > It seems that although they have a completion > > queue, they are still using the ring in order. > > I guess so (at least from the above bits). Git grep -i "out of order" in > drivers/net gives some hints. Looks like there're few deivces do this. > > > I guess maybe storage device may want OOO. > > Right, some iSCSI did. > > But tracking them elsewhere is not only for OOO. > > Spec said: > > for element address > > " > In a used descriptor, Element Address is unused. > "...