From: Cornelia Huck <cohuck@redhat.com>
To: Shujun Xue <shujunxue@google.com>,
virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org
Cc: Shujun Xue <shujunxue@google.com>,
Slava Malyugin <slavamn@google.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio-comment] Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.
Date: Mon, 29 Jan 2024 15:55:19 +0100 [thread overview]
Message-ID: <87cytkkx48.fsf@redhat.com> (raw)
In-Reply-To: <CAB6OiKgcWwH_qprNv6Z=F4=Hc2PckoCqQEJCGgkgNVL9Xx4k5A@mail.gmail.com>
On Tue, Jan 23 2024, Shujun Xue <shujunxue@google.com> wrote:
> The Virtio CPU balloon device is a primitive device for managing guest
> CPU capacity: the device asks for certain CPU cores to be online,
> offline or throttled, and the driver performs the requested operation.
> This allows the guest to adapt to changes in allowance of underlying
> CPU capacity.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/187
>
> Signed-off-by: Shujun Xue <shujunxue@google.com>
> ---
> content.tex | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 0a62dce..87f0238 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> \hline
> 45 & SPI master \\
> \hline
> +47 & CPU balloon device \\
> +\hline
> \end{tabular}
>
> Some of the devices above are unspecified by this document,
I'm holding off voting for now until the status of the OASIS
infrastructure migration is clear (sigh).
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2024-01-29 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 17:32 [virtio-comment] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47 Shujun Xue
2024-01-29 14:55 ` Cornelia Huck [this message]
2024-01-29 17:07 ` [virtio-comment] Re: [virtio-dev] " Shujun Xue
2024-01-30 8:25 ` Cornelia Huck
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=87cytkkx48.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=shujunxue@google.com \
--cc=slavamn@google.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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