From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
Anthony Liguori <aliguori@us.ibm.com>, KVM <kvm@vger.kernel.org>,
Carsten Otte <cotte@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avi Kivity <avi@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] s390: Virtual channel subsystem support.
Date: Tue, 13 Nov 2012 11:11:34 +0100 [thread overview]
Message-ID: <20121113111134.1a8baad1@BR9GNB5Z> (raw)
In-Reply-To: <20121113011755.GA27831@amt.cnet>
On Mon, 12 Nov 2012 23:17:55 -0200
Marcelo Tosatti <mtosatti@redhat.com> wrote:
> Hi Cornelia,
>
> On Wed, Oct 31, 2012 at 05:24:47PM +0100, Cornelia Huck wrote:
> > Provide a mechanism for qemu to provide fully virtual subchannels to
> > the guest. In the KVM case, this relies on the kernel's css support
> > for I/O and machine check interrupt handling. The !KVM case handles
> > interrupts on its own.
> >
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> > ---
> > hw/s390x/Makefile.objs | 1 +
> > hw/s390x/css.c | 1209 ++++++++++++++++++++++++++++++++++++++++++++
> > hw/s390x/css.h | 90 ++++
> > target-s390x/Makefile.objs | 2 +-
> > target-s390x/cpu.h | 232 +++++++++
> > target-s390x/helper.c | 146 ++++++
> > target-s390x/ioinst.c | 737 +++++++++++++++++++++++++++
> > target-s390x/ioinst.h | 213 ++++++++
> > target-s390x/kvm.c | 251 ++++++++-
> > target-s390x/misc_helper.c | 6 +-
> > 10 files changed, 2872 insertions(+), 15 deletions(-)
> > create mode 100644 hw/s390x/css.c
> > create mode 100644 hw/s390x/css.h
> > create mode 100644 target-s390x/ioinst.c
> > create mode 100644 target-s390x/ioinst.h
>
> > +void kvm_s390_enable_css_support(CPUS390XState *env)
> > +{
> > + struct kvm_enable_cap cap = {};
> > + int r;
> > +
> > + /* Activate host kernel channel subsystem support. */
> > + if (kvm_enabled()) {
> > + /* One CPU has to run */
> > + s390_add_running_cpu(env);
>
> Care to explain this?
Old code leftovers; I've removed it.
>
> > +
> > + cap.cap = KVM_CAP_S390_CSS_SUPPORT;
> > + r = kvm_vcpu_ioctl(env, KVM_ENABLE_CAP, &cap);
> > + assert(r == 0);
> > + }
> > +}
>
>
next prev parent reply other threads:[~2012-11-13 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 16:24 [Qemu-devel] [RFC PATCH v3 0/3] s390: channel I/O support in qemu Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 1/3] Update linux headers Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 2/3] s390: Virtual channel subsystem support Cornelia Huck
2012-11-13 1:17 ` Marcelo Tosatti
2012-11-13 10:11 ` Cornelia Huck [this message]
2012-11-19 13:30 ` Alexander Graf
2012-11-20 9:27 ` Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 3/3] s390: Add new channel I/O based virtio transport 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=20121113111134.1a8baad1@BR9GNB5Z \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.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 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).