lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <273e0882-24f5-465a-be18-d67b4249ce12@linux.microsoft.com>
Date: Tue, 7 Oct 2025 13:38:02 -0700
From: Roman Kisel <romank@...ux.microsoft.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: benhill@...rosoft.com, bperkins@...rosoft.com, sunilmut@...rosoft.com,
 arnd@...db.de, bp@...en8.de, corbet@....net, dave.hansen@...ux.intel.com,
 decui@...rosoft.com, haiyangz@...rosoft.com, hpa@...or.com,
 kys@...rosoft.com, mikelley@...rosoft.com, mingo@...hat.com,
 tglx@...utronix.de, Tianyu.Lan@...rosoft.com, wei.liu@...nel.org,
 x86@...nel.org, linux-hyperv@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH hyperv-next v6 01/17] Documentation: hyperv: Confidential
 VMBus



On 10/6/2025 7:23 PM, Bagas Sanjaya wrote:
> On Fri, Oct 03, 2025 at 03:26:54PM -0700, Roman Kisel wrote:
>> +The data is transferred directly between the VM and a vPCI device (a.k.a.
>> +a PCI pass-thru device, see :doc:`vpci`) that is directly assigned to VTL2
>> +and that supports encrypted memory. In such a case, neither the host partition
> 
> Nit: You can also write the cross-reference simply as vpci.rst.
> 

Thanks for helping out! I could not find that way of cross-referencing
in the Sphinx documentation though:
https://www.sphinx-doc.org/en/master/usage/referencing.html#cross-referencing-documents

I tried it out anyway. The suggestion worked out only for the HTML
documentation, and would not work for the PDF one. Options attempted:

1. vpci
2. vpci.rst
3. Documentation/virt/hyperv/vpci
4. Documentation/virt/hyperv/vpci.rst

and neither would produce a hyperlink inside virt.pdf. Options 2 & 4
generated a hyperlink in HTML.

The

| :doc:`vpci`

directive I've used produces a hyperlink both for HTML & PDF and is
mentioned in the Sphinx documentation linked above.

Please let me know if I misunderstood your suggestion and/or tested
it in a wrong way. So far, it appears that it works only for HTML.

> Thanks.
> 

-- 
Thank you,
Roman


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ