From: 王贇 <yun.wang@linux.alibaba.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
"open list:VIRTIO CORE AND NET DRIVERS"
<virtualization@lists.linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] virtio: make sure legacy pci device gain 32bit-pfn vq
Date: Thu, 9 Dec 2021 16:26:47 +0800 [thread overview]
Message-ID: <22c1f3f1-beab-83cb-c7ce-d61a970d0f0e@linux.alibaba.com> (raw)
In-Reply-To: <20211209013833-mutt-send-email-mst@kernel.org>
在 2021/12/9 下午2:40, Michael S. Tsirkin 写道:
[snip]
>>>> Besides, I've checked that patch but it can't address our issue, we actually
>>>> have this legacy pci device on arm platform, and the memory layout is
>>>> unfriendly since allocation rarely providing page-address below 44bit, we
>>>> understand the virtio-iommu case should not do force dma, while we don't
>>>> have that so it's just working fine.
>>>>
>>>> Regards,
>>>> Michael Wang
>>>
>>> Hmm wait a sec is it a physical device or a hypervisor?
>>> If a physical one then doesn't it need VIRTIO_F_ORDER_PLATFORM
>>> on ARM?
>>
>> The PCI device is virtual, I can't see how VIRTIO_F_ORDER_PLATFORM help
>> address this issue, legacy pci config is 32bit but it's 36, seems like will
>> never be included?
>>
>> Regards,
>> Michael Wang
>
> Oh, if the device is virtual then I think you should just update it please.
> virtio 0.X is architecturally limited to small VMs,
> if your hypervisor supports more it should emulate virtio 1.0.
I see, nice to confirm the proper approach, although we don't have that
option on the desk :-P
So as long as we don't have any iommu enabled, the force dma approach
could be safe, is this correct?
Regards,
Michael Wang
>
>
>
>>>
>>>
>>>
>>>>>
>>>>>
>>>>>>>
>>>>>>>> ---
>>>>>>>> drivers/virtio/virtio_pci_legacy.c | 10 ++++++++++
>>>>>>>> drivers/virtio/virtio_ring.c | 3 +++
>>>>>>>> include/linux/virtio.h | 1 +
>>>>>>>> 3 files changed, 14 insertions(+)
>>>>>>>>
>>>>>>>> diff --git a/drivers/virtio/virtio_pci_legacy.c
>>>>>>>> b/drivers/virtio/virtio_pci_legacy.c
>>>>>>>> index d62e983..11f2ebf 100644
>>>>>>>> --- a/drivers/virtio/virtio_pci_legacy.c
>>>>>>>> +++ b/drivers/virtio/virtio_pci_legacy.c
>>>>>>>> @@ -263,6 +263,16 @@ int virtio_pci_legacy_probe(struct virtio_pci_device
>>>>>>>> *vp_dev)
>>>>>>>> vp_dev->setup_vq = setup_vq;
>>>>>>>> vp_dev->del_vq = del_vq;
>>>>>>>>
>>>>>>>> + /*
>>>>>>>> + * The legacy pci device requre 32bit-pfn vq,
>>>>>>>> + * or setup_vq() will failed.
>>>>>>>> + *
>>>>>>>> + * Thus we make sure vring_use_dma_api() will
>>>>>>>> + * return true during the allocation by marking
>>>>>>>> + * force_dma here.
>>>>>>>> + */
>>>>>>>> + vp_dev->vdev.force_dma = true;
>>>>>>>> +
>>>>>>>> return 0;
>>>>>>>>
>>>>>>>> err_iomap:
>>>>>>>> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
>>>>>>>> index 3035bb6..6562e01 100644
>>>>>>>> --- a/drivers/virtio/virtio_ring.c
>>>>>>>> +++ b/drivers/virtio/virtio_ring.c
>>>>>>>> @@ -245,6 +245,9 @@ static inline bool virtqueue_use_indirect(struct
>>>>>>>> virtqueue *_vq,
>>>>>>>>
>>>>>>>> static bool vring_use_dma_api(struct virtio_device *vdev)
>>>>>>>> {
>>>>>>>> + if (vdev->force_dma)
>>>>>>>> + return true;
>>>>>>>> +
>>>>>>>> if (!virtio_has_dma_quirk(vdev))
>>>>>>>> return true;
>>>>>>>>
>>>>>>>> diff --git a/include/linux/virtio.h b/include/linux/virtio.h
>>>>>>>> index 41edbc0..a4eb29d 100644
>>>>>>>> --- a/include/linux/virtio.h
>>>>>>>> +++ b/include/linux/virtio.h
>>>>>>>> @@ -109,6 +109,7 @@ struct virtio_device {
>>>>>>>> bool failed;
>>>>>>>> bool config_enabled;
>>>>>>>> bool config_change_pending;
>>>>>>>> + bool force_dma;
>>>>>>>> spinlock_t config_lock;
>>>>>>>> spinlock_t vqs_list_lock; /* Protects VQs list access */
>>>>>>>> struct device dev;
>>>>>>>> --
>>>>>>>> 1.8.3.1
next prev parent reply other threads:[~2021-12-09 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 7:51 王贇
2021-12-07 8:13 ` Michael S. Tsirkin
2021-12-07 9:09 ` 王贇
2021-12-07 10:44 ` Michael S. Tsirkin
2021-12-08 7:23 ` Michael S. Tsirkin
2021-12-08 8:04 ` 王贇
2021-12-08 11:08 ` Michael S. Tsirkin
2021-12-09 3:21 ` 王贇
2021-12-09 6:40 ` Michael S. Tsirkin
2021-12-09 8:26 ` 王贇 [this message]
2021-12-09 17:50 ` Michael S. Tsirkin
2021-12-09 0:19 ` Michael S. Tsirkin
2021-12-09 3:00 ` 王贇
2021-12-09 6:50 ` 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=22c1f3f1-beab-83cb-c7ce-d61a970d0f0e@linux.alibaba.com \
--to=yun.wang@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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®