From: Avi Kivity <avi@qumranet.com>
To: Carsten Otte <cotte@de.ibm.com>
Cc: "kvm-devel@lists.sourceforge.net"
<kvm-devel@lists.sourceforge.net>,
schwidefsky@de.ibm.com, Olaf Schnapper <os@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH 2/2] virtio-s390: Change virtio interrupt definitions to follow architecture
Date: Thu, 17 Apr 2008 11:44:40 +0300 [thread overview]
Message-ID: <48070DF8.3070303@qumranet.com> (raw)
In-Reply-To: <1208354797.6122.13.camel@cotte.boeblingen.de.ibm.com>
Carsten Otte wrote:
> From: Christian Borntraeger <borntraeger@de.ibm.com>
>
> This patch changes the interrupt defintions for virtio on s390. We now use
> the extint number 0x2603, which is used as a host interrupt already by z/VM
> for pfault and dasd_diag.
> We will use subcode 0x0D to distinguish virtio from dasd and pfault.
>
Don't you need to change KVM_S390_INT_VIRTIO as well?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-17 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1208354539.6122.6.camel@cotte.boeblingen.de.ibm.com>
2008-04-16 14:06 ` [PATCH 1/2] kvm-s390: provide get/set_mp_state stubs to fix compile error Carsten Otte
2008-04-16 16:21 ` Hollis Blanchard
2008-04-16 17:44 ` Marcelo Tosatti
2008-04-17 8:18 ` Avi Kivity
2008-04-16 14:06 ` [PATCH 2/2] virtio-s390: Change virtio interrupt definitions to follow architecture Carsten Otte
2008-04-17 8:44 ` Avi Kivity [this message]
2008-04-17 9:14 ` Christian Borntraeger
2008-04-17 9:27 ` Avi Kivity
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=48070DF8.3070303@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=os@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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.