在 2024/12/20 02:07, Dan Carpenter 写道:
On Thu, Dec 19, 2024 at 06:10:56PM +0300, Dan Carpenter wrote:
Mind to test it with KASAN enabled?
Anders is going to try that later and report back.
Anders ran it and emailed me. I was going to tell him to respond to
the thread but I decided to s
在 2024/12/20 01:40, Dan Carpenter 写道:
On Thu, Dec 19, 2024 at 10:44:12AM +1030, Qu Wenruo wrote:
在 2024/12/19 06:37, Qu Wenruo 写道:
在 2024/12/19 02:22, Naresh Kamboju 写道:
On Wed, 18 Dec 2024 at 17:33, Naresh Kamboju
wrote:
The following kernel crash noticed on qemu-arm64 while
在 2024/12/19 06:37, Qu Wenruo 写道:
在 2024/12/19 02:22, Naresh Kamboju 写道:
On Wed, 18 Dec 2024 at 17:33, Naresh Kamboju
wrote:
The following kernel crash noticed on qemu-arm64 while running the
Linux next-20241210 tag (to next-20241218) kernel built with
- CONFIG_ARM64_64K_PAGES=y
在 2024/12/19 02:22, Naresh Kamboju 写道:
On Wed, 18 Dec 2024 at 17:33, Naresh Kamboju wrote:
The following kernel crash noticed on qemu-arm64 while running the
Linux next-20241210 tag (to next-20241218) kernel built with
- CONFIG_ARM64_64K_PAGES=y
- CONFIG_ARM64_16K_PAGES=y
and running LT
On 2018年04月25日 21:18, Daniel P. Berrangé wrote:
> On Wed, Apr 25, 2018 at 05:48:42PM +0800, Qu Wenruo wrote:
>> Hi,
>>
>> When testing IO heavy work on my VM backed by Ryzen 1700 CPU, I turned
>> to brd modules, but surprisingly, the speed is even slower than so
Hi,
When testing IO heavy work on my VM backed by Ryzen 1700 CPU, I turned
to brd modules, but surprisingly, the speed is even slower than some HDD:
---
$ sudo modprobe brd rd_nr=1 rd_size=1048576
$ dd if=/dev/zero of=/dev/ram0 bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 byte
At 06/12/2017 10:05 PM, Keith Busch wrote:
On Fri, Jun 02, 2017 at 03:51:51PM +0200, Kevin Wolf wrote:
Am 02.06.2017 um 03:47 hat Qu Wenruo geschrieben:
When going through NVMe specification and hw/block/nvme.c,
I found that it seems that NVMe qemu implementation only support PRP
for sq
At 06/12/2017 10:05 PM, Keith Busch wrote:
On Fri, Jun 02, 2017 at 03:51:51PM +0200, Kevin Wolf wrote:
Am 02.06.2017 um 03:47 hat Qu Wenruo geschrieben:
When going through NVMe specification and hw/block/nvme.c,
I found that it seems that NVMe qemu implementation only support PRP
for sq
nvme controller supports it, it's never a bad idea to
enhance the check.
Signed-off-by: Qu Wenruo
---
hw/block/nvme.c | 11 +++
hw/block/nvme.h | 7 ++-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/hw/block/nvme.c b/hw/block/nvme.c
index fa1069160e..b2579
.
Signed-off-by: Qu Wenruo
---
hw/block/nvme.c | 16
hw/block/nvme.h | 122 +++-
2 files changed, 111 insertions(+), 27 deletions(-)
diff --git a/hw/block/nvme.c b/hw/block/nvme.c
index 381dc7c5fb..fa1069160e 100644
--- a/hw/block/nvme.c
Hi all,
After upgrading gcc from 6.3.1 to 7.1.1, qemu can't be compiled with gcc.
The error is:
--
CC block/blkdebug.o
block/blkdebug.c: In function 'blkdebug_refresh_filename':
block/blkdebug.c:693:31: error: '%s' directive output may be truncated
writing up to 4095 bytes into a re
At 06/02/2017 10:57 PM, Eric Blake wrote:
On 06/01/2017 11:08 PM, Qu Wenruo wrote:
Since we have already ignored ctags, ignoring .clangcomplete for
vim-clang_completion is quite reasonable for me.
(Not to mention vim-clang_completion provides better and more accurate
completion and definition
also makes sense to ignore per-project vim config file.
Signed-off-by: Qu Wenruo
---
.gitignore | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.gitignore b/.gitignore
index 55a001e3b8..c7c6eec0b6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -113,6 +113,8 @@
cscope.*
tags
TAGS
+.vim
Hi,
When going through NVMe specification and hw/block/nvme.c,
I found that it seems that NVMe qemu implementation only support PRP for
sq entry.
And NvmeRwCmd doesn't even use union to define DPTR, but just prp1 and prp2.
Although I am just a newbie, but I'm quite interested in NVMe and want
14 matches
Mail list logo
