From: "Bo Liu (刘波)-浪潮信息" <liubo03@inspur.com>
To: "mst@redhat.com" <mst@redhat.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: Mon, 30 May 2022 02:16:20 +0000 [thread overview]
Message-ID: <7a413652a9a9469f948fbfa2eae5c401@inspur.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Adding this patch can avoid unnecessary VM exits and reduce the number of VM exits
-----邮件原件-----
发件人: Michael S. Tsirkin <mst@redhat.com>
发送时间: 2022年5月27日 18:58
收件人: Bo Liu (刘波)-浪潮信息 <liubo03@inspur.com>
抄送: david@redhat.com; jasowang@redhat.com; virtualization@lists.linux-foundation.org; linux-kernel@vger.kernel.org
主题: Re: [PATCH] virtio_balloon: check virtqueue_add_outbuf() return value
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
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3777 bytes --]
next reply other threads:[~2022-05-30 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 2:16 Bo Liu (刘波)-浪潮信息 [this message]
2022-05-30 7:00 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2022-05-27 10:43 Bo Liu (刘波)-浪潮信息
2022-05-27 10:57 ` Michael S. Tsirkin
2022-05-27 1:34 Bo Liu
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=7a413652a9a9469f948fbfa2eae5c401@inspur.com \
--to=liubo03@inspur.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.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
all inboxes | Powered by JetHome®