OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [virtio-dev] [PATCH 3/4] vhost-user: add requirements for the notification capability


On Fri, Apr 26, 2019 at 05:14:15PM +0300, Nikos Dragazis wrote:
> On 24/4/19 10:36 Î.Î., Stefan Hajnoczi wrote:
> 
> > On Tue, Apr 23, 2019 at 06:18:18PM +0300, Nikos Dragazis wrote:
> >> The configuration structure for the notification capability has certain
> >> device/driver requirements, similar to those of the MSI-X vector
> >> configuration. Add these requirements to the device spec.
> >>
> >> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
> >> ---
> >>  virtio-vhost-user.tex | 40 ++++++++++++++++++++++++++++++++++++++++
> >>  1 file changed, 40 insertions(+)
> >>
> >> diff --git a/virtio-vhost-user.tex b/virtio-vhost-user.tex
> >> index 0bfc48d..605272f 100644
> >> --- a/virtio-vhost-user.tex
> >> +++ b/virtio-vhost-user.tex
> >> @@ -275,6 +275,46 @@ \subsubsection{Notification structure layout}\label{sec:Device Types / Vhost-use
> >>  \field{VIRTIO_MSI_NO_VECTOR} to \field{notification_msix_vector} to change the
> >>  MSI-X vector for that notification.
> >>  
> >> +\devicenormative{\paragraph}{Notification capability}{Device Types / Vhost-user Device Backend / Additional Device Resources over PCI / Notification capability}
> >> +
> >> +If MSI-X is available, device MUST support mapping any master queue
> >> +event to any valid vector 0 to MSI-X \field{Table Size}. The valid
> > Do you mean Table Size - 1 since vector numbering is zero-based?
> 
> According to the PCI Spec, the "Table Size", which is a portion of the
> Message Control Register of the MSI-X capability structure, is encoded
> as <n-1>, where <n> is the actual table size. For example, a returned
> value of 2047 indicates a table size of 2048, which in turn implies that
> this PCI function supports vectors 0-2047. So, I think it is correct.
> 
> To be honest, I haven't read the actual spec, but this is my
> understanding based on the following sources:
> 
> https://fpgawiki.intel.com/wiki/Implementing_MSI-X_for_PCI_Express_in_Altera_FPGA_Devices#MSI-X_Capability_and_Table_Structures_Programming
> 
> https://www.intel.com/content/www/us/en/programmable/documentation/lbl1415123763821.html#nik1410564944281

Thanks, I have confirmed this by checking the PCI Express specification.

It would be nice to clarify that you mean the n-1 encoded table size,
and not the actual table size here.

Stefan

Attachment: signature.asc
Description: PGP signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]