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] [day] [month] [year] [list]
Date:	Thu, 9 Dec 2010 09:54:24 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, Matthew Garrett <mjg@...hat.com>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH] x86/PCI: never allocate PCI space from the last 1M below 4G

On Friday, December 03, 2010 08:15:48 am Bjorn Helgaas wrote:
> On Thursday, December 02, 2010 06:19:20 pm Linus Torvalds wrote:
> > On Mon, Nov 29, 2010 at 2:04 PM, Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> > >
> > > I think we're talking about whether to reserve the top 1MB or top 2MB.
> > > I freely admit I don't know the right answer.  My point is merely that
> > > since we're using a heuristic anyway, copying Windows is a pretty good
> > > starting point.  In my mind, doing something different requires a
> > > stronger argument than "it might fix some machines where Windows is
> > > broken."
> > 
> > What's the status of this? The original patch is pretty nasty, and I
> > think that hack to put things in the bios_align_resource() function is
> > just disgusting.

OK, let's drop this approach.  My next proposal is the
"PCI, PNP, resources: effectively reserve ACPI device resources"
thread I posted yesterday (with mangled cover letter) here:

    https://lkml.org/lkml/2010/12/8/352

Bjorn
--
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