Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932547AbZLRSPj (ORCPT ); Fri, 18 Dec 2009 13:15:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932523AbZLRSOw (ORCPT ); Fri, 18 Dec 2009 13:14:52 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:37259 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932343AbZLRSMK (ORCPT ); Fri, 18 Dec 2009 13:12:10 -0500 Date: Fri, 18 Dec 2009 19:11:44 +0100 From: Pavel Machek To: Huang Ying Cc: lenb@kernel.org, ACPI Devel Maling List , Andi Kleen , "linux-kernel@vger.kernel.org" Subject: Re: [PATH 1/5 -v2] acpi, IO memory pre-mapping and atomic accessing Message-ID: <20091218181144.GB1470@ucw.cz> References: <1260429413.15264.393.camel@yhuang-dev.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1260429413.15264.393.camel@yhuang-dev.sh.intel.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 694 Lines: 19 Hi! > Some ACPI IO accessing need to be done in atomic context. For example, Does it? Maybe better fix would be to make sure acpi interpretter can't be ran from interrupt context -- just create threads for it...? It would solve a lot of uglyness with acpi trying to guess if it can sleep etc... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/