Dear all,
This patch series make hvc framework pass DMA capable memory to
put_chars() of hvc backend(eg, virtio-console), and revert commit
c4baad5029 ("virtio-console: avoid DMA from stack”)
V1
virtio-console: avoid DMA from vmalloc area
https://lkml.org/lkml/2021/7/27/494
For v1 patch, Arnd Bergmann suggests to fix the issue in the first
place:
Make hvc pass DMA capable memory to put_chars()
The fix suggestion is included in v2.
V2
[PATCH 1/2] tty: hvc: pass DMA capable memory to put_chars()
https://lkml.org/lkml/2021/8/1/8
[PATCH 2/2] virtio-console: remove unnecessary kmemdup()
https://lkml.org/lkml/2021/8/1/9
For v2 patch, Arnd Bergmann suggests to make new buf part of the
hvc_struct structure, and fix the compile issue.
The fix suggestion is included in v3.
V3
[PATCH v3 1/2] tty: hvc: pass DMA capable memory to put_chars()
https://lkml.org/lkml/2021/8/3/1347
[PATCH v3 2/2] virtio-console: remove unnecessary kmemdup()
https://lkml.org/lkml/2021/8/3/1348
For v3 patch, Jiri Slaby suggests to make 'char c[N_OUTBUF]' part of
hvc_struct, and make 'hp->outbuf' aligned and use struct_size() to
calculate the size of hvc_struct. The fix suggestion is included in
v4.
V4
[PATCH v4 0/2] make hvc pass dma capable memory to its backend
https://lkml.org/lkml/2021/8/5/1350
[PATCH v4 1/2] tty: hvc: pass DMA capable memory to put_chars()
https://lkml.org/lkml/2021/8/5/1351
[PATCH v4 2/2] virtio-console: remove unnecessary kmemdup()
https://lkml.org/lkml/2021/8/5/1352
For v4 patch, Arnd Bergmann suggests to introduce another
array(cons_outbuf[]) for the buffer pointers next to the cons_ops[]
and vtermnos[] arrays. This fix included in this v5 patch.
V5
Arnd Bergmann suggests to use "L1_CACHE_BYTES" as dma alignment,
use 'sizeof(long)' as dma alignment is wrong. fix it in v6.
V6
It contains coding error, fix it in v7 and it worked normally
according to test result.
V7
Greg KH suggests to add test and code review developer,
Jiri Slaby suggests to use lockless buffer and fix dma alignment
in separate patch.
fix above things in v8.
V8
This contains coding error when switch to use new buffer. fix it in v9.
V9
It didn't make things much clearer, it needs add more comments for new added buf.
Add use lock to protect new added buffer. fix in v10.
V10
Remove 'char outchar' and its lock from hvc_struct, adjust hvc_struct and use
pahole to display the struct layout.
fix it in v11.
********TEST STEPS*********
1, config guest console=hvc0
2, start guest
3, login guest
Welcome to Buildroot
buildroot login: root
#
# cat /proc/cmdline
console=hvc0 root=/dev/vda rw init=/sbin/init
#
drivers/tty/hvc/hvc_console.c | 36 ++++++++++++++++++++---------------
drivers/tty/hvc/hvc_console.h | 21 +++++++++++++++++++-
drivers/char/virtio_console.c | 12 ++----------
3 file changed
As well known, hvc backend can register its opertions to hvc backend.
the operations contain put_chars(), get_chars() and so on.
Some hvc backend may do dma in its operations. eg, put_chars() of
virtio-console. But in the code of hvc framework, it may pass DMA
incapable memory to put_chars() under a specific configuration, which
is explained in commit c4baad5029(virtio-console: avoid DMA from stack):
1, c[] is on stack,
hvc_console_print():
char c[N_OUTBUF] __ALIGNED__;
cons_ops[index]->put_chars(vtermnos[index], c, i);
2, ch is on stack,
static void hvc_poll_put_char(,,char ch)
{
struct tty_struct *tty = driver->ttys[0];
struct hvc_struct *hp = tty->driver_data;
int n;
do {
n = hp->ops->put_chars(hp->vtermno, &ch, 1);
} while (n <= 0);
}
Commit c4baad5029 is just the fix to avoid DMA from stack memory, which
is passed to virtio-console by hvc framework in above code. But I think
the fix is aggressive, it directly uses kmemdup() to alloc new buffer
from kmalloc area and do memcpy no matter the memory is in kmalloc area
or not. But most importantly, it should better be fixed in the hvc
framework, by changing it to never pass stack memory to the put_chars()
function in the first place. Otherwise, we still face the same issue if
a new hvc backend using dma added in the furture.
In this patch, add 'char cons_outbuf[]' as part of 'struct hvc_struct',
so hp->cons_outbuf is no longer the stack memory, we can use it in above
cases safely. We also add lock to protect cons_outbuf instead of using
the global lock of hvc.
Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.
With the patch, we can revert the fix c4baad5029.
Signed-off-by: Xianting Tian <redacted>
Signed-off-by: Shile Zhang <redacted>
---
drivers/tty/hvc/hvc_console.c | 36 ++++++++++++++++++++---------------
drivers/tty/hvc/hvc_console.h | 21 +++++++++++++++++++-
2 files changed, 41 insertions(+), 16 deletions(-)
@@ -922,8 +927,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,returnERR_PTR(err);}-hp=kzalloc(ALIGN(sizeof(*hp),sizeof(long))+outbuf_size,-GFP_KERNEL);+hp=kzalloc(struct_size(hp,outbuf,outbuf_size),GFP_KERNEL);if(!hp)returnERR_PTR(-ENOMEM);
@@ -931,13 +935,13 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,hp->data=data;hp->ops=ops;hp->outbuf_size=outbuf_size;-hp->outbuf=&((char*)hp)[ALIGN(sizeof(*hp),sizeof(long))];tty_port_init(&hp->port);hp->port.ops=&hvc_port_ops;INIT_WORK(&hp->tty_resize,hvc_set_winsz);spin_lock_init(&hp->lock);+spin_lock_init(&hp->cons_outbuf_lock);mutex_lock(&hvc_structs_mutex);/*
@@ -964,6 +968,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,if(i<MAX_NR_HVC_CONSOLES){cons_ops[i]=ops;vtermnos[i]=vtermno;+cons_hvcs[i]=hp;}list_add_tail(&(hp->next),&hvc_structs);
@@ -988,6 +993,7 @@ int hvc_remove(struct hvc_struct *hp)if(hp->index<MAX_NR_HVC_CONSOLES){vtermnos[hp->index]=-1;cons_ops[hp->index]=NULL;+cons_hvcs[hp->index]=NULL;}/* Don't whack hp->irq because tty_hangup() will need to free the irq. */
@@ -48,6 +57,16 @@ struct hvc_struct {structwork_structtty_resize;structlist_headnext;unsignedlongflags;++/*+*thebufanditslockareusedinhvcconsoleapiforputtingchars,+*andalsousedinhvc_poll_put_char()forputtingsinglechar.+*/+spinlock_tcons_outbuf_lock;+charcons_outbuf[N_OUTBUF]__ALIGNED__;++/* the buf is used for putting chars to tty */+charoutbuf[]__ALIGNED__;};/* implemented by a low level driver */
This revert commit c4baad5029 ("virtio-console: avoid DMA from stack")
hvc framework will never pass stack memory to the put_chars() function,
So the calling of kmemdup() is unnecessary, we can remove it.
Signed-off-by: Xianting Tian <redacted>
Reviewed-by: Shile Zhang <redacted>
---
drivers/char/virtio_console.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
Hi Greg and experts
Is this version ok for you? thanks
在 2021/10/15 上午10:46, Xianting Tian 写道:
quoted hunk
As well known, hvc backend can register its opertions to hvc backend.
the operations contain put_chars(), get_chars() and so on.
Some hvc backend may do dma in its operations. eg, put_chars() of
virtio-console. But in the code of hvc framework, it may pass DMA
incapable memory to put_chars() under a specific configuration, which
is explained in commit c4baad5029(virtio-console: avoid DMA from stack):
1, c[] is on stack,
hvc_console_print():
char c[N_OUTBUF] __ALIGNED__;
cons_ops[index]->put_chars(vtermnos[index], c, i);
2, ch is on stack,
static void hvc_poll_put_char(,,char ch)
{
struct tty_struct *tty = driver->ttys[0];
struct hvc_struct *hp = tty->driver_data;
int n;
do {
n = hp->ops->put_chars(hp->vtermno, &ch, 1);
} while (n <= 0);
}
Commit c4baad5029 is just the fix to avoid DMA from stack memory, which
is passed to virtio-console by hvc framework in above code. But I think
the fix is aggressive, it directly uses kmemdup() to alloc new buffer
from kmalloc area and do memcpy no matter the memory is in kmalloc area
or not. But most importantly, it should better be fixed in the hvc
framework, by changing it to never pass stack memory to the put_chars()
function in the first place. Otherwise, we still face the same issue if
a new hvc backend using dma added in the furture.
In this patch, add 'char cons_outbuf[]' as part of 'struct hvc_struct',
so hp->cons_outbuf is no longer the stack memory, we can use it in above
cases safely. We also add lock to protect cons_outbuf instead of using
the global lock of hvc.
Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.
With the patch, we can revert the fix c4baad5029.
Signed-off-by: Xianting Tian <redacted>
Signed-off-by: Shile Zhang <redacted>
---
drivers/tty/hvc/hvc_console.c | 36 ++++++++++++++++++++---------------
drivers/tty/hvc/hvc_console.h | 21 +++++++++++++++++++-
2 files changed, 41 insertions(+), 16 deletions(-)
@@ -922,8 +927,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,returnERR_PTR(err);}-hp=kzalloc(ALIGN(sizeof(*hp),sizeof(long))+outbuf_size,-GFP_KERNEL);+hp=kzalloc(struct_size(hp,outbuf,outbuf_size),GFP_KERNEL);if(!hp)returnERR_PTR(-ENOMEM);
@@ -931,13 +935,13 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,hp->data=data;hp->ops=ops;hp->outbuf_size=outbuf_size;-hp->outbuf=&((char*)hp)[ALIGN(sizeof(*hp),sizeof(long))];tty_port_init(&hp->port);hp->port.ops=&hvc_port_ops;INIT_WORK(&hp->tty_resize,hvc_set_winsz);spin_lock_init(&hp->lock);+spin_lock_init(&hp->cons_outbuf_lock);mutex_lock(&hvc_structs_mutex);/*
@@ -964,6 +968,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,if(i<MAX_NR_HVC_CONSOLES){cons_ops[i]=ops;vtermnos[i]=vtermno;+cons_hvcs[i]=hp;}list_add_tail(&(hp->next),&hvc_structs);
@@ -988,6 +993,7 @@ int hvc_remove(struct hvc_struct *hp)if(hp->index<MAX_NR_HVC_CONSOLES){vtermnos[hp->index]=-1;cons_ops[hp->index]=NULL;+cons_hvcs[hp->index]=NULL;}/* Don't whack hp->irq because tty_hangup() will need to free the irq. */
@@ -48,6 +57,16 @@ struct hvc_struct {structwork_structtty_resize;structlist_headnext;unsignedlongflags;++/*+*thebufanditslockareusedinhvcconsoleapiforputtingchars,+*andalsousedinhvc_poll_put_char()forputtingsinglechar.+*/+spinlock_tcons_outbuf_lock;+charcons_outbuf[N_OUTBUF]__ALIGNED__;++/* the buf is used for putting chars to tty */+charoutbuf[]__ALIGNED__;};/* implemented by a low level driver */
hi Greg,
Could I get your comments of this new version patches? thanks
在 2021/10/15 上午10:46, Xianting Tian 写道:
quoted hunk
As well known, hvc backend can register its opertions to hvc backend.
the operations contain put_chars(), get_chars() and so on.
Some hvc backend may do dma in its operations. eg, put_chars() of
virtio-console. But in the code of hvc framework, it may pass DMA
incapable memory to put_chars() under a specific configuration, which
is explained in commit c4baad5029(virtio-console: avoid DMA from stack):
1, c[] is on stack,
hvc_console_print():
char c[N_OUTBUF] __ALIGNED__;
cons_ops[index]->put_chars(vtermnos[index], c, i);
2, ch is on stack,
static void hvc_poll_put_char(,,char ch)
{
struct tty_struct *tty = driver->ttys[0];
struct hvc_struct *hp = tty->driver_data;
int n;
do {
n = hp->ops->put_chars(hp->vtermno, &ch, 1);
} while (n <= 0);
}
Commit c4baad5029 is just the fix to avoid DMA from stack memory, which
is passed to virtio-console by hvc framework in above code. But I think
the fix is aggressive, it directly uses kmemdup() to alloc new buffer
from kmalloc area and do memcpy no matter the memory is in kmalloc area
or not. But most importantly, it should better be fixed in the hvc
framework, by changing it to never pass stack memory to the put_chars()
function in the first place. Otherwise, we still face the same issue if
a new hvc backend using dma added in the furture.
In this patch, add 'char cons_outbuf[]' as part of 'struct hvc_struct',
so hp->cons_outbuf is no longer the stack memory, we can use it in above
cases safely. We also add lock to protect cons_outbuf instead of using
the global lock of hvc.
Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.
With the patch, we can revert the fix c4baad5029.
Signed-off-by: Xianting Tian <redacted>
Signed-off-by: Shile Zhang <redacted>
---
drivers/tty/hvc/hvc_console.c | 36 ++++++++++++++++++++---------------
drivers/tty/hvc/hvc_console.h | 21 +++++++++++++++++++-
2 files changed, 41 insertions(+), 16 deletions(-)
@@ -922,8 +927,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,returnERR_PTR(err);}-hp=kzalloc(ALIGN(sizeof(*hp),sizeof(long))+outbuf_size,-GFP_KERNEL);+hp=kzalloc(struct_size(hp,outbuf,outbuf_size),GFP_KERNEL);if(!hp)returnERR_PTR(-ENOMEM);
@@ -931,13 +935,13 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,hp->data=data;hp->ops=ops;hp->outbuf_size=outbuf_size;-hp->outbuf=&((char*)hp)[ALIGN(sizeof(*hp),sizeof(long))];tty_port_init(&hp->port);hp->port.ops=&hvc_port_ops;INIT_WORK(&hp->tty_resize,hvc_set_winsz);spin_lock_init(&hp->lock);+spin_lock_init(&hp->cons_outbuf_lock);mutex_lock(&hvc_structs_mutex);/*
@@ -964,6 +968,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data,if(i<MAX_NR_HVC_CONSOLES){cons_ops[i]=ops;vtermnos[i]=vtermno;+cons_hvcs[i]=hp;}list_add_tail(&(hp->next),&hvc_structs);
@@ -988,6 +993,7 @@ int hvc_remove(struct hvc_struct *hp)if(hp->index<MAX_NR_HVC_CONSOLES){vtermnos[hp->index]=-1;cons_ops[hp->index]=NULL;+cons_hvcs[hp->index]=NULL;}/* Don't whack hp->irq because tty_hangup() will need to free the irq. */
@@ -48,6 +57,16 @@ struct hvc_struct {structwork_structtty_resize;structlist_headnext;unsignedlongflags;++/*+*thebufanditslockareusedinhvcconsoleapiforputtingchars,+*andalsousedinhvc_poll_put_char()forputtingsinglechar.+*/+spinlock_tcons_outbuf_lock;+charcons_outbuf[N_OUTBUF]__ALIGNED__;++/* the buf is used for putting chars to tty */+charoutbuf[]__ALIGNED__;};/* implemented by a low level driver */
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Oct 20, 2021 at 04:47:23PM +0800, Xianting Tian wrote:
hi Greg,
Could I get your comments of this new version patches? thanks
It has been less than 5 days. Please relax, and only worry after 2
weeks have gone by. We have lots of patches to review. To help
maintainers out, why don't you review other patches on the mailing lists
as well while you wait?
thanks,
greg k-h
On Fri, Oct 15, 2021 at 10:46:55AM +0800, Xianting Tian wrote:
Dear all,
This patch series make hvc framework pass DMA capable memory to
put_chars() of hvc backend(eg, virtio-console), and revert commit
c4baad5029 ("virtio-console: avoid DMA from stack”)
Thanks for sticking with this, looks much better now, all now queued up.
greg k-h
I am very glad to get this reply:)
Thank you and other experts' kindly help and guide, which improved me a lot.
在 2021/10/21 下午4:35, Greg KH 写道:
On Fri, Oct 15, 2021 at 10:46:55AM +0800, Xianting Tian wrote:
quoted
Dear all,
This patch series make hvc framework pass DMA capable memory to
put_chars() of hvc backend(eg, virtio-console), and revert commit
c4baad5029 ("virtio-console: avoid DMA from stack”)
Thanks for sticking with this, looks much better now, all now queued up.
greg k-h
@@ -151,9 +142,11 @@ static uint32_t vtermnos[MAX_NR_HVC_CONSOLES] = static void hvc_console_print(struct console *co, const char *b, unsigned count) {- char c[N_OUTBUF] __ALIGNED__;+ char *c; unsigned i = 0, n = 0; int r, donecr = 0, index = co->index;+ unsigned long flags;+ struct hvc_struct *hp; /* Console access attempt outside of acceptable console range. */ if (index >= MAX_NR_HVC_CONSOLES)
@@ -163,6 +156,13 @@ static void hvc_console_print(struct console *co, const char *b, if (vtermnos[index] == -1) return;+ hp = cons_hvcs[index];+ if (!hp)+ return;
You effectively make the console unusable until someone calls
hvc_alloc() for this device, correct? This doesn't look right. Neither
you describe this change of behaviour in the commit log.
regards,
--
js
suse labs
*co, const char *b,
if (vtermnos[index] == -1)
return;
+ hp = cons_hvcs[index];
+ if (!hp)
+ return;
You effectively make the console unusable until someone calls
hvc_alloc() for this device, correct? This doesn't look right. Neither
you describe this change of behaviour in the commit log.
I mentioned such info in the commit log:
'Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.'
After you pointed it out, I just found what you said make sense, I checked the code hvc_console_print() can support print before hvc_alloc() is called when someone use hvc_instantiate() for an early console discovery method.
I send a patch to fix the issue? or these serial pathches reverted fisrtly then I resend new version patches? thanks
*co, const char *b,
if (vtermnos[index] == -1)
return;
+ hp = cons_hvcs[index];
+ if (!hp)
+ return;
You effectively make the console unusable until someone calls
hvc_alloc() for this device, correct? This doesn't look right. Neither
you describe this change of behaviour in the commit log.
I mentioned such info in the commit log:
'Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.'
After you pointed it out, I just found what you said make sense, I checked the code hvc_console_print() can support print before hvc_alloc() is called when someone use hvc_instantiate() for an early console discovery method.
I send a patch to fix the issue? or these serial pathches reverted fisrtly then I resend new version patches? thanks
Let me revert these now and you can send an updated version.
thanks,
greg k-h
*co, const char *b,
if (vtermnos[index] == -1)
return;
+ hp = cons_hvcs[index];
+ if (!hp)
+ return;
You effectively make the console unusable until someone calls
hvc_alloc() for this device, correct? This doesn't look right. Neither
you describe this change of behaviour in the commit log.
I mentioned such info in the commit log:
'Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.'
After you pointed it out, I just found what you said make sense, I checked the code hvc_console_print() can support print before hvc_alloc() is called when someone use hvc_instantiate() for an early console discovery method.
I send a patch to fix the issue? or these serial pathches reverted fisrtly then I resend new version patches? thanks
Let me revert these now and you can send an updated version.
*co, const char *b,
if (vtermnos[index] == -1)
return;
+ hp = cons_hvcs[index];
+ if (!hp)
+ return;
You effectively make the console unusable until someone calls
hvc_alloc() for this device, correct? This doesn't look right. Neither
you describe this change of behaviour in the commit log.
I mentioned such info in the commit log:
'Introduce another array(cons_hvcs[]) for hvc pointers next to the
cons_ops[] and vtermnos[] arrays. With the array, we can easily find
hvc's cons_outbuf and its lock.'
After you pointed it out, I just found what you said make sense, I checked the code hvc_console_print() can support print before hvc_alloc() is called when someone use hvc_instantiate() for an early console discovery method.
I send a patch to fix the issue? or these serial pathches reverted fisrtly then I resend new version patches? thanks
Let me revert these now and you can send an updated version.
OK, thanks.
I have now reverted patches 2/3 and 3/3 in this series from my tree.
The first patch was just fine.
thanks,
greg k-h