From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel List <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [RFC] KVM: PPC: Add level based interrupt logic
Date: Wed, 01 Sep 2010 15:09:06 +0300 [thread overview]
Message-ID: <4C7E4262.2040905@redhat.com> (raw)
In-Reply-To: <1D0E7834-57D9-4845-9329-141CD2443039@suse.de>
On 09/01/2010 02:58 PM, Alexander Graf wrote:
>
>> Why not limit it to ppc? Someone might call it by accident.
> How would you model it? Call kvm_arch_set_interrupt in hw/ppc.c? Which header would I define the call in?
>
Well, eventually this finds its way to cpu code in target-ppc, no? from
there you can call a function in target-ppc/kvm.c without any need for
tricks.
So just hack it there.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-09-01 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 10:07 [Qemu-devel] [RFC] KVM: PPC: Add level based interrupt logic Alexander Graf
2010-09-01 7:41 ` [Qemu-devel] " Avi Kivity
2010-09-01 9:38 ` Alexander Graf
2010-09-01 11:45 ` Avi Kivity
2010-09-01 11:47 ` Alexander Graf
2010-09-01 11:56 ` Avi Kivity
2010-09-01 11:58 ` Alexander Graf
2010-09-01 12:09 ` Avi Kivity [this message]
2010-09-01 12:09 ` Avi Kivity
2010-09-01 12:10 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C7E4262.2040905@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.