From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Bo Liu (刘波)-浪潮信息" <liubo03@inspur.com>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio_balloon: check virtqueue_add_outbuf() return value
Date: Fri, 27 May 2022 06:57:32 -0400 [thread overview]
Message-ID: <20220527065611-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <4789cbbb9d59420abc86a9e225ef0bfd@inspur.com>
On Fri, May 27, 2022 at 10:43:30AM +0000, Bo Liu (刘波)-浪潮信息 wrote:
> The purpose of this patch is, virtqueue_add_outbuf() adding data to
> virtqueue may succeed or fail. If successful, it will call virtqueue_kick()
> to notifie the host backend driver, but if the virtqueue_add_outbuf() fails,
> the data is not successfully added to the virtqueue, and the host back-end
> driver does not need to be notified for processing.
>
> Thanks.
Why is it a problem if we do?
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Bo Liu (刘波)-浪潮信息" <liubo03@inspur.com>
Cc: "david@redhat.com" <david@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio_balloon: check virtqueue_add_outbuf() return value
Date: Fri, 27 May 2022 06:57:32 -0400 [thread overview]
Message-ID: <20220527065611-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <4789cbbb9d59420abc86a9e225ef0bfd@inspur.com>
On Fri, May 27, 2022 at 10:43:30AM +0000, Bo Liu (刘波)-浪潮信息 wrote:
> The purpose of this patch is, virtqueue_add_outbuf() adding data to
> virtqueue may succeed or fail. If successful, it will call virtqueue_kick()
> to notifie the host backend driver, but if the virtqueue_add_outbuf() fails,
> the data is not successfully added to the virtqueue, and the host back-end
> driver does not need to be notified for processing.
>
> Thanks.
Why is it a problem if we do?
--
MST
next prev parent reply other threads:[~2022-05-27 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:43 [PATCH] virtio_balloon: check virtqueue_add_outbuf() return value Bo Liu (刘波)-浪潮信息
2022-05-27 10:57 ` Michael S. Tsirkin [this message]
2022-05-27 10:57 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2022-05-30 2:16 Bo Liu (刘波)-浪潮信息
2022-05-30 7:00 ` David Hildenbrand
2022-05-30 7:00 ` David Hildenbrand
2022-05-27 1:34 Bo Liu
2022-05-27 10:24 ` Michael S. Tsirkin
2022-05-27 10:24 ` Michael S. Tsirkin
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=20220527065611-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.