search for: splitup

...t; create mode 100644 Documentation/devicetree/bindings/virtio/iommu.txt > create mode 100644 drivers/iommu/virtio-iommu.c > create mode 100644 include/uapi/linux/virtio_iommu.h This all looks good to me. Minor nits: - I think DEBUG mode is best just removed for now - Slightly wrong patch splitup causing a misaligned structure in uapi until all patches are applied. You should Cc Bjorn on the pci change - I'd like to see his ack on it being merged through my tree. And pls Cc the virtio-dev list on any virtio uapi changes. At a feature level I have some ideas for more features we cou...

...ndition false and we have a goto there which now can get us to end of loop and then exit. previously at least we would only exit on a break. Frankly trying to review it I get lost now. I also think repeated checking of empty_ring is not that problematic. But I don't insist on this specific splitup just pls make the code regular by moving stuff to sub-function. -- MST

...ndition false and we have a goto there which now can get us to end of loop and then exit. previously at least we would only exit on a break. Frankly trying to review it I get lost now. I also think repeated checking of empty_ring is not that problematic. But I don't insist on this specific splitup just pls make the code regular by moving stuff to sub-function. -- MST

...ight. With the patch, we will check and exit the loop if we exceeds the weight. Did I miss anything obvious? Thanks > > Frankly trying to review it I get lost now. > I also think repeated checking of empty_ring is not that > problematic. > But I don't insist on this specific splitup > just pls make the code regular by > moving stuff to sub-function. > >

...duplication correctly, but we can solve it just by adding functions. like i suggested. > > > > > Frankly trying to review it I get lost now. > > I also think repeated checking of empty_ring is not that > > problematic. > > But I don't insist on this specific splitup > > just pls make the code regular by > > moving stuff to sub-function. > > > >

Hi List, so first the basics. I''m running Arch Linux with 3.13-rc2, btrfs-progs 0.20rc1.3-2 from the repo and I''m using a SSD. So I was having kernel panics with my USB 3.0 Gigabit card and was trying to get a panic output. These panics are intermittent and most often happen while using Chromium. Anyway so my system paniced while I was in Chromium. After the reboot Chromium

On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >> When the rx buffer is too small for a packet, we will discard the vq >> descriptor and retry it for the next packet: >> >> while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, >> &busyloop_intr))) { >> ... >> /* On

On 2019/4/26 ??1:52, Michael S. Tsirkin wrote: > On Thu, Apr 25, 2019 at 03:33:19AM -0400, Jason Wang wrote: >> When the rx buffer is too small for a packet, we will discard the vq >> descriptor and retry it for the next packet: >> >> while ((sock_len = vhost_net_rx_peek_head_len(net, sock->sk, >> &busyloop_intr))) { >> ... >> /* On

...GE_RESOURCELOAD for fb->texture reads. wined3d: Delay render target activation. wined3d: Restore the gamma when destroying the swapchain. wined3d: Correct an off-by-one error in constant dirtification. wined3d: Remove an unneeded atifs hack. wined3d: Start the state splitup. wined3d: Implement the state merger and start to use it. wined3d: Make the stream source application a regular state function. wined3d: Move stream source and vshader to misc and vertex pipeline tables. wined3d: Move material application to the vertex pipeline. wined3...

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the