From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Reset problem vs. MMIO emulation, hypercalls, etc...
Date: Wed, 08 Aug 2012 19:27:12 +1000
Message-ID: <1344418032.2698.40.camel@pasglop>
References: <1343791031.16975.41.camel@pasglop>
	 <501A740F.2000000@redhat.com> <1343938818.6911.9.camel@pasglop>
	 <20120803174113.GA13174@amt.cnet> <1344033008.24037.67.camel@pasglop>
	 <20120806031344.GG16664@truffala.fritz.box>
	 <1344286677.24037.100.camel@pasglop>
	 <20120807013228.GL16664@truffala.fritz.box> <5020D5EB.9060104@redhat.com>
	 <20120807121442.GN16664@truffala.fritz.box> <5021148D.4000107@redhat.com>
	 <1344373762.2698.21.camel@pasglop> <502228C2.1080605@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: David Gibson <dwg@au1.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org,
	Alexander Graf <agraf@suse.de>,
	Paul Mackerras <paulus@au1.ibm.com>, kvm-ppc@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from gate.crashing.org ([63.228.1.57]:56142 "EHLO gate.crashing.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1757957Ab2HHJ1a (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 8 Aug 2012 05:27:30 -0400
In-Reply-To: <502228C2.1080605@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, 2012-08-08 at 11:52 +0300, Avi Kivity wrote:
> > So for now I'm just doing my own version of CREATE_IRQCHIP to create it
> > and KVM_INTERRUPT to trigger the various interrupts. None of the mapping
> > stuff (which we really don't need).
> 
> You mean KVM_IRQ_LINE.  KVM_INTERRUPT is a synchronous vcpu ioctl.

Yes, sorry, brain and fingers not agreeing :-)

> > That's a bit of a problem vs. some of the code qemu-side such as in
> > virtio-pci which does seem to be written around the model exposed by the
> > x86 stuff and relies on doing such mappings so I think we'll have to
> > butcher some of that.
> 
> Can you elaborate? virtio-pci is pci-centric, there should be nothing
> x86 specific there.

The kvm_irqchip_add_msi_route & co is a problem, it more/less dives into
the x86/ia64 specific routing stuff at a generic level, I'll have to
hook things up differently in qemu I suspect.

Not a huge deal, we can sort it out.

Cheers,
Ben.