From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Hecht Subject: Re: + stupid-hack-to-make-mainline-build.patch added to -mm tree Date: Wed, 07 Mar 2007 13:02:32 -0800 Message-ID: <45EF2868.8050009@vmware.com> References: <200703060654.l266sVxr014860@shell0.pdx.osdl.net> <45ED16D2.3000202@vmware.com> <20070306084258.GA15745@elte.hu> <20070306084647.GA16280@elte.hu> <45ED2C82.3080008@vmware.com> <1173178774.24738.311.camel@localhost.localdomain> <45EDD82F.90204@vmware.com> <1173225182.24738.507.camel@localhost.localdomain> <45EE0628.1080108@goop.org> <45EE08E8.2020008@vmware.com> <1173228544.24738.514.camel@localhost.localdomain> <45EE0D10.7070807@vmware.com> <1173230305.24738.529.camel@localhost.localdomain> <45EE1EA3.90803@vmware.com> <1173256666.24738.576.camel@localhost.localdomain> <45EEF966.6060902@goop.org> <45EF0CF5.5090305@goop.org> <45EF175D.6030609@vmware.com> <45EF1C80.50900@goop.org> <1173301065.24738.766.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1173301065.24738.766.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org To: tglx@linutronix.de Cc: Jeremy Fitzhardinge , James Morris , Virtualization Mailing List , akpm@linux-foundation.org, john stultz , Ingo Molnar , LKML List-Id: virtualization@lists.linuxfoundation.org On 03/07/2007 12:57 PM, Thomas Gleixner wrote: > On Wed, 2007-03-07 at 12:11 -0800, Jeremy Fitzhardinge wrote: >> Dan Hecht wrote: >>> Jeremy, I saw you sent out the Xen version earlier, thanks. Here's >>> ours for reference (please excuse any formating issues); it's also >>> lean. We'll send out a proper patch later after some more testing: >> So the interrupt side of the clockevent comes through the virtual apic? >> Where does evt->handle_event get called? > > >> /* We use normal irq0 handler on cpu0. */ >> time_init_hook(); > > That's exactly the thing I ranted about before. We keep the historic > view of emulated hardware and just wrap it into enough glue code instead > of doing an abstract design, which just gets rid of those hardware > assumptions at all. That's the big advantage of paravirtualization, but > the current way on paravirt ops is just ignoring this. > Are you saying you would prefer we create our own irq handler something like this rather than using the standard i386 handlers? irqreturn_t vmi_timer_interrupt(int irq, void *dev_id) { local_event->event_handler(local_event); return IRQ_HANDLED; } ?? That's fine with me.