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]
Date:	Wed, 21 Jan 2015 15:48:57 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Jiang Liu <jiang.liu@...ux.intel.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Yinghai Lu <yinghai@...nel.org>,
	Borislav Petkov <bp@...en8.de>, Len Brown <lenb@...nel.org>,
	Tony Luck <tony.luck@...el.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: [RFC Patch 08/19] ACPI: Add prefetch decoding to the address space parser

On Wednesday, January 21, 2015 01:26:25 PM Jiang Liu wrote:
> On 2015/1/21 8:35, Rafael J. Wysocki wrote:
> > On Thursday, January 08, 2015 10:32:55 AM Jiang Liu wrote:
> >> From: Thomas Gleixner <tglx@...utronix.de>
> >>
> >> Add support of PREFETCH attributre to ACPI address space and extended
> >> address space parser.
> > 
> > This potentially enables untested configurations which tends to uncover bugs,
> > so I'm concerned.
> > 
> > What's the possible impact of this?
> Hi Rafael,
> 	I have analyzed all call sites related to this change, most
> users just care about resource type(IO, MEM, IRQ etc) and ignore
> the prefetch property. Seems only PCI subsystem cares about PREFETCH.

OK


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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