# RE: \[PATCH 1/1\] Documentation: hyperv: Update docs for PCI pass-thru device support

- From: Michael Kelley \<hidden\>
- Date: 2026-11-03 04:50:53 
- List: linux-hyperv
- Page: https://ratatoskr.run/linux-hyperv/2026/11/17849552
- Thread: https://ratatoskr.run/linux-hyperv/2026/11/17838824/t.md

```text
From: Daniel Pereira <danielmaraboo@gmail.com> Sent: Monday, November 2, 2026 6:12 PM
> 
> Hi !
> 
> > +and unmask interrupts. It becomes the parent domain for the per
> > +device IRQ domain created by the normal Linux driver for the
> 
> I think "per-device" should have a hyphen here too, since it's an adjective.
> 
> > +"irqchip@<paddr>" domain created by the GICv3 driver when it
> > +initiaizes the virtual GICv3 hardware provided to the guest
> 
> Is "initiaizes" a typo? Shouldn't it be "initializes"?
> 
> > +device's MSI/MSI-X registers/tables. The guest writes a virutal
> 
> I think this one is also a typo, right? Shouldn't it be "virtual"?
> 
> > +Once the host-valid MSI message is obtained, the guest must treat it
> > +as a black-box that the guest does not interpret or modify. The only
> 
> "black box" (no hyphen) it's used as a noun here, so it shouldn't be hyphenated.
> 
> > +valid guest action is to write it to the MSI/MSI-X registers/tables
> > +using the .irq_chip_write_msi_msg function on the HV-PCI-MSIX-<PCIaddr>
> 
> struct irq_chip has no .irq_chip_write_msi_msg; shouldn't this be
> .irq_write_msi_msg? Same in the last paragraph.
> 

Thanks for the careful review! Yes, these are typos and hypenation
errors that I'll fix in v2.

Michael
```