[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f3c13be-f65d-1793-bd91-7491d3e149b0@redhat.com>
Date: Mon, 9 Aug 2021 11:03:22 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Joao Martins <joao.m.martins@...cle.com>
Cc: stable@...r.kernel.org, David Matlack <dmatlack@...gle.com>,
Maxim Levitsky <mlevitsk@...hat.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] selftests: KVM: avoid failures due to reserved
HyperTransport region
On 06/08/21 12:57, Joao Martins wrote:
> Base Address Top Address Use
>
> FD_0000_0000h FD_F7FF_FFFFh Reserved interrupt address space
> FD_F800_0000h FD_F8FF_FFFFh Interrupt/EOI IntCtl
> FD_F900_0000h FD_F90F_FFFFh Legacy PIC IACK
> FD_F910_0000h FD_F91F_FFFFh System Management
> FD_F920_0000h FD_FAFF_FFFFh Reserved Page Tables
> FD_FB00_0000h FD_FBFF_FFFFh Address Translation
> FD_FC00_0000h FD_FDFF_FFFFh I/O Space
> FD_FE00_0000h FD_FFFF_FFFFh Configuration
> FE_0000_0000h FE_1FFF_FFFFh Extended Configuration/Device Messages
> FE_2000_0000h FF_FFFF_FFFFh Reserved
The problems we're seeing are with FFFD_0000_0000h. How does the IOMMU
interpret bits 40-47 of the address?
Paolo
Powered by blists - more mailing lists