From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Lukas Wunner" <lukas@wunner.de>,
"Keith Busch" <kbusch@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Parav Pandit" <parav@nvidia.com>,
virtualization@lists.linux.dev, stefanha@redhat.com,
alok.a.tiwari@oracle.com, "Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Subject: [PATCH RFC v4 3/5] virtio: pack config changed flags
Date: Thu, 3 Jul 2025 05:26:32 -0400 [thread overview]
Message-ID: <ae1546541834abe3296c6341f6dd02a73a49f29a.1751534711.git.mst@redhat.com> (raw)
In-Reply-To: <cover.1751534711.git.mst@redhat.com>
In anticipation of adding more, use bit-fields instead of bool.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
include/linux/virtio.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index 64cb4b04be7a..be0beb16b487 100644
--- a/include/linux/virtio.h
+++ b/include/linux/virtio.h
@@ -149,9 +149,9 @@ struct virtio_admin_cmd {
struct virtio_device {
int index;
bool failed;
- bool config_core_enabled;
- bool config_driver_disabled;
- bool config_change_pending;
+ u8 config_core_enabled:1;
+ u8 config_driver_disabled:1;
+ u8 config_change_pending:1;
spinlock_t config_lock;
spinlock_t vqs_list_lock;
struct device dev;
--
MST
next prev parent reply other threads:[~2025-07-03 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 9:26 [PATCH RFC v4 0/5] pci,virtio: report surprise removal event Michael S. Tsirkin
2025-07-03 9:26 ` [PATCH RFC v4 1/5] pci: " Michael S. Tsirkin
2025-07-03 9:26 ` [PATCH RFC v4 2/5] virtio: fix comments, readability Michael S. Tsirkin
2025-07-07 3:32 ` Jason Wang
2025-07-03 9:26 ` Michael S. Tsirkin [this message]
2025-07-03 9:26 ` [PATCH RFC v4 4/5] virtio: allow transports to suppress config change Michael S. Tsirkin
2025-07-03 9:26 ` [PATCH RFC v4 5/5] virtio: support device disconnect Michael S. Tsirkin
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=ae1546541834abe3296c6341f6dd02a73a49f29a.1751534711.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=alok.a.tiwari@oracle.com \
--cc=bhelgaas@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=parav@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®