linux-kernel - Re: [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is disabled in GENERIC_INTERRUPT

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090916090306.GF5094@lenovo>
Date:	Wed, 16 Sep 2009 13:03:06 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Sheng Yang <sheng@...ux.intel.com>,
	Keir Fraser <keir.fraser@...citrix.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	Jun Nakajima <jun.nakajima@...el.com>,
	Eddie Dong <eddie.dong@...el.com>,
	linux-kernel@...r.kernel.org,
	xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is
	disabled in GENERIC_INTERRUPT_VECTOR handler

[Cyrill Gorcunov - Wed, Sep 16, 2009 at 12:58:35PM +0400]
...
| 
| Hi Sheng,
| 
| is there was some problem with it? I'm asking you
| because if disable_apic=1 then any apic write/read
| operations become NOPs. So I don't see how it may
| hurt. But I could be missing something.
|  
| 	-- Cyrill

Ah, I see -- it's due to your other patch...
Hmm this makes all "disable apic" idea less
general. And safety of ack_APIC_irq is now
under suspicious.

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