From: Jason Wang <jasowang@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Dongli Zhang <dongli.zhang@oracle.com>
Cc: berrange@redhat.com, ehabkost@redhat.com, mst@redhat.com,
joe.jin@oracle.com, qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [PATCH RFC 0/1] To add HMP interface to dump PCI MSI-X table/PBA
Date: Wed, 28 Apr 2021 10:31:52 +0800 [thread overview]
Message-ID: <37e7aa41-5c87-3276-67f6-b5bd64dde7ea@redhat.com> (raw)
In-Reply-To: <YIfRAKDvfZyOWrEL@work-vm>
在 2021/4/27 下午4:53, Dr. David Alan Gilbert 写道:
> * Dongli Zhang (dongli.zhang@oracle.com) wrote:
>>
>> On 4/22/21 11:01 PM, Jason Wang wrote:
>>> 在 2021/4/23 下午12:47, Dongli Zhang 写道:
>>>> This is inspired by the discussion with Jason on below patchset.
>>>>
>>>> https://urldefense.com/v3/__https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg09020.html__;!!GqivPVa7Brio!KbGQZW5lq3JZ60k12NuWZ6Th1lT6AwmBTF0pBgoWUKKQ4-2UhdW57PtvXUN5XQnZ2NU$
>>>>
>>>> The new HMP command is introduced to dump the MSI-X table and PBA.
>>>>
>>>> Initially, I was going to add new option to "info pci". However, as the
>>>> number of entries is not determined and the output of MSI-X table is much
>>>> more similar to the output of hmp_info_tlb()/hmp_info_mem(), this patch
>>>> adds interface for only HMP.
>>>>
>>>> The patch is tagged with RFC because I am looking for suggestions on:
>>>>
>>>> 1. Is it fine to add new "info msix <dev>" command?
>>>
>>> I wonder the reason for not simply reusing "info pci"?
>> The "info pci" will show PCI data for all devices and it does not accept any
>> argument to print for a specific device.
>>
>> In addition, the "info pci" relies on qmp_query_pci(), where this patch will not
>> implement the interface for QMP considering the number of MSI-X entries is not
>> determined.
>>
>> Suppose we have 10 NVMe (emulated by QEMU with default number of queues), we
>> will have about 600+ lines of output.
> From an HMP perspective I'm happy, so:
>
> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> but since I don't know much about MSI I'd like to see Jason's reply.
I think we'd better have more information, e.g the device can optionally
report how the MSI-X vector is used.
Virtio-pci could be the first user for this.
>
> Adding an optional option to 'info pci' to limit to one device would be easy
> though; that bit is probably easier than adding a new command.
One interesting point is that MSI could be extended for other bus, (e.g
MMIO). So "info msi" should be better I guess.
> Figuring out the QMP representation of your entries might be harder -
> and if this is strictly for debug, probably not worth it?
I think so.
Thanks
>
> Dave
>
>
>> Dongli Zhang
>>
>>>
>>>> 2. Is there any issue with output format?
>>>
>>> If it's not for QMP, I guess it's not a part of ABI so it should be fine.
>>>
>>>
>>>> 3. Is it fine to add only for HMP, but not QMP?
>>>
>>> I think so.
>>>
>>> Thanks
>>>
>>>
>>>> Thank you very much!
>>>>
>>>> Dongli Zhang
>>>>
>>>>
>>>>
next prev parent reply other threads:[~2021-04-28 2:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 4:47 [PATCH RFC 0/1] To add HMP interface to dump PCI MSI-X table/PBA Dongli Zhang
2021-04-23 4:47 ` [PATCH RFC 1/1] msix: add hmp interface to dump MSI-X info Dongli Zhang
2021-04-23 7:59 ` Jason Wang
2021-04-23 17:32 ` Dongli Zhang
2021-04-25 3:36 ` Jason Wang
2021-04-26 5:41 ` Dongli Zhang
2021-04-23 6:01 ` [PATCH RFC 0/1] To add HMP interface to dump PCI MSI-X table/PBA Jason Wang
2021-04-23 17:26 ` Dongli Zhang
2021-04-25 3:34 ` Jason Wang
2021-04-27 8:53 ` Dr. David Alan Gilbert
2021-04-28 2:31 ` Jason Wang [this message]
2021-04-28 5:10 ` Dongli Zhang
2021-04-28 5:55 ` Jason Wang
2021-04-28 6:25 ` Dongli Zhang
2021-04-28 8:45 ` Dr. David Alan Gilbert
2021-04-28 15:59 ` Dongli Zhang
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=37e7aa41-5c87-3276-67f6-b5bd64dde7ea@redhat.com \
--to=jasowang@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=dongli.zhang@oracle.com \
--cc=ehabkost@redhat.com \
--cc=joe.jin@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).