* [PATCH] virtio-blk: Define dev cfg layout before its fields
@ 2023-02-23 13:52 Parav Pandit
2023-02-23 20:46 ` [virtio-comment] " Stefan Hajnoczi
0 siblings, 1 reply; 10+ messages in thread
From: Parav Pandit @ 2023-02-23 13:52 UTC (permalink / raw)
To: mst, virtio-dev, cohuck
Cc: virtio-comment, shahafs, Parav Pandit, Max Gurtovoy
Define device configuration layout structure before describing its
individual fields.
This is an editorial change.
Suggested-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/blk/description.tex | 95 ++++++++++++++++----------------
1 file changed, 48 insertions(+), 47 deletions(-)
diff --git a/device-types/blk/description.tex b/device-types/blk/description.tex
index 20007e3..517b012 100644
--- a/device-types/blk/description.tex
+++ b/device-types/blk/description.tex
@@ -83,6 +83,54 @@ \subsubsection{Legacy Interface: Feature bits}\label{sec:Device Types / Block De
\subsection{Device configuration layout}\label{sec:Device Types / Block Device / Device configuration layout}
+The block device has the following device configuration layout.
+
+\begin{lstlisting}
+struct virtio_blk_config {
+ le64 capacity;
+ le32 size_max;
+ le32 seg_max;
+ struct virtio_blk_geometry {
+ le16 cylinders;
+ u8 heads;
+ u8 sectors;
+ } geometry;
+ le32 blk_size;
+ struct virtio_blk_topology {
+ // # of logical blocks per physical block (log2)
+ u8 physical_block_exp;
+ // offset of first aligned logical block
+ u8 alignment_offset;
+ // suggested minimum I/O size in blocks
+ le16 min_io_size;
+ // optimal (suggested maximum) I/O size in blocks
+ le32 opt_io_size;
+ } topology;
+ u8 writeback;
+ u8 unused0;
+ u16 num_queues;
+ le32 max_discard_sectors;
+ le32 max_discard_seg;
+ le32 discard_sector_alignment;
+ le32 max_write_zeroes_sectors;
+ le32 max_write_zeroes_seg;
+ u8 write_zeroes_may_unmap;
+ u8 unused1[3];
+ le32 max_secure_erase_sectors;
+ le32 max_secure_erase_seg;
+ le32 secure_erase_sector_alignment;
+ struct virtio_blk_zoned_characteristics {
+ le32 zone_sectors;
+ le32 max_open_zones;
+ le32 max_active_zones;
+ le32 max_append_sectors;
+ le32 write_granularity;
+ u8 model;
+ u8 unused2[3];
+ } zoned;
+};
+\end{lstlisting}
+
The \field{capacity} of the device (expressed in 512-byte sectors) is always
present. The availability of the others all depend on various feature
bits as indicated above.
@@ -167,53 +215,6 @@ \subsection{Device configuration layout}\label{sec:Device Types / Block Device /
terminated by the device with a "zone resources exceeded" error as defined for
specific commands later.
-\begin{lstlisting}
-struct virtio_blk_config {
- le64 capacity;
- le32 size_max;
- le32 seg_max;
- struct virtio_blk_geometry {
- le16 cylinders;
- u8 heads;
- u8 sectors;
- } geometry;
- le32 blk_size;
- struct virtio_blk_topology {
- // # of logical blocks per physical block (log2)
- u8 physical_block_exp;
- // offset of first aligned logical block
- u8 alignment_offset;
- // suggested minimum I/O size in blocks
- le16 min_io_size;
- // optimal (suggested maximum) I/O size in blocks
- le32 opt_io_size;
- } topology;
- u8 writeback;
- u8 unused0;
- u16 num_queues;
- le32 max_discard_sectors;
- le32 max_discard_seg;
- le32 discard_sector_alignment;
- le32 max_write_zeroes_sectors;
- le32 max_write_zeroes_seg;
- u8 write_zeroes_may_unmap;
- u8 unused1[3];
- le32 max_secure_erase_sectors;
- le32 max_secure_erase_seg;
- le32 secure_erase_sector_alignment;
- struct virtio_blk_zoned_characteristics {
- le32 zone_sectors;
- le32 max_open_zones;
- le32 max_active_zones;
- le32 max_append_sectors;
- le32 write_granularity;
- u8 model;
- u8 unused2[3];
- } zoned;
-};
-\end{lstlisting}
-
-
\subsubsection{Legacy Interface: Device configuration layout}\label{sec:Device Types / Block Device / Device configuration layout / Legacy Interface: Device configuration layout}
When using the legacy interface, transitional devices and drivers
MUST format the fields in struct virtio_blk_config
--
2.26.2
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
2023-02-23 13:52 [PATCH] virtio-blk: Define dev cfg layout before its fields Parav Pandit
@ 2023-02-23 20:46 ` Stefan Hajnoczi
2023-03-12 13:22 ` Parav Pandit
0 siblings, 1 reply; 10+ messages in thread
From: Stefan Hajnoczi @ 2023-02-23 20:46 UTC (permalink / raw)
To: Parav Pandit
Cc: mst, virtio-dev, cohuck, virtio-comment, shahafs, Max Gurtovoy
[-- Attachment #1: Type: text/plain, Size: 5125 bytes --]
On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> Define device configuration layout structure before describing its
> individual fields.
>
> This is an editorial change.
>
> Suggested-by: Cornelia Huck <cohuck@redhat.com>
> Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> device-types/blk/description.tex | 95 ++++++++++++++++----------------
> 1 file changed, 48 insertions(+), 47 deletions(-)
>
> diff --git a/device-types/blk/description.tex b/device-types/blk/description.tex
> index 20007e3..517b012 100644
> --- a/device-types/blk/description.tex
> +++ b/device-types/blk/description.tex
> @@ -83,6 +83,54 @@ \subsubsection{Legacy Interface: Feature bits}\label{sec:Device Types / Block De
>
> \subsection{Device configuration layout}\label{sec:Device Types / Block Device / Device configuration layout}
>
> +The block device has the following device configuration layout.
> +
> +\begin{lstlisting}
> +struct virtio_blk_config {
> + le64 capacity;
> + le32 size_max;
> + le32 seg_max;
> + struct virtio_blk_geometry {
> + le16 cylinders;
> + u8 heads;
> + u8 sectors;
> + } geometry;
> + le32 blk_size;
> + struct virtio_blk_topology {
> + // # of logical blocks per physical block (log2)
> + u8 physical_block_exp;
> + // offset of first aligned logical block
> + u8 alignment_offset;
> + // suggested minimum I/O size in blocks
> + le16 min_io_size;
> + // optimal (suggested maximum) I/O size in blocks
> + le32 opt_io_size;
> + } topology;
> + u8 writeback;
> + u8 unused0;
> + u16 num_queues;
> + le32 max_discard_sectors;
> + le32 max_discard_seg;
> + le32 discard_sector_alignment;
> + le32 max_write_zeroes_sectors;
> + le32 max_write_zeroes_seg;
> + u8 write_zeroes_may_unmap;
> + u8 unused1[3];
> + le32 max_secure_erase_sectors;
> + le32 max_secure_erase_seg;
> + le32 secure_erase_sector_alignment;
> + struct virtio_blk_zoned_characteristics {
> + le32 zone_sectors;
> + le32 max_open_zones;
> + le32 max_active_zones;
> + le32 max_append_sectors;
> + le32 write_granularity;
> + u8 model;
> + u8 unused2[3];
> + } zoned;
> +};
> +\end{lstlisting}
> +
> The \field{capacity} of the device (expressed in 512-byte sectors) is always
> present. The availability of the others all depend on various feature
> bits as indicated above.
> @@ -167,53 +215,6 @@ \subsection{Device configuration layout}\label{sec:Device Types / Block Device /
> terminated by the device with a "zone resources exceeded" error as defined for
> specific commands later.
>
> -\begin{lstlisting}
> -struct virtio_blk_config {
> - le64 capacity;
> - le32 size_max;
> - le32 seg_max;
> - struct virtio_blk_geometry {
> - le16 cylinders;
> - u8 heads;
> - u8 sectors;
> - } geometry;
> - le32 blk_size;
> - struct virtio_blk_topology {
> - // # of logical blocks per physical block (log2)
> - u8 physical_block_exp;
> - // offset of first aligned logical block
> - u8 alignment_offset;
> - // suggested minimum I/O size in blocks
> - le16 min_io_size;
> - // optimal (suggested maximum) I/O size in blocks
> - le32 opt_io_size;
> - } topology;
> - u8 writeback;
> - u8 unused0;
> - u16 num_queues;
> - le32 max_discard_sectors;
> - le32 max_discard_seg;
> - le32 discard_sector_alignment;
> - le32 max_write_zeroes_sectors;
> - le32 max_write_zeroes_seg;
> - u8 write_zeroes_may_unmap;
> - u8 unused1[3];
> - le32 max_secure_erase_sectors;
> - le32 max_secure_erase_seg;
> - le32 secure_erase_sector_alignment;
> - struct virtio_blk_zoned_characteristics {
> - le32 zone_sectors;
> - le32 max_open_zones;
> - le32 max_active_zones;
> - le32 max_append_sectors;
> - le32 write_granularity;
> - u8 model;
> - u8 unused2[3];
> - } zoned;
> -};
> -\end{lstlisting}
> -
> -
> \subsubsection{Legacy Interface: Device configuration layout}\label{sec:Device Types / Block Device / Device configuration layout / Legacy Interface: Device configuration layout}
> When using the legacy interface, transitional devices and drivers
> MUST format the fields in struct virtio_blk_config
> --
> 2.26.2
Yes, please!
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* [virtio-dev] RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
2023-02-23 20:46 ` [virtio-comment] " Stefan Hajnoczi
@ 2023-03-12 13:22 ` Parav Pandit
0 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-12 13:22 UTC (permalink / raw)
To: Stefan Hajnoczi
Cc: mst, virtio-dev, cohuck, virtio-comment, Shahaf Shuler, Max Gurtovoy
> From: Stefan Hajnoczi <stefanha@redhat.com>
> Sent: Thursday, February 23, 2023 3:46 PM
>
> On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > Define device configuration layout structure before describing its
> > individual fields.
> >
> > This is an editorial change.
> >
> > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > ---
> > device-types/blk/description.tex | 95
[..]
> Yes, please!
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Hi Cornelia,
Can you please merge this?
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
@ 2023-03-12 13:22 ` Parav Pandit
0 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-12 13:22 UTC (permalink / raw)
To: Stefan Hajnoczi
Cc: mst, virtio-dev, cohuck, virtio-comment, Shahaf Shuler, Max Gurtovoy
> From: Stefan Hajnoczi <stefanha@redhat.com>
> Sent: Thursday, February 23, 2023 3:46 PM
>
> On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > Define device configuration layout structure before describing its
> > individual fields.
> >
> > This is an editorial change.
> >
> > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > ---
> > device-types/blk/description.tex | 95
[..]
> Yes, please!
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Hi Cornelia,
Can you please merge this?
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/
^ permalink raw reply [flat|nested] 10+ messages in thread
* [virtio-dev] RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
2023-03-12 13:22 ` Parav Pandit
@ 2023-03-15 14:24 ` Parav Pandit
-1 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-15 14:24 UTC (permalink / raw)
To: Parav Pandit, Stefan Hajnoczi
Cc: mst, virtio-dev, cohuck, virtio-comment, Shahaf Shuler, Max Gurtovoy
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Parav Pandit
>
> > From: Stefan Hajnoczi <stefanha@redhat.com>
> > Sent: Thursday, February 23, 2023 3:46 PM
> >
> > On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > > Define device configuration layout structure before describing its
> > > individual fields.
> > >
> > > This is an editorial change.
> > >
> > > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > ---
> > > device-types/blk/description.tex | 95
>
> [..]
>
> > Yes, please!
> >
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> Hi Cornelia,
>
> Can you please merge this?
Any updates?
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
@ 2023-03-15 14:24 ` Parav Pandit
0 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-15 14:24 UTC (permalink / raw)
To: Parav Pandit, Stefan Hajnoczi
Cc: mst, virtio-dev, cohuck, virtio-comment, Shahaf Shuler, Max Gurtovoy
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Parav Pandit
>
> > From: Stefan Hajnoczi <stefanha@redhat.com>
> > Sent: Thursday, February 23, 2023 3:46 PM
> >
> > On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > > Define device configuration layout structure before describing its
> > > individual fields.
> > >
> > > This is an editorial change.
> > >
> > > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > ---
> > > device-types/blk/description.tex | 95
>
> [..]
>
> > Yes, please!
> >
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> Hi Cornelia,
>
> Can you please merge this?
Any updates?
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/
^ permalink raw reply [flat|nested] 10+ messages in thread
* [virtio-dev] Re: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
2023-03-15 14:24 ` Parav Pandit
@ 2023-03-15 15:00 ` Michael S. Tsirkin
-1 siblings, 0 replies; 10+ messages in thread
From: Michael S. Tsirkin @ 2023-03-15 15:00 UTC (permalink / raw)
To: Parav Pandit
Cc: Stefan Hajnoczi, virtio-dev, cohuck, virtio-comment,
Shahaf Shuler, Max Gurtovoy
On Wed, Mar 15, 2023 at 02:24:27PM +0000, Parav Pandit wrote:
>
> > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> > open.org> On Behalf Of Parav Pandit
> >
> > > From: Stefan Hajnoczi <stefanha@redhat.com>
> > > Sent: Thursday, February 23, 2023 3:46 PM
> > >
> > > On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > > > Define device configuration layout structure before describing its
> > > > individual fields.
> > > >
> > > > This is an editorial change.
> > > >
> > > > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > > > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > > ---
> > > > device-types/blk/description.tex | 95
> >
> > [..]
> >
> > > Yes, please!
> > >
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> >
> > Hi Cornelia,
> >
> > Can you please merge this?
>
> Any updates?
Pushed, thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
@ 2023-03-15 15:00 ` Michael S. Tsirkin
0 siblings, 0 replies; 10+ messages in thread
From: Michael S. Tsirkin @ 2023-03-15 15:00 UTC (permalink / raw)
To: Parav Pandit
Cc: Stefan Hajnoczi, virtio-dev, cohuck, virtio-comment,
Shahaf Shuler, Max Gurtovoy
On Wed, Mar 15, 2023 at 02:24:27PM +0000, Parav Pandit wrote:
>
> > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> > open.org> On Behalf Of Parav Pandit
> >
> > > From: Stefan Hajnoczi <stefanha@redhat.com>
> > > Sent: Thursday, February 23, 2023 3:46 PM
> > >
> > > On Thu, Feb 23, 2023 at 03:52:05PM +0200, Parav Pandit wrote:
> > > > Define device configuration layout structure before describing its
> > > > individual fields.
> > > >
> > > > This is an editorial change.
> > > >
> > > > Suggested-by: Cornelia Huck <cohuck@redhat.com>
> > > > Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> > > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > > > ---
> > > > device-types/blk/description.tex | 95
> >
> > [..]
> >
> > > Yes, please!
> > >
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> >
> > Hi Cornelia,
> >
> > Can you please merge this?
>
> Any updates?
Pushed, thanks!
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/
^ permalink raw reply [flat|nested] 10+ messages in thread
* [virtio-dev] RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
2023-03-15 15:00 ` Michael S. Tsirkin
@ 2023-03-15 15:12 ` Parav Pandit
-1 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-15 15:12 UTC (permalink / raw)
To: Michael S. Tsirkin
Cc: Stefan Hajnoczi, virtio-dev, cohuck, virtio-comment,
Shahaf Shuler, Max Gurtovoy
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Michael S. Tsirkin
> > > Hi Cornelia,
> > >
> > > Can you please merge this?
> >
> > Any updates?
>
> Pushed, thanks!
Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [virtio-comment] [PATCH] virtio-blk: Define dev cfg layout before its fields
@ 2023-03-15 15:12 ` Parav Pandit
0 siblings, 0 replies; 10+ messages in thread
From: Parav Pandit @ 2023-03-15 15:12 UTC (permalink / raw)
To: Michael S. Tsirkin
Cc: Stefan Hajnoczi, virtio-dev, cohuck, virtio-comment,
Shahaf Shuler, Max Gurtovoy
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Michael S. Tsirkin
> > > Hi Cornelia,
> > >
> > > Can you please merge this?
> >
> > Any updates?
>
> Pushed, thanks!
Thank you.
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/
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-03-15 15:12 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-23 13:52 [PATCH] virtio-blk: Define dev cfg layout before its fields Parav Pandit
2023-02-23 20:46 ` [virtio-comment] " Stefan Hajnoczi
2023-03-12 13:22 ` [virtio-dev] " Parav Pandit
2023-03-12 13:22 ` Parav Pandit
2023-03-15 14:24 ` [virtio-dev] " Parav Pandit
2023-03-15 14:24 ` Parav Pandit
2023-03-15 15:00 ` [virtio-dev] " Michael S. Tsirkin
2023-03-15 15:00 ` Michael S. Tsirkin
2023-03-15 15:12 ` [virtio-dev] " Parav Pandit
2023-03-15 15:12 ` Parav Pandit
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.