From: Paolo Bonzini <pbonzini@redhat.com>
To: Bob Liu <bob.liu@oracle.com>, linux-kernel@vger.kernel.org
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] drivers: virtio_blk: notify blk-core when hw-queue number changes
Date: Sun, 19 Jun 2016 00:10:32 +0200 [thread overview]
Message-ID: <3cd56d3a-85f0-9cce-d42f-f4eace84667b@redhat.com> (raw)
In-Reply-To: <1465811906-24510-1-git-send-email-bob.liu__9616.24590349874$1465832216$gmane$org@oracle.com>
On 13/06/2016 11:58, Bob Liu wrote:
> A guest might be migrated to other hosts with different num_queues, the
> blk-core should aware of that else the reference of &vblk->vqs[qid] may be wrong.
>
> Signed-off-by: Bob Liu <bob.liu@oracle.com>
> ---
> drivers/block/virtio_blk.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> index 42758b5..c169238 100644
> --- a/drivers/block/virtio_blk.c
> +++ b/drivers/block/virtio_blk.c
> @@ -819,6 +819,9 @@ static int virtblk_restore(struct virtio_device *vdev)
> if (ret)
> return ret;
>
> + if (vblk->num_vqs != vblk->tag_set.nr_hw_queues)
> + blk_mq_update_nr_hw_queues(&vblk->tag_set, vblk->num_vqs);
> +
> virtio_device_ready(vdev);
>
> blk_mq_start_stopped_hw_queues(vblk->disk->queue, true);
>
This should never happen; it'd be a configuration problem.
Paolo
next prev parent reply other threads:[~2016-06-18 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:58 [PATCH] drivers: virtio_blk: notify blk-core when hw-queue number changes Bob Liu
2016-06-18 22:10 ` Paolo Bonzini [this message]
2016-07-28 8:18 ` Bob Liu
2016-08-01 9:58 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cd56d3a-85f0-9cce-d42f-f4eace84667b@redhat.com \
--to=pbonzini@redhat.com \
--cc=bob.liu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).