From: "Liu, Jing2" <jing2.liu@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Zha Bin <zhabin@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, jasowang@redhat.com,
slp@redhat.com, virtio-dev@lists.oasis-open.org,
qemu-devel@nongnu.org, gerry@linux.alibaba.com,
chao.p.peng@linux.intel.com
Subject: Re: [virtio-dev] Re: [PATCH v2 2/5] virtio-mmio: refactor common functionality
Date: Wed, 12 Feb 2020 10:58:13 +0800 [thread overview]
Message-ID: <787bac48-3fd0-316a-a99a-8c93154dc8e2@linux.intel.com> (raw)
In-Reply-To: <20200211061758-mutt-send-email-mst@kernel.org>
On 2/11/2020 7:19 PM, Michael S. Tsirkin wrote:
> On Mon, Feb 10, 2020 at 05:05:18PM +0800, Zha Bin wrote:
>> From: Liu Jiang <gerry@linux.alibaba.com>
>>
>> Common functionality is refactored into virtio_mmio_common.h
>> in order to MSI support in later patch set.
>>
>> Signed-off-by: Liu Jiang <gerry@linux.alibaba.com>
>> Co-developed-by: Zha Bin <zhabin@linux.alibaba.com>
>> Signed-off-by: Zha Bin <zhabin@linux.alibaba.com>
>> Co-developed-by: Jing Liu <jing2.liu@linux.intel.com>
>> Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
>> Co-developed-by: Chao Peng <chao.p.peng@linux.intel.com>
>> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
> What does this proliferation of header files achieve?
> common with what?
We're considering that the virtio mmio structure is useful for virtio
mmio msi file so refactor out.
e.g. to get the base of virtio_mmio_device from struct msi_desc *desc.
Jing
>> ---
>> drivers/virtio/virtio_mmio.c | 21 +--------------------
>> drivers/virtio/virtio_mmio_common.h | 31 +++++++++++++++++++++++++++++++
>> 2 files changed, 32 insertions(+), 20 deletions(-)
>> create mode 100644 drivers/virtio/virtio_mmio_common.h
>>
>> diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c
>> index 1733ab97..41e1c93 100644
>> --- a/drivers/virtio/virtio_mmio.c
>> +++ b/drivers/virtio/virtio_mmio.c
>> @@ -61,13 +61,12 @@
>> #include <linux/io.h>
>> #include <linux/list.h>
>> #include <linux/module.h>
>> -#include <linux/platform_device.h>
>> #include <linux/slab.h>
>> #include <linux/spinlock.h>
>> -#include <linux/virtio.h>
>> #include <linux/virtio_config.h>
>> #include <uapi/linux/virtio_mmio.h>
>> #include <linux/virtio_ring.h>
>> +#include "virtio_mmio_common.h"
>>
>>
>>
>> @@ -77,24 +76,6 @@
>>
>>
>>
>> -#define to_virtio_mmio_device(_plat_dev) \
>> - container_of(_plat_dev, struct virtio_mmio_device, vdev)
>> -
>> -struct virtio_mmio_device {
>> - struct virtio_device vdev;
>> - struct platform_device *pdev;
>> -
>> - void __iomem *base;
>> - unsigned long version;
>> -
>> - /* a list of queues so we can dispatch IRQs */
>> - spinlock_t lock;
>> - struct list_head virtqueues;
>> -
>> - unsigned short notify_base;
>> - unsigned short notify_multiplier;
>> -};
>> -
>> struct virtio_mmio_vq_info {
>> /* the actual virtqueue */
>> struct virtqueue *vq;
>> diff --git a/drivers/virtio/virtio_mmio_common.h b/drivers/virtio/virtio_mmio_common.h
>> new file mode 100644
>> index 0000000..90cb304
>> --- /dev/null
>> +++ b/drivers/virtio/virtio_mmio_common.h
>> @@ -0,0 +1,31 @@
>> +/* SPDX-License-Identifier: GPL-2.0-or-later */
>> +#ifndef _DRIVERS_VIRTIO_VIRTIO_MMIO_COMMON_H
>> +#define _DRIVERS_VIRTIO_VIRTIO_MMIO_COMMON_H
>> +/*
>> + * Virtio MMIO driver - common functionality for all device versions
>> + *
>> + * This module allows virtio devices to be used over a memory-mapped device.
>> + */
>> +
>> +#include <linux/platform_device.h>
>> +#include <linux/virtio.h>
>> +
>> +#define to_virtio_mmio_device(_plat_dev) \
>> + container_of(_plat_dev, struct virtio_mmio_device, vdev)
>> +
>> +struct virtio_mmio_device {
>> + struct virtio_device vdev;
>> + struct platform_device *pdev;
>> +
>> + void __iomem *base;
>> + unsigned long version;
>> +
>> + /* a list of queues so we can dispatch IRQs */
>> + spinlock_t lock;
>> + struct list_head virtqueues;
>> +
>> + unsigned short notify_base;
>> + unsigned short notify_multiplier;
>> +};
>> +
>> +#endif
>> --
>> 1.8.3.1
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
next prev parent reply other threads:[~2020-02-12 2:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 9:05 [PATCH v2 0/5] virtio mmio specification enhancement Zha Bin
2020-02-10 9:05 ` [PATCH v2 1/5] virtio-mmio: add notify feature for per-queue Zha Bin
2020-02-11 10:50 ` Michael S. Tsirkin
2020-02-11 11:33 ` Michael S. Tsirkin
2020-02-12 3:39 ` Jason Wang
2020-02-12 8:18 ` Michael S. Tsirkin
2020-02-12 8:53 ` Jason Wang
2020-02-12 9:33 ` Jason Wang
2020-02-12 9:55 ` Michael S. Tsirkin
2020-02-13 3:38 ` Jason Wang
2020-02-10 9:05 ` [PATCH v2 2/5] virtio-mmio: refactor common functionality Zha Bin
2020-02-11 11:19 ` Michael S. Tsirkin
2020-02-12 2:58 ` Liu, Jing2 [this message]
2020-02-12 7:29 ` [virtio-dev] " Michael S. Tsirkin
2020-02-10 9:05 ` [PATCH v2 3/5] virtio-mmio: create a generic MSI irq domain Zha Bin
2020-02-11 11:16 ` Michael S. Tsirkin
2020-02-12 7:40 ` Michael S. Tsirkin
2020-02-10 9:05 ` [PATCH v2 4/5] virtio-mmio: add MSI interrupt feature support Zha Bin
2020-02-11 3:17 ` Jason Wang
2020-02-11 3:35 ` [virtio-dev] " Liu, Jing2
2020-02-11 4:02 ` Jason Wang
[not found] ` <5522f205-207b-b012-6631-3cc77dde3bfe@linux.intel.com>
2020-02-11 7:40 ` Jason Wang
2020-02-11 11:58 ` Michael S. Tsirkin
2020-02-11 12:04 ` Jason Wang
2020-02-11 12:08 ` Michael S. Tsirkin
2020-02-11 12:18 ` Jason Wang
2020-02-11 14:00 ` Michael S. Tsirkin
2020-02-12 9:03 ` Jason Wang
2020-02-12 9:15 ` Michael S. Tsirkin
[not found] ` <4c19292f-9d25-a859-3dde-6dd5a03fdf0b@linux.intel.com>
2020-02-12 7:33 ` Michael S. Tsirkin
2020-02-12 9:06 ` Jason Wang
2020-02-12 9:16 ` Michael S. Tsirkin
2020-02-13 3:40 ` Jason Wang
2020-02-11 11:21 ` Michael S. Tsirkin
2020-02-11 11:11 ` Michael S. Tsirkin
2020-02-10 9:05 ` [PATCH v2 5/5] x86: virtio-mmio: support virtio-mmio with MSI for x86 Zha Bin
2020-02-11 11:14 ` Michael S. Tsirkin
2020-02-10 11:44 ` [PATCH v2 0/5] virtio mmio specification enhancement Michael S. Tsirkin
2020-02-11 16:05 ` Chao Peng
2020-02-11 10:57 ` 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=787bac48-3fd0-316a-a99a-8c93154dc8e2@linux.intel.com \
--to=jing2.liu@linux.intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=gerry@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=zhabin@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;
as well as URLs for NNTP newsgroup(s).