[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH 1/3] xen/vioapic: add support for the extended destination ID field
On 26.01.2022 14:52, David Woodhouse wrote: > On Tue, 2022-01-25 at 16:13 +0100, Roger Pau Monné wrote: >> On Mon, Jan 24, 2022 at 02:20:47PM +0100, Jan Beulich wrote: >>> On 20.01.2022 16:23, Roger Pau Monne wrote: >>>> Such field uses bits 55:48, but for the purposes the register will be >>>> used use bits 55:49 instead. Bit 48 is used to signal an RTE entry is >>>> in remappable format which is not supported by the vIO-APIC. >>> >>> Neither here nor in the cover letter you point at a formal specification >>> of this mode of operation. >> >> I'm not aware of any formal specification of this mode, apart from the >> work done to introduce support in Linux and QEMU: >> >> https://lore.kernel.org/all/20201009104616.1314746-1-dwmw2@xxxxxxxxxxxxx/ >> >> https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c1bb5418e >> >> >> Adding David in case there's some kind of specification somewhere I'm >> not aware of. > > Indeed there is no formal specification that I am aware of, although > it's vaguely possible that Microsoft wrote something up when they added > it to Hyper-V. > > https://lore.kernel.org/all/20201103011136.59108-1-decui@xxxxxxxxxxxxx/ > > I had an internal doc which.... looks like I can clean it up a tiny bit > and then share at http://david.woodhou.se/15-bit-msi.pdf if that helps? Thanks, this at least puts us on common grounds. >>> What I'm aware of are vague indications of >>> this mode's existence in some of Intel's chipset data sheets. Yet that >>> leaves open, for example, whether indeed bit 48 cannot be used here. >> >> Bit 48 cannot be used because it's already used to signal an RTE is in >> remappable format. We still want to differentiate an RTE entry in >> remappable format, as it should be possible to expose both the >> extended ID support and an emulated IOMMU. > > Right. I chose not to use the low bit of the existing Extended > Destination ID because that's the one Intel used to indicate Remappable > Format. This means we can still expose an IOMMU to guests and easily > distinguish between Compatibility Format and Remappable Format MSIs > just as real hardware does. Well, with the defacto standard of using only 7 of the bits we will have to follow suit of course. Jan
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |