From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPu7M-00033C-Gp for qemu-devel@nongnu.org; Sun, 12 Jul 2009 04:09:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPu7K-0002zh-D5 for qemu-devel@nongnu.org; Sun, 12 Jul 2009 04:09:03 -0400 Received: from [199.232.76.173] (port=50065 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPu7K-0002zD-60 for qemu-devel@nongnu.org; Sun, 12 Jul 2009 04:09:02 -0400 Received: from fg-out-1718.google.com ([72.14.220.153]:23980) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MPu7J-0003Ni-PS for qemu-devel@nongnu.org; Sun, 12 Jul 2009 04:09:02 -0400 Received: by fg-out-1718.google.com with SMTP id l27so371131fgb.8 for ; Sun, 12 Jul 2009 01:09:00 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 12 Jul 2009 11:09:00 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH] sparc64: trap handling corrections From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Kovalenko Cc: qemu-devel@nongnu.org On 7/12/09, Igor Kovalenko wrote: > Good trap handling is required to process interrupts. > This patch fixes the following: > > - sparc64 has no wim register > - sparc64 has no psret register, use IE bit of pstate > extract IE checking code to cpu_interrupts_enabled > - alternate globals are not available if cpu has GL feature > in this case bit AG of pstate is constant zero > - write to pstate must actually write pstate > even if cpu has GL feature > > Also timer interrupt is handled using do_interrupt. A bit too much for one patch. Please also remove the code instead of commenting out. PUT_PSR for Sparc64 needs CC_OP = CC_OP_FLAGS; like Sparc32. > Timer interrupt would require attention later when timers > start to tick (currently timers are not really functional). I think this comment is not true, IIRC at least tick and stick counters can be read (and they are used by SILO) and also interrupts work.