[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 1/2] x86/iommu: avoid mapping the interrupt address range for hwdom
- To: Roger Pau Monne <roger.pau@xxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- From: Jan Beulich <JBeulich@xxxxxxxx>
- Date: Thu, 25 Jul 2019 10:22:17 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=suse.com;dmarc=pass action=none header.from=suse.com;dkim=pass header.d=suse.com;arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yrn1fN/uixDX5g+Vokpt36zTRs8X8mNHVVtkbz75oGg=; b=i3wuJhYN5UfOdrIf9afJTlH7XkyGrEl00nkX+Ca/st0USLcHNeig9i+iQyEUH4Z/Gnz+CkftI1LtR2Z4JzZarfvSKx/TCH478MKro5vEixWIxegeGXSfg9DOi0xNvghapnkylKbYsmxWm7Jl6X3YORNxAb7FiCmrCOCjQrc/d3xa6GqAJvdO/djjAfhHKGVtoK6qYUCrd/8YabK59Qz0C3VzCQS9BcI0dOPw1FArDOpU8vhYiPfl6EBg0SNDROnLiMFuWWlfPp//mZ8Xr4NQvQnLtLmmmLnfZqqB3FU2sP+Njz71o/O1UrVpeLeZgvV2uUbM6oWZbx+P7KXUa5e08Q==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bHuyBqf2LxpOiHb36EfzsgumYexrO5A5lQGRAECZZE1Zyb4Bxkzhy+lWCCwbiV+gCkaJ8TD9xJvWO29QN60mdAskZwKsabwDJ8RMqtAs2HQRFOTIlfdyOvQtUG7W+iXqDrghJFIYfb09iOyTGRZy4GB7Hd+t81aoBBV6g1HtlLxodP15kvu0dNvRyNR2q8PnI5b5ULF1vKQe0QTXdlxO74JfW9BIJP5s+UTAG9y97485gA1kBuExrn+9VdSK5g8q8fSMhWKKeIDiD3EVOTyjDPJFPikq9SDrOKfpNFnorw6IHe3GRawOSucLbG3YKM8dWZOfM24JZSIaQTIhI7MUgQ==
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=JBeulich@xxxxxxxx;
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Thu, 25 Jul 2019 10:24:30 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHVQW4v+Mw2bodxPUiy9HdTXv5ycabbIsgA
- Thread-topic: [PATCH 1/2] x86/iommu: avoid mapping the interrupt address range for hwdom
On 23.07.2019 17:48, Roger Pau Monne wrote:
> Current code only prevent mapping the lapic page into the guest
> physical memory map. Expand the range to be 0xFEEx_xxxx as described
> in the Intel VTd specification section 3.13 "Handling Requests to
> Interrupt Address Range".
>
> AMD also lists this address range in the AMD SR5690 Databook, section
> 2.4.4 "MSI Interrupt Handling and MSI to HT Interrupt Conversion".
>
> Requested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
I've committed this on the basis that it shouldn't hurt, but having
thought about this some more I'm not really sure I see the point:
The IOMMU special cases accesses into this range anyway, to redirect
lookup to the interrupt remapping table instead of the DMA remapping
one. Hence any mappings inserted into this range are simply useless,
but shouldn't otherwise hurt.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
