From: Kunkun Jiang <jiangkunkun@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "open list:All patches CC here" <qemu-devel@nongnu.org>,
Eric Auger <eric.auger@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
tangnianyao@huawei.com, ganqixin@huawei.com,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH 2/2] vfio/common: Add trace point when a MMIO RAM section less than PAGE_SIZE
Date: Fri, 10 Sep 2021 16:38:22 +0800 [thread overview]
Message-ID: <3fc51a67-954e-d22c-bcb4-0177014dfa74@huawei.com> (raw)
In-Reply-To: <20210908144552.1f7f072e.alex.williamson@redhat.com>
Hi Alex,
On 2021/9/9 4:45, Alex Williamson wrote:
> On Fri, 3 Sep 2021 17:36:11 +0800
> Kunkun Jiang <jiangkunkun@huawei.com> wrote:
>
>> The MSI-X structures of some devices and other non-MSI-X structures
>> are in the same BAR. They may share one host page, especially in the
>> case of large page granularity, suck as 64K.
> s/suck/such/
ok
>> For example, MSIX-Table size of 82599 NIC is 0x30 and the offset in
>> Bar 3(size 64KB) is 0x0. If host page size is 64KB.
>> vfio_listenerregion_add() will be called to map the remaining range
> s/vfio_listenerregion_add/vfio_listener_region_add/
ok
>> (0x30-0xffff). And it will return early at
>> 'int128_ge((int128_make64(iova), llend))' and hasn't any message.
>> Let's add a trace point to informed users like 5c08600547c did.
> Please use the following syntax for referencing previous commits
> (12-char sha1 is standard):
>
> commit 5c08600547c0 ("vfio: Use a trace point when a RAM section
> cannot be DMA mapped")
Thank you for your reply. I will correct it in V2.
Thanks,
Kunkun Jiang
> Thanks,
> Alex
>
>> Signed-off-by: Kunkun Jiang <jiangkunkun@huawei.com>
>> ---
>> hw/vfio/common.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
>> index 8728d4d5c2..2fc6213c0f 100644
>> --- a/hw/vfio/common.c
>> +++ b/hw/vfio/common.c
>> @@ -892,6 +892,13 @@ static void vfio_listener_region_add(MemoryListener *listener,
>> llend = int128_and(llend, int128_exts64(qemu_real_host_page_mask));
>>
>> if (int128_ge(int128_make64(iova), llend)) {
>> + if (memory_region_is_ram_device(section->mr)) {
>> + trace_vfio_listener_region_add_no_dma_map(
>> + memory_region_name(section->mr),
>> + section->offset_within_address_space,
>> + int128_getlo(section->size),
>> + qemu_real_host_page_size);
>> + }
>> return;
>> }
>> end = int128_get64(int128_sub(llend, int128_one()));
> .
prev parent reply other threads:[~2021-09-10 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 9:36 [PATCH 0/2] vfio: Some fixes about vfio-pci MMIO RAM mapping Kunkun Jiang
2021-09-03 9:36 ` [PATCH 1/2] vfio/pci: Fix vfio-pci sub-page MMIO BAR mmaping in live migration Kunkun Jiang
2021-09-08 20:45 ` Alex Williamson
2021-09-10 8:33 ` Kunkun Jiang
2021-09-10 22:24 ` Alex Williamson
2021-09-13 2:44 ` Kunkun Jiang
2021-09-03 9:36 ` [PATCH 2/2] vfio/common: Add trace point when a MMIO RAM section less than PAGE_SIZE Kunkun Jiang
2021-09-08 20:45 ` Alex Williamson
2021-09-10 8:38 ` Kunkun Jiang [this message]
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=3fc51a67-954e-d22c-bcb4-0177014dfa74@huawei.com \
--to=jiangkunkun@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=ganqixin@huawei.com \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=tangnianyao@huawei.com \
--cc=wanghaibin.wang@huawei.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).