linux-kernel - Re: [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZ5v0ia+eotSZgjbitt7TAT0ECSmTAz1XJhS3Auz5w5Z61SZA@mail.gmail.com>
Date:   Tue, 11 Dec 2018 22:46:34 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     okaya@...nel.org
Cc:     Christoph Hellwig <hch@...radead.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Len Brown <lenb@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled

On Tue, Dec 11, 2018 at 6:37 PM Sinan Kaya <okaya@...nel.org> wrote:
>
> On 12/11/2018 12:09 PM, Christoph Hellwig wrote:
> > On Mon, Dec 10, 2018 at 06:13:14PM +0000, Sinan Kaya wrote:
> >> Getting ready to allow PCI to be disabled with ACPI enabled. Stub
> >> out calls that depend on PCI.
> >
> > I think you want to skip building at least all of hwpci.c if CONFIG_PCI
> > is disabled.  Or replace that whole stiking pile of crap with something
> > resembling C code..
> >
>
> I can give it a try but I'm under the impression that we don't touch
> ACPICA code in general.
>
> Feel free to correct me.

We don't as a rule, but depending on what the patch looks like, we
might not follow the rule this time.

I wonder though what we do if some AML wants to access PCI config
space via an opregion in there.  Have you thought about that?