Displaying 20 results from an estimated 100 matches similar to: "[PATCH] virtio: console: Unlock vqs while freeing buffers"
2016 Oct 25
0
[PATCH] virtio: console: Unlock vqs while freeing buffers
On (Tue) 11 Oct 2016 [12:05:15], Matt Redfearn wrote:
> Commit c6017e793b93 ("virtio: console: add locks around buffer removal
> in port unplug path") added locking around the freeing of buffers in the
> vq. However, when free_buf() is called with can_sleep = true and rproc
> is enabled, it calls dma_free_coherent() directly, requiring interrupts
> to be enabled. Currently
2016 Jan 27
1
[v3,11/41] mips: reuse asm-generic/barrier.h
On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote:
> So you need to build a different kernel for some types of MIPS systems?
Yes. We can't really do without. Classic MIPS code is not relocatable
without the complexity of PIC code as used by ELF DSOs - and their
performanc penalty. Plus we have a number of architecture revisions
ovr the decades, big and little endian, 32
2016 Jan 27
1
[v3,11/41] mips: reuse asm-generic/barrier.h
On Thu, Jan 14, 2016 at 04:47:53PM -0800, Paul E. McKenney wrote:
> So you need to build a different kernel for some types of MIPS systems?
Yes. We can't really do without. Classic MIPS code is not relocatable
without the complexity of PIC code as used by ELF DSOs - and their
performanc penalty. Plus we have a number of architecture revisions
ovr the decades, big and little endian, 32
2020 Apr 07
0
[vhost:vhost 32/44] drivers/remoteproc/remoteproc_sysfs.c:55:2: error: implicit declaration of function 'kfree'; did you mean 'vfree'?
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost
head: 4e6ebec0de18aaea5f5f814b25bfcae3751c6369
commit: 013a472de94693ba05696d59e7df3224c20a22e6 [32/44] virtio: stop using legacy struct vring in kernel
config: x86_64-randconfig-s1-20200407 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
git checkout
2016 Nov 01
0
[PULL] virtio: tests, cleanups and fixes
The following changes since commit a909d3e636995ba7c349e2ca5dbb528154d4ac30:
Linux 4.9-rc3 (2016-10-29 13:52:02 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 75bfa81bf0897ba87f1e1b9b576a07536029b86a:
virtio_ring: mark vring_dma_dev inline (2016-10-31 00:40:08 +0200)
2016 Nov 01
0
[PULL] virtio: tests, cleanups and fixes
The following changes since commit a909d3e636995ba7c349e2ca5dbb528154d4ac30:
Linux 4.9-rc3 (2016-10-29 13:52:02 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 75bfa81bf0897ba87f1e1b9b576a07536029b86a:
virtio_ring: mark vring_dma_dev inline (2016-10-31 00:40:08 +0200)
2006 Nov 23
1
BUG: warning at kernel/softirq.c:141
Hello ext3-users,
we have an oopsy situation here:
we have 4 machines: 3 client nodes, 1 master: the master holds a fairly
big repository of small files. The repo's current size is ~40GB
with ~1.2 M files in ~100 directories. Now, we like to rsync changes
from the master to the client nodes, which is working perfectly for 2
nodes, but our 3rd node oopses "sometimes", rendering
2006 Mar 04
2
Problem compiling ztdummy on centos 4, 2.6 kernel
Hi all,
I hope everyone is doing well. I just joined the list, and I've really
enjoyed all I have read about asterisk so far. Unfortunately, I'm having a
bit of trouble implementing this thing :).
By the way ... I did my best to search the forums, and also to use google
extensively, and while I have found pages with people with the same problem,
... The fix suggested on those sites,
2016 Jun 06
2
[PATCH v2] Revert "drm/nouveau/device/pci: set as non-CPU-coherent on ARM64"
From: Robin Murphy <robin.murphy at arm.com>
This reverts commit 1733a2ad36741b1812cf8b3f3037c28d0af53f50.
There is apparently something amiss with the way the TTM code handles
DMA buffers, which the above commit was attempting to work around for
arm64 systems with non-coherent PCI. Unfortunately, this completely
breaks systems *with* coherent PCI (which appear to be the majority).
2016 Apr 29
1
[PATCH] Revert "drm/nouveau/device/pci: set as non-CPU-coherent on ARM64"
This reverts commit 1733a2ad36741b1812cf8b3f3037c28d0af53f50.
There is apparently something amiss with the way the TTM code handles
DMA buffers, which the above commit was attempting to work around for
arm64 systems with non-coherent PCI. Unfortunately, this completely
breaks systems *with* coherent PCI (which appear to be the majority).
Booting a plain arm64 defconfig + CONFIG_DRM +
2003 Aug 26
0
INTERNAL ERROR: Signal 11 in pid 5457 (3.0.0beta3)
By logging into a smbd server with the username "HAENGINEERS\KMR", we are
able to cause a smbd panic every time. Other usernames
("HAENGINEERS\_TestME") work.
The stack trace is below, full logs and smb.conf are available on request
(don't want to saturate the list.)
I can't post to bugzilla as I can't register a new account as my incoming
mail is crippled by
2023 Sep 06
0
[PATCH] virtio-mmio: fix memory leak of vm_dev
On Tue, Sep 05, 2023 at 09:42:28AM +0000, Maximilian Heyne wrote:
> With the recent removal of vm_dev from devres its memory is only freed
> via the callback virtio_mmio_release_dev. However, this only takes
> effect after device_add is called by register_virtio_device. Until then
> it's an unmanaged resource and must be explicitly freed on error exit.
>
> This bug was
2009 Sep 09
4
Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12.
Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed
on F12 before loading under Xen 3.4.1.
Dmesg log looks similar to Michael Yuong''s ''rc7.git4'' kernel for F12.
Boris.
--- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris
2012 Jul 10
0
[LLVMdev] Unable to do even basic Clang tutorial
Hi Ashok,
$ cd bin/bin
$ ./llvm-config --ldflags --libs
-L/home/ubuntu/bin/lib -ldl -lpthread
-lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMMCDisassembler -lLLVMMCParser -lLLVMInstrumentation -lLLVMInterpreter
2008 Aug 28
0
Error while cross compiling libvorbis 1.2.0
Dear All,
I am trying to cross compile the dependencies of ices for arm linux. I
have been able to compile libxml2 (2.6.32) and libogg (1.1.3)
successfully but I am getting stuck at compiling libvorbis (1.2.0).
Making install in examples
make[1]: Entering directory `/home/sr/armlinux/stream/libvorbis-1.2.0/examples'
/bin/bash ../libtool --tag=CC --mode=link
/usr/local/arm/bin/arm-linux-gcc
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You will need to link to the LLVM/clang libraries. To get the correct
flags, you can run:
./llvm-config --ldflags --libs
and use the flags reported.
On 7/10/2012 11:35 AM, NY Knicks Fan wrote:
> OK. Thanks. I now get the following error (which appears to be a
> problem w/ the tutorial itself?):
>
> $ /home/ubuntu/bin/bin/clang++ -I /home/ubuntu/bin/include/
>
2012 Jul 10
2
[LLVMdev] Unable to do even basic Clang tutorial
You need to link in the libclang* as well.
On 7/10/2012 1:22 PM, NY Knicks Fan wrote:
> Hi Ashok,
>
> $ cd bin/bin
> $ ./llvm-config --ldflags --libs
> -L/home/ubuntu/bin/lib -ldl -lpthread
> -lLLVMAsmParser -lLLVMTableGen -lLLVMDebugInfo -lLLVMX86Disassembler
> -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter
> -lLLVMX86Desc -lLLVMX86Info
2019 Apr 09
0
[RFC PATCH 02/12] virtio/s390: DMA support for virtio-ccw
On Tue, 9 Apr 2019 13:29:27 +0200
Halil Pasic <pasic at linux.ibm.com> wrote:
> On Tue, 9 Apr 2019 11:57:43 +0200
> Cornelia Huck <cohuck at redhat.com> wrote:
>
> > On Fri, 5 Apr 2019 01:16:12 +0200
> > Halil Pasic <pasic at linux.ibm.com> wrote:
> >
> > > Currently we have a problem if a virtio-ccw device has
> > >
2016 Aug 15
1
v4.8-rc2 crashes while probing nvidia graphics card on arm64
Hi,
While trying out v4.8-rc2 on Juno r2 (arm64), I ran into the following
crash when probing the nvidia graphics card attached to the PCIe
slot. So I tried rc1 and got the same crash. The card probes without any
errors on v4.7.
Anybody familiear with the recent changes knows what might have led to
the below crashlog?
Thanks,
Punit
------------->8-------------
[ 2.996678] [drm]
2016 Jun 06
0
[PATCH v2] Revert "drm/nouveau/device/pci: set as non-CPU-coherent on ARM64"
On 06/06/16 08:11, Alexandre Courbot wrote:
> From: Robin Murphy <robin.murphy at arm.com>
>
> This reverts commit 1733a2ad36741b1812cf8b3f3037c28d0af53f50.
>
> There is apparently something amiss with the way the TTM code handles
> DMA buffers, which the above commit was attempting to work around for
> arm64 systems with non-coherent PCI. Unfortunately, this completely