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: <m1hby293fh.fsf@fess.ebiederm.org>
Date:	Fri, 26 Jun 2009 12:54:10 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"Pan\, Jacob jun" <jacob.jun.pan@...el.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH 8/9] x86/apic: match destination id with destination mode

Ingo Molnar <mingo@...e.hu> writes:

> The question here is whether this should layer on top of Jeremy's 
> IO-APIC driverization patches. I think it should.

The patch is a bad hack that is totally misdocumented.  A bit
like the Xen apic changes in that respect.

I haven't seen Jeremy's IO-APIC driverization patches.  

I am stumped why we need any driverization in this area.  x86_64 and has
had for years a mechanism that is perfectly fine for abstracting this.
i386 also has had something similar and last I looked we just about
had that code merged.

Xen doesn't have ioapics so it doesn't need us faking writes to
ioapics.  Xen either needs to parse the ioapic tables itself
or Xen needs a proper interface to be given the table information.

I this patch can be replaced by a 2 line change to the apic mode
logic to force us into physflat mode on moorestown.

Eric


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