[virtio-comment] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[virtio-comment] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Shujun Xue]

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.

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,
-- 
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/

[virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Shujun Xue]

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.

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,
-- 
2.43.0.429.g432eaa2c6b-goog

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

[virtio-comment] Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Cornelia Huck]

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/

Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Cornelia Huck]

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).


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

[virtio-comment] Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Shujun Xue]

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Is there ETA for the migration?

Bests,
Shujun


Cornelia Huck <cohuck@redhat.com>于2024年1月29日 周一上午6:55写道：

> 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).
>
>

[-- Attachment #2: Type: text/html, Size: 2076 bytes --]

Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Shujun Xue]

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Is there ETA for the migration?

Bests,
Shujun


Cornelia Huck <cohuck@redhat.com>于2024年1月29日 周一上午6:55写道：

> 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).
>
>

[-- Attachment #2: Type: text/html, Size: 2076 bytes --]

[virtio-comment] Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Cornelia Huck]

On Mon, Jan 29 2024, Shujun Xue <shujunxue@google.com> wrote:

> Is there ETA for the migration?

Well, I wish I knew...

>
> Bests,
> Shujun
>
>
> Cornelia Huck <cohuck@redhat.com>于2024年1月29日 周一上午6:55写道：
>
>> 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/

Re: [virtio-dev] [PATCH] Define the DEVICE ID of Virtio Cpu balloon device as 47.

[Cornelia Huck]

On Mon, Jan 29 2024, Shujun Xue <shujunxue@google.com> wrote:

> Is there ETA for the migration?

Well, I wish I knew...

>
> Bests,
> Shujun
>
>
> Cornelia Huck <cohuck@redhat.com>于2024年1月29日 周一上午6:55写道：
>
>> 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).
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org