On Tue, Feb 07 2023, Parav Pandit wrote:
>> From: Cornelia Huck
>> Sent: Tuesday, February 7, 2023 8:49 AM
>>
>> On Fri, Feb 03 2023, Parav Pandit wrote:
>>
>> > Currently some fields of the virtio_net_config structure are defined
>> > befor
On Thu, Feb 09 2023, Parav Pandit wrote:
> The control VQ of the virtio network device is used beyond advance
> steering control. The control VQ dynamically changes multiple features
> of the initialized device.
>
> Hence, update this area of control VQ introductory description at few
> places
On Thu, Feb 09 2023, "Michael S. Tsirkin" wrote:
> On Thu, Feb 09, 2023 at 03:41:08AM +0200, Parav Pandit wrote:
>> @@ -389,8 +392,8 @@ \subsection{Device Operation}\label{sec:Device Types /
>> Network Device / Device O
>> };
>> \end{lstlisting}
>>
>> -The controlq is used to control device
On Fri, Feb 03 2023, Parav Pandit wrote:
> Driver notifications section is under "Basic Facilities of a Virtio
> Device". However, the label is placed under "Virtqueues" section.
>
> Fix the label references.
>
> Signed-off-by: Parav Pandit
> ---
> content.tex | 14 +++---
> 1 file
On Thu, Feb 02 2023, Parav Pandit wrote:
> The control VQ of the virtio network device is used beyond advance
> steering control. The control VQ dynamically changes multiple features
> of the initialized device.
>
> Hence, update this area of control VQ introductory description at few
> places
On Wed, Feb 15 2023, "Michael S. Tsirkin" wrote:
> On Fri, Feb 10, 2023 at 12:23:14PM +0100, Cornelia Huck wrote:
>> On Fri, Feb 03 2023, Parav Pandit wrote:
>>
>> > Driver notifications section is under "Basic Facilities of a Virtio
>> > Device&
On Wed, Feb 15 2023, "Michael S. Tsirkin" wrote:
> On Wed, Feb 15, 2023 at 01:19:25PM +0100, Cornelia Huck wrote:
>> On Wed, Feb 15 2023, "Michael S. Tsirkin" wrote:
>>
>> > On Fri, Feb 10, 2023 at 12:23:14PM +0100, Cornelia Huck wrote:
&g
On Mon, Jan 23 2023, Parav Pandit wrote:
> The control VQ of the virtio network device is used beyond advance
> steering control. The control VQ dynamically changes multiple features
> of the initialized device.
>
> Hence, update this area of control VQ introductory description at few
> places
ion
> v4->v5:
> - new patch
> ---
> admin.tex | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Cornelia Huck
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional
On Thu, Jul 06 2023, Parav Pandit wrote:
> diff --git a/admin-cmds-legacy-interface.tex b/admin-cmds-legacy-interface.tex
> new file mode 100644
> index 000..dd01c0a
> --- /dev/null
> +++ b/admin-cmds-legacy-interface.tex
> @@ -0,0 +1,261 @@
> +\subsubsection{Legacy
On Thu, Jul 06 2023, Parav Pandit wrote:
> diff --git a/transport-pci-legacy-regs.tex b/transport-pci-legacy-regs.tex
> new file mode 100644
> index 000..ceea28c
> --- /dev/null
> +++ b/transport-pci-legacy-regs.tex
> @@ -0,0 +1,42 @@
> +\subsection{Legacy Interface: Group member device
On Thu, Jul 06 2023, Parav Pandit wrote:
>> From: Cornelia Huck
>> Sent: Thursday, July 6, 2023 12:28 PM
>>
>> On Thu, Jul 06 2023, Parav Pandit wrote:
>>
>> > diff --git a/transport-pci-legacy-regs.tex
>> > b/transport-pci-legacy-regs.tex
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
as part of the release process for the 1.3 version of the virtio spec,
we have now entered feature freeze. This means:
***
By July 1st[3rd], all not yet integrated features that are targeting 1.3 need
to have at
On Thu, Jul 06 2023, Parav Pandit wrote:
>> From: Michael S. Tsirkin
>> Sent: Thursday, July 6, 2023 4:42 PM
>
> [..]
>> > Can we please avoid this over engineering?
>> > Interface has the doors open for driver to make wise decision depending on
>> its environment.
>>
>> what if driver can
On Fri, Jul 07 2023, Parav Pandit wrote:
> This short series introduces legacy registers access commands for the owner
> group member access the legacy registers of the member VFs.
> This short series introduces legacy region access commands by the group owner
> device for its member devices.
>
On Thu, Jul 06 2023, "Michael S. Tsirkin" wrote:
> On Fri, Jul 07, 2023 at 12:27:19AM +0300, Parav Pandit wrote:
>> This short series introduces legacy registers access commands for the owner
>> group member access the legacy registers of the member VFs.
>> This short series introduces legacy
On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
> On Wed, Jul 12, 2023 at 07:44:01PM +0800, Xuan Zhuo wrote:
>> On Wed, 12 Jul 2023 07:34:38 -0400, "Michael S. Tsirkin"
>> wrote:
>> > On Tue, Mar 15, 2022 at 11:24:02AM +0800, Xuan Zhuo wrote:
>> > > This patch allows the driver to obtain some
On Wed, Jul 12 2023, Heng Qi wrote:
> 在 2023/7/12 下午8:42, Cornelia Huck 写道:
>> On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
>>
>>> On Wed, Jul 12, 2023 at 02:22:26PM +0200, Cornelia Huck wrote:
>>>> On Mon, Jul 03 2023, Heng Qi wrote:
>&
On Wed, Jul 12 2023, Heng Qi wrote:
> 在 2023/7/12 下午9:25, Cornelia Huck 写道:
>> ...while the changes above give me a fine pdf, the html generated is
>> broken. The problem seems to originate in the normative references that
>> are added in introduction.tex, but I don't see
On Mon, Jul 03 2023, Heng Qi wrote:
(...)
> +\paragraph{Inner Header Hash}
> +\label{sec:Device Types / Network Device / Device Operation / Processing of
> Incoming Packets / Inner Header Hash}
> +
> +If VIRTIO_NET_F_HASH_TUNNEL has been negotiated, the driver can send the
> command
>
On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
> On Wed, Jul 12, 2023 at 02:22:26PM +0200, Cornelia Huck wrote:
>> On Mon, Jul 03 2023, Heng Qi wrote:
>>
>> (...)
>>
>> > +\paragraph{Inner Header Hash}
>> > +\label{sec:Device
On Thu, Jul 13 2023, Cornelia Huck wrote:
> On Thu, Jul 13 2023, Parav Pandit wrote:
>
>> This short patches fixes the editing errors that stops the pdf and html
>> generation.
>>
>> These 3 fixes are for the patch [1] for the github issue [2].
>>
>>
On Thu, Jul 13 2023, Parav Pandit wrote:
> This short patches fixes the editing errors that stops the pdf and html
> generation.
>
> These 3 fixes are for the patch [1] for the github issue [2].
>
> [1] https://lists.oasis-open.org/archives/virtio-comment/202307/msg00024.html
> [2]
On Thu, Jul 13 2023, Parav Pandit wrote:
> Avoid hyphen and replace it with white space like rest of the entries.
> Also avoid unnecessary braces.
> Name RFC as just RFC without special prefix about it.
>
> This likely resolves the html generation errors.
>
> Signed-off-by: Parav Pandit
> ---
>
On Wed, Jul 12 2023, Parav Pandit wrote:
>> From: Michael S. Tsirkin
>> Sent: Wednesday, July 12, 2023 6:41 PM
>> Hmm. escapechar did not work then?
>
> Forgot to mention, I tried it, it didn't work.
It seemed to work for me (at least in the pdf) -- I'd prefer that one as
a minimal change.
On Thu, Jul 13 2023, Parav Pandit wrote:
> With extra white space for the define, pdf generation fails.
> Also place the C code under listing.
>
> Signed-off-by: Parav Pandit
> ---
> device-types/net/description.tex | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
On Mon, Jul 10 2023, "Michael S. Tsirkin" wrote:
> On Mon, Jul 10, 2023 at 07:17:52PM +0300, Parav Pandit wrote:
>> +The \field{flags} value of 0x1 indicates that the notification address is of
>> +the owner device, value of 0x2 indicates that the notification address is of
>> +the member
On Fri, Jul 07 2023, Haixu Cui wrote:
> Hi Michael S. Tsirkin, Cornelia Huck,
> I have created an issue
> https://github.com/oasis-tcs/virtio-spec/issues/174 to request Device ID
> 45 for SPI master. Please help to deal with it, thank you very much.
Technically, we're in fe
On Fri, Jul 07 2023, Parav Pandit wrote:
(...)
> +When the device supports VIRTIO_ADMIN_CMD_LEGACY_NOTIFY_INFO command, the
> group
s/supports/supports the/
> +owner device hardwires VF BAR0 to zero in the SR-IOV Extended capability.
(...)
> +\devicenormative{\paragraph}{Legacy
On Wed, Jul 05 2023, Parav Pandit wrote:
>> From: Michael S. Tsirkin
>> Sent: Wednesday, July 5, 2023 7:09 AM
>>
>> OK I sent a bunch of comments. Pls try to address, unfortunately I didn't go
>> in
>> depth over the last patch, but I feel it should be squashed into the generic
>> legacy
On Wed, Jul 05 2023, Parav Pandit wrote:
> diff --git a/admin-cmds-legacy-interface.tex b/admin-cmds-legacy-interface.tex
> new file mode 100644
> index 000..09001d5
> --- /dev/null
> +++ b/admin-cmds-legacy-interface.tex
> @@ -0,0 +1,205 @@
> +\subsubsection{Legacy
On Wed, Jul 05 2023, Parav Pandit wrote:
> diff --git a/admin-cmds-legacy-interface.tex b/admin-cmds-legacy-interface.tex
> index 09001d5..571b256 100644
> --- a/admin-cmds-legacy-interface.tex
> +++ b/admin-cmds-legacy-interface.tex
> @@ -150,7 +150,7 @@ \subsubsection{Legacy
changed, 2 insertions(+)
>
Reviewed-by: Cornelia Huck
-
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
On Wed, Jul 05 2023, Parav Pandit wrote:
> Requirements are put one additional level down. Fix it.
>
> Signed-off-by: Parav Pandit
> ---
> changelog:
> v4->v5:
> - new patch
> ---
> admin.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Same thing applies to the normative
On Mon, Jul 03 2023, "Michael S. Tsirkin" wrote:
> On Mon, Jul 03, 2023 at 11:27:11PM +0800, Heng Qi wrote:
>> 1. Currently, a received encapsulated packet has an outer and an inner
>> header, but
>> the virtio device is unable to calculate the hash for the inner header. The
>> same
>> flow
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
we'll soon start the process of getting version 1.3 of the virtio spec
released. As a first step, we'll enter feature freeze on July 1st. This
means:
***
By July 1st, all not yet integrated features that are
As outlined in
https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
as part of the release process for the 1.3 version of the virtio spec,
we have now entered change freeze. This means that the only changes to
the main virtio branch will now be those needed for the 1.3 release
On Mon, Jul 03 2023, Cornelia Huck wrote:
> As outlined in
> https://lists.oasis-open.org/archives/virtio/202304/msg00036.html ff.,
> as part of the release process for the 1.3 version of the virtio spec,
> we have now entered feature freeze. This means:
>
> ***
> By July
On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
> On Wed, Jul 12, 2023 at 02:24:32PM +0200, Cornelia Huck wrote:
>> On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
>> > Yes we were supposed to freeze for 1.3. This change can be merged on a
>> >
On Fri, Jul 21 2023, "Michael S. Tsirkin" wrote:
> On Fri, Jul 21, 2023 at 02:24:57PM +0200, Cornelia Huck wrote:
>> On Wed, Jul 12 2023, "Michael S. Tsirkin" wrote:
>>
>> > On Wed, Jul 12, 2023 at 02:24:32PM +0200, Cornelia Huck wrote:
>> &
On Thu, Jun 29 2023, "Michael S. Tsirkin" wrote:
> On Thu, Jun 29, 2023 at 05:41:34PM +, Parav Pandit wrote:
>> Hi Cornelia, Michael,
>>
>> > From: virtio-comm...@lists.oasis-open.org > > open.org> On Behalf Of Cornelia Huck
>> > Sent: W
dhat.com/T/#t
>
> Signed-off-by: Parav Pandit
> ---
> admin.tex | 11 ++-
> 1 file changed, 6 insertions(+), 5 deletions(-)
Reviewed-by: Cornelia Huck
Let's push this as an editorial change once the main series is merged.
-
On Fri, May 05 2023, Parav Pandit wrote:
> diff --git a/content.tex b/content.tex
> index 9cf938c..327926f 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -405,8 +405,12 @@ \section{Driver Notifications} \label{sec:Basic
> Facilities of a Virtio Device /
> notification to the device.
>
>
On Tue, May 16 2023, "Michael S. Tsirkin" wrote:
> On Tue, May 16, 2023 at 10:24:12AM +0200, Cornelia Huck wrote:
>> On Tue, May 16 2023, "Michael S. Tsirkin" wrote:
>>
>> > On Tue, May 16, 2023 at 06:01:39AM +0300, Parav Pandit wrote:
>> >
On Tue, May 16 2023, "Michael S. Tsirkin" wrote:
> On Tue, May 16, 2023 at 06:01:39AM +0300, Parav Pandit wrote:
>> diff --git a/content.tex b/content.tex
>> index 9df81b8..417d476 100644
>> --- a/content.tex
>> +++ b/content.tex
>> @@ -26,10 +26,10 @@ \section{\field{Device Status}
On Wed, May 03 2023, Alex Bennée wrote:
> Cornelia Huck writes:
>
>> On Fri, Apr 28 2023, Alexander Gordeev
>> wrote:
>>
>>> On 27.04.23 15:16, Alexandre Courbot wrote:
>>>> But in any case, that's irrelevant to the guest-host interface, and I
&g
On Fri, Apr 28 2023, Alexander Gordeev
wrote:
> On 27.04.23 15:16, Alexandre Courbot wrote:
>> But in any case, that's irrelevant to the guest-host interface, and I
>> think a big part of the disagreement stems from the misconception that
>> V4L2 absolutely needs to be used on either the guest
>>> I also hope to be able to update virtio-video at a faster pace. Please
>>> let me try.
>>
>> Please hold on a bit - there are two things here.
>>
>> 1) I'd like to settle the virtio-v4l2/virtio-video argument first to
>> make sure we don't get two things clashing head-on. As far as codecs
>>
On Tue, Feb 13 2024, Harald Mommer wrote:
> This is the 3rd RFC version of a virtio SPI Linux driver which is
> intended to be compliant with the proposed virtio SPI draft
> specification V10.
FWIW: this version of the SPI spec has been voted in for virtio 1.4 (and
is consequently available on
On Tue, Jan 30 2024, Viresh Kumar wrote:
> The virtio documentation currently doesn't define any generic
> requirements that are applicable to all transports. They can be useful
> while adding support for a new transport.
>
> This commit tries to define the same.
>
> Signed-off-by: Viresh Kumar
On Fri, Jun 09 2023, Mikhail Golubev-Ciuchea
wrote:
> diff --git a/introduction.tex b/introduction.tex
> index b7155bf..d560c63 100644
> --- a/introduction.tex
> +++ b/introduction.tex
> @@ -101,6 +101,8 @@ \section{Normative References}\label{sec:Normative
> References}
>
On Fri, Jun 09 2023, Mikhail Golubev-Ciuchea
wrote:
> From: Harald Mommer
>
> virtio-can is a virtual CAN device. It provides a way to give access to
> a CAN controller from a driver guest. The device is aimed to be used by
> driver guests running a HLOS as well as by driver guests running a
>
On Mon, Feb 05 2024, "Pape, Andreas (ADITG/ESS3)" wrote:
> 24kHz is used for 'super wideband' voice transmission 12kHz is added 'for
> completeness'
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/184
>
> Signed-off-by: Andreas Pape
> ---
> device-types/sound/description.tex | 4 +++-
On Wed, Feb 14 2024, Anton Yakovlev wrote:
> Thanks Pape!
>
>
> On 05.02.2024 23:41, Pape, Andreas (ADITG/ESS3) wrote:
>> 24kHz is used for 'super wideband' voice transmission 12kHz is added 'for
>> completeness'
>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/184
>>
>>
On Mon, Dec 04 2023, Haixu Cui wrote:
> Hi Huck,
>
> On 12/1/2023 7:01 PM, Cornelia Huck wrote:
>> On Fri, Dec 01 2023, Haixu Cui wrote:
>>
>>>>> +Note: chipselect is an electrical signal controlled by the SPI
>>>>> controller, used to selec
On Tue, Dec 05 2023, Alex Bennée wrote:
> Cornelia Huck writes:
>
>> On Tue, Dec 05 2023, Viresh Kumar wrote:
>>> +
>>> +The device MUST present each event, in a transport defined way, from the
>>> +moment it takes place until the driver acknowledges
On Wed, Dec 06 2023, Viresh Kumar wrote:
> On 05-12-23, 14:18, Cornelia Huck wrote:
>> On Tue, Dec 05 2023, Viresh Kumar wrote:
>> > +\section{Virtio Transport Requirements}\label{sec:Virtio Transport
>> > Options / Virtio Transport Requirements}
>> >
On Tue, Dec 12 2023, Haixu Cui wrote:
[BTW: A changelog would be useful, either in the patch or in the cover
letter.]
> The Virtio SPI (Serial Peripheral Interface) device is a virtual
> SPI controller that allows the driver to operate and use the SPI
> controller under the control of the host.
On Tue, Dec 05 2023, Scott McGrath wrote:
[dropped non-virtio lists, added the other virtio lists]
> The Transition Schedule
>
> Starting 14 December, there may be as much as several days of system
> downtime. During the downtime you will not receive email messages sent to
> this list or have
On Tue, Dec 12 2023, Haixu Cui wrote:
> The Virtio SPI (Serial Peripheral Interface) device is a virtual
> SPI controller that allows the driver to operate and use the SPI
> controller under the control of the host.
>
> This patch adds the specification for virtio-spi.
>
> Signed-off-by: Haixu
On Mon, Dec 18 2023, Alex Bennée wrote:
> Cornelia Huck writes:
>
>> On Tue, Dec 05 2023, Alex Bennée wrote:
>>
>>> Cornelia Huck writes:
>>>
>>>> On Tue, Dec 05 2023, Viresh Kumar wrote:
>>>>> +
>>>>> +The devi
On Mon, Dec 18 2023, Bill Mills wrote:
> On 12/18/23 9:19 AM, Alex Bennée wrote:
>> Cornelia Huck writes:
>>
>>> On Wed, Dec 06 2023, Viresh Kumar wrote:
>>>
>>>> On 05-12-23, 14:18, Cornelia Huck wrote:
>>>>> On Tue, Dec 05 2
On Thu, Dec 21 2023, Haixu Cui wrote:
> Hi Cornelia,
> Much appreciated for your comments and please refer to my response.
>
> On 12/18/2023 7:04 PM, Cornelia Huck wrote:
>> On Tue, Dec 12 2023, Haixu Cui wrote:
>>
>> [BTW: A changelog would be useful, eithe
On Thu, Dec 21 2023, Haixu Cui wrote:
> Hi Cornelia,
>
> On 12/21/2023 4:44 PM, Cornelia Huck wrote:
>> On Thu, Dec 21 2023, Haixu Cui wrote:
>>>> Please move inclusion of this new file into content.tex here, instead of
>>>> including a not-
You may have been wondering what the current state of virtio 1.3 is; the
tl;dr is: we have to deal with some unfortunate delays, but it is really
nearing release now.
The current state
-
virtio-1.3-csd01 (committee specification draft) has been out for public
review, and that 30
On Thu, Dec 07 2023, Igor Skalkin wrote:
> diff --git a/device-types/bt/description.tex b/device-types/bt/description.tex
> new file mode 100644
> index 000..98311f4
> --- /dev/null
> +++ b/device-types/bt/description.tex
> @@ -0,0 +1,158 @@
> +\section{BT Device}\label{sec:Device Types / BT
On Mon, Jan 08 2024, Mikhail Golubev-Ciuchea
wrote:
> Hi all!
>
> I kindly request a vote.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/186
Oh, that has been a while... I believe that this still fits on top,
although it has conflicts with virtio-spi, but nothing that a bit of
On Thu, Jan 11 2024, Heng Qi wrote:
> 在 2024/1/4 下午12:47, Heng Qi 写道:
>>
>>
>> 在 2024/1/3 下午2:35, Heng Qi 写道:
>>> There is a historical error in virtio spec:
>>> "If VIRTIO_NET_F_GUEST_CSUM is not negotiated, the device *MUST*
>>> set flags
>>> to zero and SHOULD supply a fully
On Wed, Nov 29 2023, Haixu Cui wrote:
> Hi Viresh,
>
> On 11/29/2023 3:30 PM, Viresh Kumar wrote:
>> On 28-11-23, 20:58, Haixu Cui wrote:
>>> On 11/27/2023 6:17 PM, Viresh Kumar wrote:
On 24-11-23, 15:20, Haixu Cui wrote:
> +For half-duplex read transfer, \field{rx_buf} is filled by
On Mon, Nov 27 2023, Haixu Cui wrote:
> On 11/24/2023 11:46 PM, Cornelia Huck wrote:
>> On Fri, Nov 24 2023, Haixu Cui wrote:
>>> +The \field{chip_select_max_number} is the maximum number of chipselect the
>>> host SPI controller supports.
>>
>>
On Mon, Nov 27 2023, Cornelia Huck wrote:
> On Mon, Nov 27 2023, Haixu Cui wrote:
>
>> On 11/24/2023 11:46 PM, Cornelia Huck wrote:
>>> On Fri, Nov 24 2023, Haixu Cui wrote:
>>>> +The \field{chip_select_max_number} is the maximum number of chipselect
>
On Tue, Dec 05 2023, Viresh Kumar wrote:
> The virtio documentation currently doesn't define any generic
> requirements that are applicable to all transports. They can be useful
> while adding support for a new transport.
>
> This commit tries to define the same.
Thank you for tackling this,
On Fri, Dec 01 2023, Haixu Cui wrote:
>>> +Note: chipselect is an electrical signal controlled by the SPI controller,
>>> used to select the
>>> +SPI slaves connected to the controller.
>>
>> I wonder whether another term is now more commonly used... the Wikipedia
>> article uses main/sub, is
On Fri, Nov 24 2023, Haixu Cui wrote:
> virtio-spi is a virtual SPI (Serial Peripheral Interface) controller and it
> allows
> a guest to operate and use the host SPI controller.
>
> This patch adds the specification for virtio-spi.
As Mark has already reviewed it from the SPI POV (thanks!),
On Thu, Nov 30 2023, Haixu Cui wrote:
> The Virtio SPI (Serial Peripheral Interface) device is a virtual
> SPI controller that allows the driver to operate and use the SPI
> controller under the control of the device.
>
> This patch adds the specification for virtio-spi.
>
> Signed-off-by: Haixu
On Wed, Nov 29 2023, Viresh Kumar wrote:
> On 29-11-23, 18:31, Haixu Cui wrote:
>> Hi Viresh,
>>
>> Thank you for your helpful comments. In next patch, I will clearly point
>> this out:
>
> Great, finally we are on the same page. Thanks Haixu.
>
>> "For full-duplex read and write
On Mon, Jan 29 2024, "Michael S. Tsirkin" wrote:
> On Mon, Jan 29, 2024 at 04:06:01PM +0100, Cornelia Huck wrote:
>> On Wed, Jan 24 2024, "Michael S. Tsirkin" wrote:
>>
>> > This is not a huge deal since it's a SHOULD anyway,
>> > so make
On Tue, Jan 23 2024, 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 online,
> offline or throttled, and the driver performs the requested operation.
> This allows the guest to adapt to changes
On Wed, Jan 24 2024, "Michael S. Tsirkin" wrote:
> This is not a huge deal since it's a SHOULD anyway,
> so make the new requirement SHOULD too.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> device-types/net/description.tex | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff
On Mon, Jan 29 2024, Viresh Kumar wrote:
> On 18-12-23, 15:02, Cornelia Huck wrote:
>> Other things that probably should be mandatory:
>>
>> - A way for the driver to change the device status. Reading it would
>> probably be a strong SHOULD.
>> - A way to imp
On Mon, Jan 15 2024, Cornelia Huck wrote:
> On Mon, Jan 08 2024, Mikhail Golubev-Ciuchea
> wrote:
>
>> Hi all!
>>
>> I kindly request a vote.
>>
>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/186
>
> Oh, that has been a while... I be
On Mon, Jan 29 2024, Shujun Xue wrote:
> Is there ETA for the migration?
Well, I wish I knew...
>
> Bests,
> Shujun
>
>
> Cornelia Huck 于2024年1月29日 周一上午6:55写道：
>
>> On Tue, Jan 23 2024, Shujun Xue wrote:
>>
>> > The Virtio CPU balloon device is a
On Wed, Feb 21 2024, Marc Kleine-Budde wrote:
> On 21.02.2024 14:16:54, Matias Ezequiel Vara Larsen wrote:
>> On Wed, Feb 21, 2024 at 01:49:31PM +0100, Marc Kleine-Budde wrote:
>> > On 21.02.2024 11:37:58, Matias Ezequiel Vara Larsen wrote:
>> > > > > +The length of the \field{sdu} is determined
601 - 683 of 683 matches
Mail list logo
