From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: gleb@kernel.org, borntraeger@de.ibm.com, qemu-devel@nongnu.org,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 3/5] s390x: Add I/O adapter registration.
Date: Wed, 9 Apr 2014 16:24:01 +0200 [thread overview]
Message-ID: <20140409162401.072f887c.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <5345538C.9060709@suse.de>
On Wed, 09 Apr 2014 16:05:00 +0200
Alexander Graf <agraf@suse.de> wrote:
>
> On 09.04.14 13:34, Cornelia Huck wrote:
> > Register an I/O adapter interrupt source for when virtio-ccw devices start
> > using adapter interrupts.
> >
> > Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> > ---
> > hw/intc/s390_flic.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++
> > hw/s390x/css.c | 51 ++++++++++++++++++++++++++++++++++++++++++
> > hw/s390x/css.h | 4 ++++
> > hw/s390x/virtio-ccw.c | 4 ++++
> > hw/s390x/virtio-ccw.h | 1 +
> > target-s390x/cpu.h | 33 +++++++++++++++++++++++++++
> > 6 files changed, 152 insertions(+)
> >
> > diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> > index 2bf0af8..1193682 100644
> > --- a/hw/s390x/virtio-ccw.c
> > +++ b/hw/s390x/virtio-ccw.c
> > @@ -522,6 +522,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> > dev->thinint_isc = thinint->isc;
> > dev->ind_bit = thinint->ind_bit;
> > cpu_physical_memory_unmap(thinint, hw_len, 0, hw_len);
> > + ret = css_register_io_adapter(CSS_IO_ADAPTER_VIRTIO,
> > + dev->thinint_isc, true, false,
> > + &dev->adapter_id);
>
> In all other machines the machine file is the one creating the link
> between a device and the interrupt controller. Can we do something
> similar for s390?
Hm. This would imply we'd need to add a virtio I/O adapter for each isc
(0-7) at startup, regardless whether the guest enables adapter
interrupts on any of those iscs. Moreover, we'd need to do the same for
each type (on each isc) if we add more types of I/O adapters later
(should we want to support one of the other adapter-interrupt using
devices). I'd prefer to add an I/O adapter only when needed.
next prev parent reply other threads:[~2014-04-09 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 11:34 [Qemu-devel] [PATCH v4 0/5] qemu: irqfds for s390x Cornelia Huck
2014-04-09 11:34 ` [Qemu-devel] [PATCH v4 1/5] linux-headers: update Cornelia Huck
2014-04-09 11:34 ` [Qemu-devel] [PATCH v4 2/5] kvm: add kvm_enable_cap_{vm,vcpu} Cornelia Huck
2014-04-09 13:58 ` Alexander Graf
2014-04-09 14:16 ` Cornelia Huck
2014-04-09 11:34 ` [Qemu-devel] [PATCH v4 3/5] s390x: Add I/O adapter registration Cornelia Huck
2014-04-09 14:05 ` Alexander Graf
2014-04-09 14:24 ` Cornelia Huck [this message]
2014-04-09 14:30 ` Alexander Graf
2014-04-09 15:35 ` Cornelia Huck
2014-04-09 15:53 ` Alexander Graf
2014-04-09 16:20 ` Cornelia Huck
2014-04-09 11:34 ` [Qemu-devel] [PATCH v4 4/5] s390x/virtio-ccw: reference-counted indicators Cornelia Huck
2014-04-09 11:34 ` [Qemu-devel] [PATCH v4 5/5] s390x/virtio-ccw: Wire up irq routing and irqfds Cornelia Huck
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=20140409162401.072f887c.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=gleb@kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).