Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: zhukeqian <zhukeqian1@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	"Wanghaibin (D)" <wanghaibin.wang@huawei.com>,
	"sundongxu (A)" <sundongxu3@huawei.com>
Subject: Re: [virtio-comment] [PATCH] pci: Update ISR related description about MSI-X
Date: Tue, 13 Sep 2022 06:46:25 +0000	[thread overview]
Message-ID: <2539b8caa9954d779eba9fae41ea14d5@huawei.com> (raw)

Hi Michael,

>>  
>>  Writing a valid MSI-X Table entry number, 0 to 0x7FF, to  
>> \field{config_msix_vector}/\field{queue_msix_vector} maps interrupts 
>> triggered @@ -1681,6 +1681,8 @@ \subsubsection{Notification of Device 
>> Configuration Changes}\label{sec:Virtio Tr
>>  
>>    \item If MSI-X capability is enabled:
>>      \begin{enumerate}
>> +    \item If \field{config_msix_vector} is not NO_VECTOR, set the second
>> +      lower bit of the ISR Status field for the device.
>
>I think it has to be set always. With NO_VECTOR driver can poll for config changes.

Thanks for pointing it out. I will send v2.

Thanks,
Keqian

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


             reply	other threads:[~2022-09-13  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  6:46 zhukeqian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-02  9:35 [virtio-comment] [PATCH] pci: Update ISR related description about MSI-X Keqian Zhu
2022-09-08 21:16 ` 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=2539b8caa9954d779eba9fae41ea14d5@huawei.com \
    --to=zhukeqian1@huawei.com \
    --cc=mst@redhat.com \
    --cc=sundongxu3@huawei.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --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