exec: fetch the alignment of Linux devdax pmem character device nodes
PATCH 1/1 exec: fetch the alignment of Linux devdax pmem character device nodes
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.
It also fixes the problem that mmap() returns failure in qemu_ram_mmap() when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.
--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)
exec.c +45 -1
@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path =g_strdup_printf ("/sys/dev/char/%d:%d/subsystem" , +major (st.st_rdev),minor (st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); + +if (g_file_get_contents (align_path, &align_str,NULL ,NULL )) { +return g_ascii_strtoll (align_str,NULL ,0 ); + } + } + } +#endif /* defined(__linux__) */ + +return align; +} + static int file_ram_open(const char *path, const char *region_name, bool *created,
@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, {RAMBlock *new_block;Error *local_err =NULL ; -int64_t file_size; +int64_t file_size, file_align;/* Just support these ram flags by now. */ assert ((ram_flags & ~(RAM_SHARED |RAM_PMEM )) ==0 );
@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr,return NULL ; } + file_align =get_file_align (fd); +if (file_align >0 && mr && file_align > mr->align) { +error_setg (errp,"backing store align 0x%" PRIx64 +" is larger than 'align' option 0x" RAM_ADDR_FMT , + file_align, mr->align); +return NULL ; + } + new_block =g_malloc0 (sizeof (*new_block)); new_block->mr = mr; new_block->used_length = size;
Signature · 1 line
2.17.1
Ping.
Any comments are appreciated.
Hi Paolo, Richard,
Any comments about this ?
Thanks,
Jingqi
Quoted 88 lines · Jingqi
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +45
-1@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path =g_strdup_printf ("/sys/dev/char/%d:%d/subsystem" , +major (st.st_rdev),minor (st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); + +if (g_file_get_contents (align_path, &align_str,NULL ,NULL )) { +return g_ascii_strtoll (align_str,NULL ,0 ); + } + } + } +#endif /* defined(__linux__) */ + +return align; +} + static int file_ram_open(const char *path, const char *region_name, bool *created,@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, {RAMBlock *new_block;Error *local_err =NULL ; -int64_t file_size; +int64_t file_size, file_align;/* Just support these ram flags by now. */ assert ((ram_flags & ~(RAM_SHARED |RAM_PMEM )) ==0 );@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr,return NULL ; } + file_align =get_file_align (fd); +if (file_align >0 && mr && file_align > mr->align) { +error_setg (errp,"backing store align 0x%" PRIx64 +" is larger than 'align' option 0x" RAM_ADDR_FMT , + file_align, mr->align); +return NULL ; + } + new_block =g_malloc0 (sizeof (*new_block)); new_block->mr = mr; new_block->used_length = size;
Quoted 7 lines · Jingqi
Ping.
Any comments are appreciated.
Hi Paolo, Richard,
Any comments about this ?
I was hoping to get a review from someone else because I have no way to test it. But I've now queued the patch, thanks.
Paolo
Quoted 100 lines
Thanks,
Jingqi
Quoted 93 lines · Jingqi
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>---
exec.c| 46 +++++++++++++++++++++++++++++++++++++++++++++-1 file changed, 45 insertions(+), 1 deletion(-)exec.c +24
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd) return size; } +static int64_t get_file_align(int fd) +{ + int64_t align = -1; +#if defined(__linux__) + struct stat st; + + if (fstat(fd, &st) < 0) { + return -errno; + } + + /* Special handling for devdax character devices */ + if (S_ISCHR(st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem", + major(st.st_rdev), minor(st.st_rdev)); + subsystem = g_file_read_link(subsystem_path, NULL); + + if (subsystem && g_str_has_suffix(subsystem, "/dax")) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path = g_strdup_printf("/sys/dev/char/%d:%d/device/align", + major(st.st_rdev),
minor(st.st_rdev));
+
+ if (g_file_get_contents(align_path, &align_str, NULL, NULL)) {
+ returng_ascii_strtoll(align_str, NULL, 0); + }
+ }
+ }exec.c +5
-0+#endif /* defined(__linux__) */ + + return align; +} +static int file_ram_open(const char *path, const char
*region_name, bool *created,exec.c +8
-1@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, { RAMBlock *new_block; Error *local_err = NULL; - int64_t file_size; + int64_t file_size, file_align; /* Just support these ram flags by now. */ assert((ram_flags & ~(RAM_SHARED | RAM_PMEM)) == 0);@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, return NULL; } + file_align = get_file_align(fd); + if (file_align > 0 && mr && file_align > mr->align) { + error_setg(errp, "backing store align 0x%" PRIx64 + " is larger than 'align' option 0x" RAM_ADDR_FMT, + file_align, mr->align); + return NULL; + } + new_block = g_malloc0(sizeof(*new_block)); new_block->mr = mr;
new_block->used_length= size;
Quoted 4 lines · Paolo Bonzini
Quoted 2 lines · Jingqi
Ping.
Quoted 8 lines
Quoted 5 lines
Any comments are appreciated.
Hi Paolo, Richard,
Any comments about this ?
I was hoping to get a review from someone else because I have no way to test it. But I've now queued the patch, thanks.
Does qemu run tests in a nested VM? The difficult aspect of testing devdax is that you need to boot your kernel with a special option or have existing memory ranges assigned to the device. Although, Joao had thoughts about allowing dynamic creation of device-dax instance by hot unplugging memory.
Quoted 89 lines
Paolo
Quoted 86 lines
Thanks,
Jingqi
Quoted 80 lines · Jingqi
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +24
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd) return size; } +static int64_t get_file_align(int fd) +{ + int64_t align = -1; +#if defined(__linux__) + struct stat st; + + if (fstat(fd, &st) < 0) { + return -errno; + } + + /* Special handling for devdax character devices */ + if (S_ISCHR(st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem", + major(st.st_rdev), minor(st.st_rdev)); + subsystem = g_file_read_link(subsystem_path, NULL); + + if (subsystem && g_str_has_suffix(subsystem, "/dax")) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path = g_strdup_printf("/sys/dev/char/%d:%d/device/align", + major(st.st_rdev),
minor(st.st_rdev));exec.c +2
-0+ + if (g_file_get_contents(align_path, &align_str, NULL,NULL)) {
exec.c +10
-1+ return g_ascii_strtoll(align_str, NULL, 0); + } + } + } +#endif /* defined(__linux__) */ + +return align; +} + static int file_ram_open(const char *path, const char *region_name, bool *created,@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, { RAMBlock *new_block;Error *local_err =NULL ; -int64_t file_size; +int64_t file_size, file_align;/* Just support these ram flags by now. */ assert ((ram_flags & ~(RAM_SHARED |RAM_PMEM )) ==0 );@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr,
Quoted 8 lines
Quoted 8 lines
exec.c RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, · line 2355
Quoted 8 lines
exec.c +5
-0return NULL ; } + file_align =get_file_align (fd); +if (file_align >0 && mr && file_align > mr->align) { +error_setg (errp,"backing store align 0x%" PRIx64 +" is larger than 'align' option 0x" RAM_ADDR_FMT , + file_align, mr->align); +return NULL ;
Is there any downside to just making the alignment value be the max of the device-dax instance align and the command line option? Why force someone to debug the option unnecessarily?
Quoted 4 lines · Dan Williams
Quoted 3 lines · Paolo Bonzini
Quoted 2 lines · Jingqi
Ping.
Quoted 9 lines
Quoted 8 lines
Quoted 5 lines
Any comments are appreciated.
Hi Paolo, Richard,
Any comments about this ?
I was hoping to get a review from someone else because I have no way to test it. But I've now queued the patch, thanks.
FWIW, I tested it (and didn't work) . Later found something odd wrt to the device path.
Paolo if it helps your future testing, you can have a device-dax with something like this:
efi_fake_mem=4G@16G:0x40000 # creates a dax0.0 device with sz 4G, 2M aligned
But it requires dax_hmem which is v5.5+. Or alternatively use memmap=4G!16G (and using ndctl create-namespace -r 0 -a <align>) and it creates pmem legacy device.
Quoted 6 lines
Does qemu run tests in a nested VM? The difficult aspect of testing devdax is that you need to boot your kernel with a special option or have existing memory ranges assigned to the device. Although, Joao had thoughts about allowing dynamic creation of device-dax instance by hot unplugging memory.
The idea was to get feature parity with hugetlbfs where you can assign a number of 2M/1G pages at runtime. Thus giving a more flexible manner of assigning memory to hmem.
This means we would create dax regions -- which can be sub-divided into dax devices -- dynamically by hotunpluging a memory%u device first and then reassigning it to dax_hmem driver (and thus marking it as 'soft-reserved'). Which could be given back to system-ram via dax_kmem. Naturally this assumes you can hot-unplug the memory block before assigning it to dax_hmem, which might be rather unpredictable. via kernel cmdline still is, though, the most deterministic manner of assigning memory say at a bigger page granularities (e.g. 1G).
But this is hotunplug-assign-to-hmem is still on paper, I haven't yet prototyped this to see where it all falls apart.
Quoted 85 lines
Quoted 85 lines
Quoted 85 lines · Jingqi
Quoted 84 lines
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +24
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd) return size; } +static int64_t get_file_align(int fd) +{ + int64_t align = -1; +#if defined(__linux__) + struct stat st; + + if (fstat(fd, &st) < 0) { + return -errno; + } + + /* Special handling for devdax character devices */ + if (S_ISCHR(st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem", + major(st.st_rdev), minor(st.st_rdev)); + subsystem = g_file_read_link(subsystem_path, NULL); + + if (subsystem && g_str_has_suffix(subsystem, "/dax")) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path = g_strdup_printf("/sys/dev/char/%d:%d/device/align", + major(st.st_rdev),
minor(st.st_rdev));exec.c +2
-0+ + if (g_file_get_contents(align_path, &align_str, NULL,NULL)) {
exec.c +11
-1+ return g_ascii_strtoll(align_str, NULL, 0); + } + } + } +#endif /* defined(__linux__) */ + +return align; +} + static int file_ram_open(const char *path, const char *region_name, bool *created,@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, { RAMBlock *new_block;Error *local_err =NULL ; -int64_t file_size; +int64_t file_size, file_align;/* Just support these ram flags by now. */ assert ((ram_flags & ~(RAM_SHARED |RAM_PMEM )) ==0 );@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, return NULL; } + file_align =get_file_align (fd); +if (file_align >0 && mr && file_align > mr->align) {
Quoted 9 lines
Quoted 4 lines
Quoted 4 lines
exec.c RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, · line 2355
Quoted 4 lines
exec.c +4
-0+error_setg (errp,"backing store align 0x%" PRIx64 +" is larger than 'align' option 0x" RAM_ADDR_FMT , + file_align, mr->align); +return NULL ;Is there any downside to just making the alignment value be the max of the device-dax instance align and the command line option? Why force someone to debug the option unnecessarily?
+1
Perhaps we can auto-detect that @align was not set and then we would set the max align value. But if user has set a value over command line we would validate it like Jingqi is doing above. Roughly, something like this just as a suggestion:
@@ -2354,11 +2354,16 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr,
}
file_align = get_file_align(fd);- if (file_align > 0 && mr && file_align > mr->align) {
- error_setg(errp, "backing store align 0x%" PRIx64
- " is larger than 'align' option 0x" RAM_ADDR_FMT,
- file_align, mr->align);
- return NULL;
+ if (file_align > 0 && mr) {
+ /* auto detect alignment if none is specified */
+ if (!mr->align)
+ mr->align = file_align;
+ if (file_align > mr->align) {
+ error_setg(errp, "backing store align 0x%" PRIx64
+ " is larger than 'align' option 0x" RAM_ADDR_FMT,
+ file_align, mr->align);
+ return NULL;
+ }
}
Quoted 10 lines · Paolo Bonzini
Quoted 7 lines · Jingqi
Ping.
Any comments are appreciated.
Hi Paolo, Richard,
Any comments about this ?
I was hoping to get a review from someone else because I have no way to test it. But I've now queued the patch, thanks.
Hi Paolo,
Thanks for your comments.
Hi Dan,
Can you help review this patch ?
Thanks,
Jingqi
Quoted 100 lines
Paolo
Quoted 98 lines
Thanks,
Jingqi
Quoted 93 lines · Jingqi
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +24
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd) return size; } +static int64_t get_file_align(int fd) +{ + int64_t align = -1; +#if defined(__linux__) + struct stat st; + + if (fstat(fd, &st) < 0) { + return -errno; + } + + /* Special handling for devdax character devices */ + if (S_ISCHR(st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem", + major(st.st_rdev), minor(st.st_rdev)); + subsystem = g_file_read_link(subsystem_path, NULL); + + if (subsystem && g_str_has_suffix(subsystem, "/dax")) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path = g_strdup_printf("/sys/dev/char/%d:%d/device/align", + major(st.st_rdev),
minor(st.st_rdev));
+
+ if (g_file_get_contents(align_path, &align_str, NULL, NULL)) {
+ returng_ascii_strtoll(align_str, NULL, 0); + }
+ }
+ }exec.c +13
-1+#endif /* defined(__linux__) */ + + return align; +} + static int file_ram_open(const char *path, const char *region_name, bool *created,@@ -2275,7 +2311,7 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, { RAMBlock *new_block; Error *local_err = NULL; - int64_t file_size; + int64_t file_size, file_align; /* Just support these ram flags by now. */ assert((ram_flags & ~(RAM_SHARED | RAM_PMEM)) == 0);@@ -2311,6 +2347,14 @@ RAMBlock *qemu_ram_alloc_from_fd(ram_addr_t size, MemoryRegion *mr, return NULL; } + file_align = get_file_align(fd); + if (file_align > 0 && mr && file_align > mr->align) { + error_setg(errp, "backing store align 0x%" PRIx64 + " is larger than 'align' option 0x" RAM_ADDR_FMT, + file_align, mr->align); + return NULL; + } + new_block = g_malloc0(sizeof(*new_block)); new_block->mr = mr; new_block->used_length = size;
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",
exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +
Perhaps, you meant instead:
/sys/dev/char/%d:%d/align
?
Quoted 6 lines · Joao Martins
Perhaps, you meant instead:
/sys/dev/char/%d:%d/align?
So it works with that change?
Paolo
Quoted 9 lines · Paolo Bonzini
Quoted 6 lines · Joao Martins
Perhaps, you meant instead:
/sys/dev/char/%d:%d/align?
So it works with that change?
Yeah.
Joao
Quoted 8 lines · Joao Martins
Quoted 7 lines · Paolo Bonzini
Quoted 6 lines · Joao Martins
Perhaps, you meant instead:
/sys/dev/char/%d:%d/align?
Hi Joao,
In my machine with real NVDIMM, the devdax device is as follows:
$ ll /dev/dax0.0 crw------- 1 root root 250, 6 3月 25 15:16 /dev/dax0.0
$ ls /sys/dev/char/250\:6/align ls: cannot access '/sys/dev/char/250:6/align': No such file or directory
$ ls /sys/dev/char/250\:6/device/align
/sys/dev/char/250:6/device/align
So:
The file of "/sys/dev/char/%d:%d/align" does not exist. It should be "/sys/dev/char/%d:%d/device/align".
Anyone has a real NVDIMM can help double check. Thanks.
Hi Dan,
You may have a real NVDIMM, in what directory is the 'align' file ?
Thanks,
Jingqi
Quoted 4 lines
Quoted 1 line
So it works with that change?
Yeah.
Joao
Quoted 19 lines · Jingqi
Quoted 8 lines · Joao Martins
Quoted 7 lines · Paolo Bonzini
Quoted 6 lines · Joao Martins
Perhaps, you meant instead:
/sys/dev/char/%d:%d/align?
Hi Joao,
In my machine with real NVDIMM, the devdax device is as follows:
$ ll /dev/dax0.0 crw------- 1 root root 250, 6 3月 25 15:16 /dev/dax0.0$ ls /sys/dev/char/250\:6/align ls: cannot access '/sys/dev/char/250:6/align': No such file or directory
Quoted 8 lines
$ ls /sys/dev/char/250\:6/device/align/sys/dev/char/250:6/device/align
So:
The file of "/sys/dev/char/%d:%d/align" does not exist. It should be "/sys/dev/char/%d:%d/device/align".
The 'align' (without the ../) was my mistake as I was testing with other wip patches.
Albeit, still retain my comment to 'device/align' as it is relying on an deprecated path, so perhaps we should look other alternatives.
I had the deprecated dax class disabled (DEV_DAX_PMEM_COMPAT=n), and 'device' does not exist on that cases.
Quoted 14 lines
Anyone has a real NVDIMM can help double check. Thanks.
Hi Dan,
You may have a real NVDIMM, in what directory is the 'align' file ?
Thanks,
Jingqi
Quoted 4 lines
Quoted 1 line
So it works with that change?
Yeah.
Joao
Quoted 58 lines · Joao Martins
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +Perhaps, you meant instead:
Quoted 2 lines
/sys/dev/char/%d:%d/align
Hmm, are you sure that's working? I expect the alignment to be found in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such file
The use of the /sys/dev/char/%d:%d/device is only supported by the deprecated /sys/class/dax. The current /sys/bus/dax device-model can be a drop in replacement as long as software is not written to the /sys/class sysfs layout, i.e. it uses ../ instead of device/ to walk to the region properties.
Quoted 56 lines · Dan Williams
Quoted 55 lines · Joao Martins
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +Perhaps, you meant instead:
Quoted 4 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 9 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
Quoted 7 lines
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.
I don't have the deprecated dax class enabled as could you tell, so the second case is what I was testing. Except it wasn't a namespace/nvdimm but rather an hmem device-dax.
'../align' though covers only one case? What about hmem which '../align' returns ENOENT; perhaps using '../dax_region/align' instead which is common to both? Albeit that wouldn't address the sub-division devices (that I mention above)
Quoted 5 lines
The current
/sys/bus/daxdevice-model can
be a drop in replacement as long as software is not written to the/sys/classsysfs layout, i.e. it uses ../ instead of device/ to walk to the region properties.
/nods
Quoted 84 lines · Joao Martins
Quoted 56 lines · Dan Williams
Quoted 55 lines · Joao Martins
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +Perhaps, you meant instead:
Quoted 4 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 9 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/alignQuoted 7 lines
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.
Quoted 7 lines
I don't have the deprecated dax class enabled as could you tell, so the second case is what I was testing. Except it wasn't a namespace/nvdimm but rather an hmem device-dax.
'../align' though covers only one case? What about hmem which '../align' returns ENOENT; perhaps using '../dax_region/align' instead which is common to both? Albeit that wouldn't address the sub-division devices (that I mention above)
Clearly a 5.1 patch then. :)
Paolo
Quoted 56 lines · Joao Martins
Quoted 55 lines · Dan Williams
Quoted 54 lines · Joao Martins
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +Perhaps, you meant instead:
Quoted 24 lines
Quoted 3 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 16 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.
Hi Dan,
Thanks for your comments.
Seems it is a mistake.
It should be: $(readlink -f /sys/dev/char/253\:263)/../../align
Quoted 7 lines
I don't have the deprecated dax class enabled as could you tell, so the second case is what I was testing. Except it wasn't a namespace/nvdimm but rather an hmem device-dax.
'../align' though covers only one case? What about hmem which '../align' returns ENOENT; perhaps using '../dax_region/align' instead which is common to both? Albeit that wouldn't address the sub-division devices (that I mention above)
Seems that you mean to use $(readlink -f /sys/dev/char/253\:263)/../../dax_region/align.
Right ?
Thanks,
Jingqi
Quoted 6 lines
Quoted 5 lines
The current
/sys/bus/daxdevice-model can
be a drop in replacement as long as software is not written to the/sys/classsysfs layout, i.e. it uses ../ instead of device/ to walk to the region properties./nods
Quoted 82 lines · Jingqi
Quoted 56 lines · Joao Martins
Quoted 55 lines · Dan Williams
Quoted 54 lines · Joao Martins
Quoted 41 lines · Jingqi Liu
If the backend file is devdax pmem character device, the alignment specified by the option 'align=NUM' in the '-object memory-backend-file' needs to match the alignment requirement of the devdax pmem character device.
This patch fetches the devdax pmem file 'align', so that we can compare it with the NUM of 'align=NUM'.
The NUM needs to be larger than or equal to the devdax pmem file 'align'.It also fixes the problem that
mmap()returns failure inqemu_ram_mmap()when the NUM of 'align=NUM' is less than the devdax pmem file 'align'.Cc Dan Williams <[email protected]>Signed-off-by Jingqi Liu <[email protected]>--- exec.c | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-)exec.c +16
-0@@ -1736,6 +1736,42 @@ static int64_t get_file_size(int fd)return size; } +static int64_t get_file_align (int fd) +{ +int64_t align =-1 ; +#if defined(__linux__) +struct stat st; + +if (fstat (fd, &st) <0 ) { +return -errno; + } + +/* Special handling for devdax character devices */ +if (S_ISCHR (st.st_mode)) { + g_autofree char *subsystem_path = NULL; + g_autofree char *subsystem = NULL; + + subsystem_path = g_strdup_printf("/sys/dev/char/%d:%d/subsystem",exec.c static int64_t get_file_size(int fd) · line 1764
Quoted 10 lines
exec.c +10
-0+ major(st.st_rdev), minor(st.st_rdev)); + subsystem =g_file_read_link (subsystem_path,NULL ); + +if (subsystem &&g_str_has_suffix (subsystem,"/dax" )) { + g_autofree char *align_path = NULL; + g_autofree char *align_str = NULL; + + align_path =g_strdup_printf ("/sys/dev/char/%d:%d/device/align" , +major (st.st_rdev),minor (st.st_rdev)); +Perhaps, you meant instead:
Quoted 24 lines
Quoted 3 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 16 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.
Quoted 8 lines
Hi Dan,
Thanks for your comments.
Seems it is a mistake.
It should be: $(readlink -f /sys/dev/char/253\:263)/../../align
Hmm, perhaps you have an extra '../' in the path? This works for me:
# ls $(readlink -f /sys/dev/char/252\:0/../align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../align 2097152 # cat /sys/dev/char/252\:0/../align 2097152
Quoted 4 lines
Quoted 4 lines
I don't have the deprecated dax class enabled as could you tell, so the second case is what I was testing. Except it wasn't a namespace/nvdimm but rather an hmem device-dax.
Quoted 9 lines
Quoted 3 lines
'../align' though covers only one case? What about hmem which '../align' returns ENOENT; perhaps using '../dax_region/align' instead which is common to both? Albeit that wouldn't address the sub-division devices (that I mention above)
Seems that you mean to use $(readlink -f
/sys/dev/char/253\:263)/../../dax_region/align.Right ?
An extra '../' ?
# ls $(readlink -f /sys/dev/char/252\:0/../dax_region/align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../dax_region/align 2097152 # cat /sys/dev/char/252\:0/../dax_region/align 2097152
For HMAT/hmem devdax, though, only 'dax_region/align' is available for now:
# ls $(readlink -f /sys/dev/char/252:0)/../align ls: cannot access /sys/devices/platform/hmem.0/dax0.0/../align: No such file or directory # ls $(readlink -f /sys/dev/char/252:0)/../dax_region/align /sys/devices/platform/hmem.0/dax0.0/../dax_region/align # cat $(readlink -f /sys/dev/char/252:0)/../dax_region/align 2097152
The 'dax_region/align' was just an idea mainly because it's common to both device-dax devices -- not sure how others feel about it.
Joao
Quoted 10 lines
Thanks,
Jingqi
Quoted 6 lines
Quoted 5 lines
The current
/sys/bus/daxdevice-model can
be a drop in replacement as long as software is not written to the/sys/classsysfs layout, i.e. it uses ../ instead of device/ to walk to the region properties./nods
Quoted 38 lines · Joao Martins
Quoted 29 lines · Jingqi
Quoted 4 lines · Joao Martins
Quoted 3 lines · Dan Williams
Quoted 2 lines · Joao Martins
Perhaps, you meant instead:
Quoted 24 lines
Quoted 3 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 16 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.Quoted 8 lines
Hi Dan,
Thanks for your comments.
Seems it is a mistake.
It should be: $(readlink -f /sys/dev/char/253\:263)/../../align
Quoted 8 lines
Hmm, perhaps you have an extra '../' in the path? This works for me:
# ls $(readlink -f /sys/dev/char/252\:0/../align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../align 2097152 # cat /sys/dev/char/252\:0/../align 2097152
Hi Joao,
Hmm, I need to have an extra '../' in the path. The details are as follows:
# ll /dev/dax2.0 crw------- 1 root root 251, 5 Mar 20 13:35 /dev/dax2.0 # uname -r 5.6.0-rc1-00044-gb19e8c684703 # readlink -f /sys/dev/char/251\:5/ /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0 # ls $(readlink -f /sys/dev/char/251\:5)/../align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../dax_region/align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../dax_region/align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../../align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../align # ls $(readlink -f /sys/dev/char/251\:5)/../../dax_region/align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../dax_region/align # lsmod|grep pmem dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compat # lsmod|grep dax dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compat
Seems some configurations are different ?
Can you share your info as above ? Thanks.
Quoted 31 lines
Quoted 4 lines
Quoted 4 lines
I don't have the deprecated dax class enabled as could you tell, so the second case is what I was testing. Except it wasn't a namespace/nvdimm but rather an hmem device-dax.
Quoted 8 lines
Quoted 3 lines
'../align' though covers only one case? What about hmem which '../align' returns ENOENT; perhaps using '../dax_region/align' instead which is common to both? Albeit that wouldn't address the sub-division devices (that I mention above)
Seems that you mean to use $(readlink -f
/sys/dev/char/253\:263)/../../dax_region/align.Right ?
An extra '../' ?
# ls $(readlink -f /sys/dev/char/252\:0/../dax_region/align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../dax_region/align 2097152 # cat /sys/dev/char/252\:0/../dax_region/align 2097152For HMAT/hmem devdax, though, only 'dax_region/align' is available for now:
# ls $(readlink -f /sys/dev/char/252:0)/../align ls: cannot access /sys/devices/platform/hmem.0/dax0.0/../align: No such file or directory # ls $(readlink -f /sys/dev/char/252:0)/../dax_region/align /sys/devices/platform/hmem.0/dax0.0/../dax_region/align # cat $(readlink -f /sys/dev/char/252:0)/../dax_region/align 2097152
Quoted 2 lines
The 'dax_region/align' was just an idea mainly because it's common to both device-dax devices -- not sure how others feel about it.
Seems it's reasonable. I need to sync the above path with yours.
Thanks,
Jingqi
Quoted 13 lines
Joao
Quoted 10 lines
Thanks,
Jingqi
Quoted 6 lines
Quoted 5 lines
The current
/sys/bus/daxdevice-model can
be a drop in replacement as long as software is not written to the/sys/classsysfs layout, i.e. it uses ../ instead of device/ to walk to the region properties./nods
Quoted 80 lines · Jingqi
Quoted 38 lines · Joao Martins
Quoted 29 lines · Jingqi
Quoted 4 lines · Joao Martins
Quoted 3 lines · Dan Williams
Quoted 2 lines · Joao Martins
Perhaps, you meant instead:
Quoted 24 lines
Quoted 3 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 16 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.Quoted 8 lines
Hi Dan,
Thanks for your comments.
Seems it is a mistake.
It should be: $(readlink -f /sys/dev/char/253\:263)/../../align
Quoted 8 lines
Hmm, perhaps you have an extra '../' in the path? This works for me:
# ls $(readlink -f /sys/dev/char/252\:0/../align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../align 2097152 # cat /sys/dev/char/252\:0/../align 2097152Hi Joao,
Hmm, I need to have an extra '../' in the path. The details are as follows:
# ll /dev/dax2.0 crw------- 1 root root 251, 5 Mar 20 13:35 /dev/dax2.0 # uname -r 5.6.0-rc1-00044-gb19e8c684703 # readlink -f /sys/dev/char/251\:5/ /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0 # ls $(readlink -f /sys/dev/char/251\:5)/../align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../dax_region/align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../dax_region/align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../../align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../align # ls $(readlink -f /sys/dev/char/251\:5)/../../dax_region/align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../dax_region/align # lsmod|grep pmem dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compat # lsmod|grep dax dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compat
Quoted 3 lines
Seems some configurations are different ?
Can you share your info as above ? Thanks.
Alternatively maybe you can use libdaxctl that automatically handles the ABI differences between compat-dax-class and dax-bus layouts? I didn't recommend it before because I was not sure about qemu's policy about taking on new library dependencies, but with libdaxctl you could do something like (untested):
path = g_strdup_printf("/sys/dev/char/%d:%d", major(st.st_rdev), minor(st.st_rdev));
rpath = realpath(path, NULL); daxctl_region_foreach(ctx, region)
if (strstr(daxctl_region_get_path(region), rpath)) {
align = daxctl_region_get_align(region);
break;
}Quoted 4 lines · Dan Williams
Alternatively maybe you can use libdaxctl that automatically handles the ABI differences between compat-dax-class and dax-bus layouts? I didn't recommend it before because I was not sure about qemu's policy about taking on new library dependencies
In this case I think the new dependency is more than justified, thanks!
Paolo
Quoted 88 lines · Dan Williams
Quoted 78 lines · Jingqi
Quoted 38 lines · Joao Martins
Quoted 29 lines · Jingqi
Quoted 4 lines · Joao Martins
Quoted 3 lines · Dan Williams
Quoted 2 lines · Joao Martins
Perhaps, you meant instead:
Quoted 24 lines
Quoted 3 lines
Quoted 2 lines
/sys/dev/char/%d:%d/alignHmm, are you sure that's working?
It is, except that I made the slight mistake of testing with a bunch of wip patches on top which one of them actually adds the 'align' to child dax device.
Argh, my apologies - and thanks for noticing.
Quoted 16 lines
I expect the alignment to be found
in the region device:
/sys/class/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.1/dax1.0 $(readlink -f /sys/dev/char/253\:263)/../align
$(readlink -f /sys/dev/char/253\:263)/device/align
/sys/bus/dax:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus1/region1/dax1.0/dax1.0 $(readlink -f /sys/dev/char/253\:265)/../align
$(readlink -f /sys/dev/char/253\:265)/device/align <-- No such fileThe use of the /sys/dev/char/%d:%d/device is only supported by the deprecated
/sys/class/dax.Quoted 8 lines
Hi Dan,
Thanks for your comments.
Seems it is a mistake.
It should be: $(readlink -f /sys/dev/char/253\:263)/../../align
Quoted 8 lines
Hmm, perhaps you have an extra '../' in the path? This works for me:
# ls $(readlink -f /sys/dev/char/252\:0/../align) /sys/devices/platform/e820_pmem/ndbus0/region0/dax0.0/dax0.0/../align # cat $(readlink -f /sys/dev/char/252\:0)/../align 2097152 # cat /sys/dev/char/252\:0/../align 2097152Hi Joao,
Hmm, I need to have an extra '../' in the path. The details are as follows:
# ll /dev/dax2.0 crw------- 1 root root 251, 5 Mar 20 13:35 /dev/dax2.0 # uname -r 5.6.0-rc1-00044-gb19e8c684703 # readlink -f /sys/dev/char/251\:5/ /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0 # ls $(readlink -f /sys/dev/char/251\:5)/../align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../dax_region/align ls: cannot access '/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../dax_region/align': No such file or directory # ls $(readlink -f /sys/dev/char/251\:5)/../../align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../align # ls $(readlink -f /sys/dev/char/251\:5)/../../dax_region/align /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1/dax/dax2.0/../../dax_region/align # lsmod|grep pmem dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compat # lsmod|grep dax dax_pmem_compat 16384 0 device_dax 20480 1 dax_pmem_compat dax_pmem_core 16384 1 dax_pmem_compatQuoted 3 lines
Seems some configurations are different ?
Can you share your info as above ? Thanks.
Alternatively maybe you can use libdaxctl that automatically handles the ABI differences between compat-dax-class and dax-bus layouts? I didn't recommend it before because I was not sure about qemu's policy about taking on new library dependencies, but with libdaxctl you could do something like (untested):
Quoted 8 lines
path =
g_strdup_printf("/sys/dev/char/%d:%d", major(st.st_rdev), minor(st.st_rdev));
rpath =realpath(path, NULL);daxctl_region_foreach(ctx, region)if (strstr(daxctl_region_get_path(region), rpath)) { align = daxctl_region_get_align(region); break; }
Thanks for your suggestion. I'll test it.
Thanks,
Jingqi