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: <20151204143803.GH21177@pd.tnic>
Date:	Fri, 4 Dec 2015 15:38:03 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"Wan, Vincent" <Vincent.Wan@....com>
Cc:	"Wang, Annie" <Annie.Wang@....com>,
	Vinod Koul <vinod.koul@...el.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Joerg Roedel <joro@...tes.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
	"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
	"Huang, Ray" <Ray.Huang@....com>, "Xue, Ken" <Ken.Xue@....com>,
	"Li, Tony" <Tony.Li@....com>
Subject: Re: [PATCH 8/9] Documentation: Add ivrs_acpihid kernel parameter
 description

On Fri, Dec 04, 2015 at 01:19:35PM +0000, Wan, Vincent wrote:
> > > +	ivrs_acpihid	[HW,X86_64]
> > > +			Provide an override to the ACPI-HID:UID<->DEVICE-ID
> > > +			mapping provided in the IVRS ACPI table. For
> > > +			example, to map UART-HID:UID AMD0020:0 to
> > > +			PCI device 00:14.5 write the parameter as:
> > > +				ivrs_acpihid[00:14.5]=AMD0020:0
> > 
> > What is that parameter needed for? Can't you deduce the mapping from the
> > hardware?
> 
> It is very like ivrs_ioapic/ ivrs_hpet, which can override the dedicated BDF id mapped to HID:UID that was reported from BIOS's IVHD entry.
> If BIOS did not report a right BDF, we can resort to this parameter to correct it.

Please add a verbose, human-readable explanation to the text so that
people know what it is for. The text above is hard to parse even for
insiders.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ