virtio-comment.lists.oasis-open.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shujun Xue <shujunxue@google.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	Slava Malyugin <slavamn@google.com>
Subject: [virtio-comment] Re: [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47
Date: Tue, 23 Jan 2024 01:58:25 -0500	[thread overview]
Message-ID: <20240123015739-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240122231157.651024-1-shujunxue@google.com>

On Mon, Jan 22, 2024 at 11:11:57PM +0000, Shujun Xue wrote:
> The virtio CPU balloon device is a primitive device for managing guest
> CPU capacity: the device asks for certain CPU cores to be onlined,
> offlined of throttled, and the driver performs the requested operation.
> This allows the guest to adapt to changes in allowance of underlying CPU
> capacity.
> 
> 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..6149612 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}

Did you change anything in this patch? CPU should be upper-case.


>  Some of the devices above are unspecified by this document,
> -- 
> 2.43.0.429.g432eaa2c6b-goog


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/


           reply	other threads:[~2024-01-23  6:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240122231157.651024-1-shujunxue@google.com>]

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=20240123015739-mutt-send-email-mst@kernel.org \
    --to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).