From: Si-Wei Liu <si-wei.liu@oracle.com>
To: Eugenio Perez Martin <eperezma@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Lei Yang <leiyang@redhat.com>, Parav Pandit <parav@mellanox.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: Re: [PATCH v2 6/7] vdpa: move iova_tree allocation to net_vhost_vdpa_init
Date: Wed, 14 Feb 2024 10:37:36 -0800 [thread overview]
Message-ID: <1bd4e4da-9ac6-4211-b997-c4002e9ef397@oracle.com> (raw)
In-Reply-To: <CAJaqyWc-OCKf-WR+h7-FoQR=iPO=9tXj3zCDDXNTT4TcejAQ_g@mail.gmail.com>
Hi Eugenio,
Just to answer the question you had in the sync meeting as I've just
tried, it seems that the issue is also reproducible even with VGA device
and VNC display removed, and also reproducible with 8G mem size. You
already knew that I can only repro with x-svq=on.
Regards,
-Siwei
On 2/13/2024 8:26 AM, Eugenio Perez Martin wrote:
> On Tue, Feb 13, 2024 at 11:22 AM Michael S. Tsirkin <mst@redhat.com> wrote:
>> On Mon, Feb 05, 2024 at 05:10:36PM -0800, Si-Wei Liu wrote:
>>> Hi Eugenio,
>>>
>>> I thought this new code looks good to me and the original issue I saw with
>>> x-svq=on should be gone. However, after rebase my tree on top of this,
>>> there's a new failure I found around setting up guest mappings at early
>>> boot, please see attached the specific QEMU config and corresponding event
>>> traces. Haven't checked into the detail yet, thinking you would need to be
>>> aware of ahead.
>>>
>>> Regards,
>>> -Siwei
>> Eugenio were you able to reproduce? Siwei did you have time to
>> look into this? Can't merge patches which are known to break things ...
>>
> Sorry for the lack of news, I'll try to reproduce this week. Meanwhile
> this patch should not be merged, as you mention.
>
> Thanks!
>
next prev parent reply other threads:[~2024-02-14 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 18:09 [PATCH v2 0/7] Move memory listener register to vhost_vdpa_init Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 1/7] vdpa: check for iova tree initialized at net_client_start Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 2/7] vdpa: reorder vhost_vdpa_set_backend_cap Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 3/7] vdpa: set backend capabilities at vhost_vdpa_init Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 4/7] vdpa: add listener_registered Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 5/7] vdpa: reorder listener assignment Eugenio Pérez
2024-02-01 18:09 ` [PATCH v2 6/7] vdpa: move iova_tree allocation to net_vhost_vdpa_init Eugenio Pérez
2024-02-06 1:10 ` Si-Wei Liu
2024-02-13 10:22 ` Michael S. Tsirkin
2024-02-13 16:26 ` Eugenio Perez Martin
2024-02-14 18:37 ` Si-Wei Liu [this message]
2024-02-14 18:29 ` Si-Wei Liu
2024-02-14 19:11 ` Eugenio Perez Martin
2024-04-02 6:19 ` Si-Wei Liu
2024-04-02 12:01 ` Eugenio Perez Martin
2024-04-03 6:53 ` Si-Wei Liu
2024-04-03 8:46 ` Eugenio Perez Martin
2024-02-01 18:09 ` [PATCH v2 7/7] vdpa: move memory listener register to vhost_vdpa_init Eugenio Pérez
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=1bd4e4da-9ac6-4211-b997-c4002e9ef397@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=leiyang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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).