virtio_console: Use kmalloc instead of kzalloc

Avoid the more cpu expensive kzalloc when allocating buffers.
Originally kzalloc was intended for isolating the guest from
the host by not sending random guest data to the host. But device
isolation is not yet in place so kzalloc is not really needed.

Signed-off-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index 09d193dbb23320570ecc1c8d47e8757c57cdca6e..eecb1f9e2e6b97b789f4270b5b44d0099e526cd6 100644 (file)
--- a/drivers/char/virtio_console.c
+++ b/drivers/char/virtio_console.c
@@ -349,7 +349,7 @@ static struct port_buffer *alloc_buf(size_t buf_size)
        buf = kmalloc(sizeof(*buf), GFP_KERNEL);
        if (!buf)
                goto fail;
-       buf->buf = kzalloc(buf_size, GFP_KERNEL);
+       buf->buf = kmalloc(buf_size, GFP_KERNEL);
        if (!buf->buf)
                goto free_buf;
        buf->len = 0;