[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161108191022.GA17771@arm.com>
Date: Tue, 8 Nov 2016 19:10:22 +0000
From: Will Deacon <will.deacon@....com>
To: Don Dutile <ddutile@...hat.com>
Cc: Auger Eric <eric.auger@...hat.com>,
Alex Williamson <alex.williamson@...hat.com>,
drjones@...hat.com, jason@...edaemon.net, kvm@...r.kernel.org,
marc.zyngier@....com, benh@...nel.crashing.org, joro@...tes.org,
punit.agrawal@....com, linux-kernel@...r.kernel.org, arnd@...db.de,
diana.craciun@....com, iommu@...ts.linux-foundation.org,
pranav.sawargaonkar@...il.com,
linux-arm-kernel@...ts.infradead.org, jcm@...hat.com,
tglx@...utronix.de, robin.murphy@....com, dwmw@...zon.co.uk,
christoffer.dall@...aro.org, eric.auger.pro@...il.com
Subject: Re: Summary of LPC guest MSI discussion in Santa Fe
On Tue, Nov 08, 2016 at 02:02:39PM -0500, Don Dutile wrote:
> On 11/08/2016 12:54 PM, Will Deacon wrote:
> >A first step would be making all this opt-in, and only supporting GICv3
> >ITS for now.
> You're trying to support a config that is < GICv3 and no ITS ? ...
> That would be the equiv. of x86 pre-intr-remap, and that's why allow_unsafe_interrupts
> hook was created ... to enable devel/kick-the-tires.
Yup, that's exactly what I was envisaging. For systems that can't do
passthrough safely, we'll always have to throw a devel switch.
Will
Powered by blists - more mailing lists