linux-kernel - RE: 2.6.30 enabling cpu1 on resume fails after suspend to memory

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0906141548490.2800@localhost.localdomain>
Date:	Sun, 14 Jun 2009 15:49:34 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
cc:	"Benjamin S." <sbenni@....de>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	"js@...21.net" <js@...21.net>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Matthew Wilcox <matthew@....cx>
Subject: RE: 2.6.30 enabling cpu1 on resume fails after suspend to memory

On Sun, 14 Jun 2009, Pallipadi, Venkatesh wrote:
> >Benjamin just confirmed that. The logic in disable_device_interrupts()
> >already skips interrupts marked with IRQF_TIMER, but I suspect that
> >the hpet/MSI interupts are not marked that way.
> >
> 
> For percpu hpet at offline we will have
> - clockevent shutdown which will disable the interrupt
> - free_irq that will unregister on CPU DEAD

Well, the interupt in question is on the boot cpu which is not going
through CPU DEAD :)

Thanks,

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