linux-kernel - Re: [PATCH 1/2] x86, ioapic: Reserve only 128 bytes for IOAPICs

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: <20110826093917.GE3903@sun>
Date:	Fri, 26 Aug 2011 13:39:18 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Ralf Jung <ralfjung-e@....de>, Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Yinghai Lu <yinghai@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] x86, ioapic: Reserve only 128 bytes for IOAPICs

On Fri, Aug 26, 2011 at 11:22:32AM +0200, Ralf Jung wrote:
> Hi,
> 
> > I rather wonder if there a way to assign a different address for the
> > watchdog Bjorn referring to. I don't have such machine to test but
> > seems its base address is configurable via pmio. Just curious.
>
> That would be the watchdog in my laptop then, I guess (I'm the reporter of the 
> bug mentioned by Bjorn)? I don't know much about all the inner workings, but 
> if you send me patches I can tell you what they do.
> 
> Kind regards,
> Ralf

Hi Ralf, I can't put that risk on you. Hell knows how it will react
on such reprogramming (which is seems rather a bios duty than kernel).

Bjorn, from where we pick this address at moment, it's obtained via
pci config?

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